Hi John, I've had good success with Option 1, but I'm not sure I understand all of the conditions you've mentioned. I assume that you intend to display these tiles in a Google Maps mashup when you're done? If so, using TileCache's tilecache_seed.py would allow you to pre-generate the tiles using Mapserver initially, and then display them in the map - without ever calling on Mapserver again. The major advantage I see to this method is that Mapserver can aggregate all of the separate layers and display them in a common projection.
Good luck, Roger -- On Thu, Dec 4, 2008 at 7:07 AM, John Jameson <[EMAIL PROTECTED]> wrote: > > I need to make tiles compatible with Google maps out of this mess. The > outcome needs to be the typical pyramid of tiles where each detailed zoom > level has 4x the number of tiles than the level above. > > Here are the things I've considered strategy-wise: > > 1. Combine everything into a single map file and then let MapServer serve > the tiles (through TileCache). I can then go through the area of data I'm > interested in and collect the tiles and save them. The super advantage of > this strategy is that I can test it by having it serve the tiles live. > It'll be slower than having them pre-computed and that isn't ultimately > acceptable because I'll need offline use of the tiles and won't have > MapServer. Still, it allows for great testing before the tile collection > begins. The disadvantage is that I fear I'll run out of space with > hundreds > of raster maps and another hundred shapefiles (each with 20-30 layers). I > fear I'd have to re-gen MapServer with all of the layers needed. Back on > the plus side, it seems like MapServer will "quilt" the maps together > nicely. This strategy has me scared about resource size and speed needed. > >
_______________________________________________ mapserver-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapserver-users
