Peter Körner schrieb:
Am 14.06.2010 21:07, schrieb Stephan Knauss:
Peter Körner wrote:
I don't think it's necessary to use a tileserver for this style. You could use the minutely updated postgis database to serve an openlayers vector layer.
Hm, it does not sound like a good idea to transfer 15.000 or more elements to be processed with openlayers. I saw this approach before, it required each user to download 1.5MB of POI-data. A lot more compared to the few kb of the bitmap layer that can also be cached.
You're not supposed to transfer all POIs at once but only those in the current viewport. In higher zoom levels you need to aggregate all POIs that are close to each other (eg. >1000km on a world-map) into a single POI. You may vary this POIs' size with the number of single POIs aggregated.
Clustering seem difficult (http://docs.scipy.org/doc/scipy/reference/cluster.hierarchy.html#references) and I found no PostGIS function for it. So it seem necessary to work with random and a limit.
Is there a specific reason why it's so difficult to get a custom rendering besides the scripts needed not existing?
It's that simple: we're no style hoster.
STOP. I can't see a different between the existing surveillance layer and the smoking layer. Both have a lot of point objects and both are political maps. Our "sponsor" the "Verein" is political active and support democracy processes, you can see this on the Wahlprüfsteinen ( http://blog.wikimedia.de/2010/05/05/wahlpruefsteine-landtagswahl-nordrhein-w... ) and so on.
The old surveillance website (http://osm.vdska.de/?zoom=14&lat=52.40252&lon=9.7162&layers=B0TF... dangerous!) works with vector layer and kills my browser very often. Now we have an working solution and should use it in other situations if we can't provide a better way. The smoking layer is also IMO a use-case where OSM can show that it can more than other systems.
I see only two problems: *I think the maps on toolserver should be political neutral. (green, yellow, red is it not.) *The surveillance layer is relative stable. To compare the smoking layer will have a rapid change at beginning. So I have no idea to run efficient tile caching or so.
Greetings Kolossos