[OSM-dev] what server next?

Micha Ruh gnubold at gmail.com
Tue Sep 8 04:47:04 BST 2009

2009/9/8 Grant Slater <openstreetmap at firefishy.com>

> What is next? What are we going to need next?

Last night I dreamed about a solution to the cc-by-sa attribution problem.
It would be soo nice to have appropriate attribution displayed in OpenLayer
while browsing the map.

There it goes..

A server calculates user contribution for sets of 3x3 tiles (supertiles) for
each zoom level 12-18. The calculation is done once a week (maybe done by
t at h clients). Users adding  ways/pois get a score of 3 per way/poi added,
users adding more tags to existing way/pois get a score-point of 1 for each
edit. Import sources get a 0.1 score-point per way/poi.

Score-points get calculated per supertile, top 4 contributors for each
supertile including their score-points get stored in a database, the
attribution-db. Keys and indexes on zoom level and new supertile index
(maybe central tile x/y).

OpenLayer gets extended in a way that while requesting tiles an additional
request to the attribution-db is issued, contributors for the corresponding
supertile get loaded and nicely presented in the lower right corner of the

OSM runs the attribution-db and spreads the extended OpenLayer lib.

* Information which user created a way is only available in history, so
initial calculation is heavy-load, but must only be done once.

* attribution information for mutliple supertiles could be aggregated into
attribution-pages which are stored in the attribution-db. this
attribution-pages are sent to the client, which sorts out the appropriate
attribution with some .js magic for the current displayed view. This could
save the attribution-db from load.

* attribution score-point changes could be calculated on-the-fly, once an
initial load of the attribution-db is done.


Need more sleep, now.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20090908/dcc81dc9/attachment.html>

More information about the dev mailing list