TileIndexes and paths - a proposal

[Stephen Woodbridge]

Brent,

I have one variant on my example:

Brent Fraser wrote:

> Some examples:
> =============
> A.  The Steve Woodbridge senario:
> -----------------------------------------
> 1. [Location of the map file]  = /u/mapfiles/
> 2. SHAPEPATH = "/u/data"
> 3. LAYER (tileIndex) : DATA =  "tiger-maps/roads-tile"
> 4. LAYER (tiles): DATA = ""
> 5. LAYER: TILEITEM contents = "./data/01/001/roads.shp"
>
> would result in a tile path of
>      /u/data/tiger-maps/./data/01/001/roads.shp

1. [Location of the map file]  = /u/mapfiles/
2. SHAPEPATH = "/u/data"
3. LAYER (tileIndex) : DATA =  "tiger-maps/county-tile"
4. LAYER (tiles): DATA = "roads"
5. LAYER: TILEITEM contents = "./data/01/001"

would result in a tile path of
      /u/data/tiger-maps/./data/01/001/roads[.shp]

I have found that often a spatial area (like a county) has many layers
in it and they can all share the the same tileindex and then I use the
DATA to select the specific file for the layer. ie. the tile represents
the extents of the data in the directory and then you can have multiple
layers in the directory.

I think you description implies this would happen anyway, but I just
wanted to make sure.

Thank you for taking the lead on this.

-Steve W.