From: Regina Obe Date: Sat, 17 Dec 2011 01:50:09 +0000 (+0000) Subject: fix typo X-Git-Tag: 2.0.0alpha1~425 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=ffd7263447b24000eaf1f00ab53d21ee63b73c6e;p=postgis fix typo git-svn-id: http://svn.osgeo.org/postgis/trunk@8449 b70326c6-7e19-0410-871a-916f4a2858ee --- diff --git a/doc/using_raster_dataman.xml b/doc/using_raster_dataman.xml index a8c34f267..b969fdee0 100644 --- a/doc/using_raster_dataman.xml +++ b/doc/using_raster_dataman.xml @@ -317,7 +317,7 @@ psql -d gisdb -f elev.sql Raster Overviews raster_overviews catalogs information about raster table columns used for overviews and additional information about them that is useful to know when utilizing overviews. Overview tables are cataloged in both raster_columns and raster_overviews because they are rasters in their own right but also serve an additional special purpose of being a lower resolution caricature of a higher resolution table. These are generated along-side the main raster table when you use the -l switch in raster loading. Overview tables contain the same constraints as other raster tables as well as additional informational only constraints specific to overviews. - The information in raster_overviews does not duplicate the information in raster_columns. If you need the information about an overview table present in raster_columns you can join the raster_overviews and raster_columns vuews together by to get the full set of information you need. + The information in raster_overviews does not duplicate the information in raster_columns. If you need the information about an overview table present in raster_columns you can join the raster_overviews and raster_columns together to get the full set of information you need. Two main reasons for overviews are: Low resolution representation of the core tables commonly used for fast mapping zoom-out.