From db620a7d045a9279bf4c9b1777dea45c2551b3b1 Mon Sep 17 00:00:00 2001 From: Regina Obe Date: Fri, 16 Dec 2011 01:25:20 +0000 Subject: [PATCH] cosmetic change to lists git-svn-id: http://svn.osgeo.org/postgis/trunk@8437 b70326c6-7e19-0410-871a-916f4a2858ee --- doc/using_raster_dataman.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/using_raster_dataman.xml b/doc/using_raster_dataman.xml index a775619ea..886d89f6f 100644 --- a/doc/using_raster_dataman.xml +++ b/doc/using_raster_dataman.xml @@ -295,10 +295,10 @@ psql -d gisdb -f elev.sql Overview tables contain the same constraints as other raster tables as well as additional informational only constraints specific to overviews. The informaiton 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 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. Computations are generally faster to do on them than their higher resolution parents because there are fewer records and each pixel covers more territory. Though the computations are not as accurate as the high-res tables they support, they can be sufficient in many rule-of-thumb computations. - + The raster_overviews catalog contains the following columns of information. -- 2.50.1