Many functionalities are available:
* ergonomic design
* large amount of pregenerated base layers (aerial and national maps provided by swisstopo)
* around 50 layers that are concatenated with TileCache
* layertree with groups and radio buttons
* advanced tooltips
* high quality print
This website takes advantage of amazon web services as cloud computing infrastructure.
4 comments:
"around 50 layers that are concatenated with TileCache". Just curious : is that one tilecache.cfg "layer" with a list of 50 comma-separated layers pointing to a number of mapfiles ? What does it look like in the cfg ? And what does that entail on the transparency and other image settings in the mapfiles ?
TIA
yves,
Basically it works like this:
Our tilecache.cfg contains ~50 individual layers (not comma separated), the user make a selection (via the layers tree), this "selection" is a standard WMS getMap request send to tilecache. Finally, tilecache combine all the layers.
Layers concatenation is a standard tilecache feature
Hi Frédéric,
I came across this : http://openlayers.org/pipermail/tilecache/2008-June/001126.html so I was wondering if you were using a mapfile with all your layers defined and one single Tilecache layer object (as mentioned in that post) :
[layer]
type=WMS
map=path/to/mapfile
layers=sticks,grid
, layerA,layerB
Would something like that work ?
Yes, we have a mapfile with all the layers and a tilecache.cfg without comma separated list, something like:
[foo]
type=MapServer
layers=foo
mapfile=/path/to/veloland.map
[bar]
type=MapServer
layers=bar
mapfile=/path/to/veloland.map
Then, we if we ask tilecache for layers 'foo' and 'bar', tilecache combine the two images and returns the result.
Take a look at: http://openlayers.org/pipermail/tilecache/2008-June/001130.html
and http://trac.tilecache.org/changeset/363
Post a Comment