Using postgis to store tile index

[Ed McNierney]

John -

Like Jeff, I've got plenty of huge TILEINDEX files.  But remember that
the TILEINDEX lets MapServer quickly select the FEW files it needs to
respond to a particular request.  If you're creating a "zoomed out" map
that ends up using most of your shapefiles anyway, then there's no
benefit to quickly figuring out which ones you need.

And make sure you've used shptree to create a .qix quadtree index for
your TILEINDEX file, as well as for all your shapefiles.  Have you done
that?

	 - Ed

Ed McNierney
President and Chief Mapmaker
TopoZone.com / Maps a la carte, Inc.
73 Princeton Street, Suite 305
North Chelmsford, MA  01863
Phone: +1 (978) 251-4242
Fax: +1 (978) 251-1396
ed at topozone.com 

-----Original Message-----
From: UMN MapServer Users List [mailto:MAPSERVER-USERS at LISTS.UMN.EDU] On
Behalf Of Jeff Hoffmann
Sent: Thursday, July 13, 2006 7:44 AM
To: MAPSERVER-USERS at LISTS.UMN.EDU
Subject: Re: [UMN_MAPSERVER-USERS] Using postgis to store tile index

John Preston wrote:
> I am currently using the TILEINDEX parameter in the LAYER section of 
> the  map file to get tiling implemented. Is it possible to use a 
> postgis table to store the tile index instead of a shape file (xxx.shp

> and xxx.dbf) as I may have a very large number of tile (~10,000) and I

> was figuring that the postgis solution would offer better response 
> times.
> 
> If not does anybody know what I kight do to speed up the response time

> when I have say 10000 files within a particular scale region.

Make sure that your tileindex is correctly indexed using shptree.  Also,
if only have one layer set up to handle a wide range of scales, you
might find it performs better if you build overview layers for the
higher scales so you end up opening less files per request.  I have
several layers set up that have over 100,000 images that perform
perfectly well with a standard shapefile tileindex.

---
Jeff Hoffmann
Head Plate Spinner
PropertyKey.com