[OSM-dev] idea: before-after map
osm-lists at mazdermind.de
Mon Dec 5 21:31:07 GMT 2011
Am 05.12.2011 19:11, schrieb Martijn van Exel:
> For it to work (for current changesets) though, we would need a
> continuously updated full history database..
Doing the import is one thing, doing the update is a whle different thing. Both being mixed up into the same application results in a lot of not-so-nice and not-so-well-optimized code (see osm2pgsql). For updates you'll need a different cache strategy, a different level of access to the database and different algorithms.
For me, cleaning up the importer, adding multipolygon and route-support as well as optimizing the importer to be able to handle full-planet-full-history imports is higher on the priority list then an updater, and you'll, have to live with that ;)
I'd love to see those tools sketched out on the data we have already. Developing a nice before/after/diff app is a really complex task and maybe if the app is finished, the updater is, too. Don't wait for other tasks beeing completed if you could work with the things that are in place already.
More information about the dev