[mapserver-users] Indexing Shape files
AScalise at geovue.com
Tue Oct 29 17:17:19 EST 2002
Thanks for your help. We are still experimenting with this feature.
We do, indeed, want to create a single Tile file for hanlding GDT data.
We can see that one single file provides a lot of advantages from a
manteinance and administrative standpoint.
However, are there any performance trade-offs in having a very large Tile
file for the whole US, as compared to inidividual tile fiels for each state?
200 Lincoln Street 5th Floor
Boston, Massachusetts 02111 USA
p 617.451.2520 x122
ascalise at geovue.com
From: owner-mapserver-users at lists.gis.umn.edu
[mailto:owner-mapserver-users at lists.gis.umn.edu]On Behalf Of Steve Lime
Sent: Tuesday, October 29, 2002 2:26 PM
To: Chip.Hankley at GASAI.Com; mapserver-users at lists.gis.umn.edu
Subject: RE: [mapserver-users] Indexing Shape files
As an aside, actually sometimes you might use the DATA line. MapServer
tiles can be used to store:
1) tiles with totally unique files names or
2) tiles with identical shapefile names but different directories
In the latter case you might store just the directory name in TILEITEM
and the shapefile name in DATA. The two then get merged to create a full
file name. This allows you to get away with a single TILEITEM for
multiple layers which can be a big deal with datasets like GDT roads...
>>> "Hankley, Chip" <Chip.Hankley at GASAI.Com> 10/29/02 10:58AM >>>
When you're using a TILEINDEX, you don't need a DATA line... the
line IS the data line. Here's an example -
In this case, TILEINDEX is the path (relative to the mapfile's
the indexing shapefile, and TILEITEM is the field name in the index
shapefile that points to the individual tile data sources (in this
More information about the mapserver-users