On 22.05.2010, at 21:26, Jason Birch wrote:
I've often wondered if power-of-two was the best approach from a
perception viewpoint. It definitely makes the most sense from a code
perspective. Anyone know of any research on this?
No research, but we invested some time while developing MapProxy
I've often wondered if power-of-two was the best approach from a
perception viewpoint. It definitely makes the most sense from a code
perspective. Anyone know of any research on this?
On 2010-05-22, Christopher Schmidt crschm...@crschmidt.net wrote:
On Fri, May 21, 2010 at 06:24:26PM -0300,
On 20.05.2010, at 22:10, miblon wrote:
If mapserver is to slow, almost everything else is to slow... I also noticed
your crosspost on the mapproxy list. mapproxy will even cache to more then
the 60TB youve estimated, because it will cache every wms request instead of
square, stitched
In my opinion (but of course Karsten needs to answer that himself) he
needs wms as I think he mentioned before. I may be wrong assuming that
mapproxy caches every unique wms request as a unique image.
I totally agree that he shouldn't preseed everything in advance,
especially when budgets are
On 21.05.2010, at 09:57, miblon wrote:
In my opinion (but of course Karsten needs to answer that himself) he needs
wms as I think he mentioned before.
Even then MapProxy should be faster. The overhead of MrSid/JP2 is larger
compared to the simple access to cached tiles.
I may be wrong
Hi Oliver
I don't understand what you mean with without caching tiles on disk.
You don't want to pre-generate the tiles?
If that's the case, I you can probably try with SpatialCache.
http://code.google.com/p/spatialcache/
___
Discuss mailing list
Hi All,
I am seeking some advice/ alternative ideas about the following project I am
working on...
I have been tasked with researching the best and fastest options serving huge
raster datasets on a web map using OpenLayers o the fly (using all Open Source
software). We want to serve the US
If mapserver is to slow, almost everything else is to slow... I also
noticed your crosspost on the mapproxy list. mapproxy will even cache to
more then the 60TB youve estimated, because it will cache every wms
request instead of square, stitched tiles.
If I where you and caching is an issue,
