Yikes, first time poster! I think the speed to generate a single tile is wholely dependent on the map-rendering engine and the dataset.
For example, here at the City of Saint Paul, our streets layer is entirely vector. I can generate a very very large tile with highly detailed streets for the entire city using Mapserver in less than 1/3 of a second. Given the nature of MapServer, and the size of the shapefile which stores our streets layer, multiple tiles is much much slower (as the shapefile needs to be read from disk and loaded to memory for each rendered tile). It would be nice to have some of the effects of tiling without the high-cost it currently presents in rendering performance. Dan "Ducky" Little City of Saint Paul / Public Works / GIS ----- Original Message ---- From: Stephen Woodbridge <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [email protected] Sent: Wednesday, October 3, 2007 9:37:29 PM Subject: Re: [OpenLayers-Dev] singleTile optimization [EMAIL PROTECTED] wrote: > What do you think about aligning singleTile bounds to the grid to > promote cacheability in the client? I think that this should be an option in the layer definition if it gets done. I can see some benefits to doing this, but the down side is that all images generated will be larger and slower to generate and the singleTile option needs to support more than one use case in my mind anyway. -Steve _______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev ____________________________________________________________________________________ Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
_______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev
