[OSM-dev] OSM Wishlist

[Roland Olbricht]

> Imagine there is list of schools in a city.
> 
> This list is maintained by a school district office with updated website,
> phone numbers, and office opening times.
> 
> They maintain this list through a simple PHP form on their website that
> allows them to make updates to each listing (node).
> 
> If any node on their list is changed by anyone but them or the people
> listed as able to edit that form on their own website (with their OSM Ids)
> then they are notified and can correct or confirm acceptance of the change.
>  They do not need to be the last editors of the node to know that the
> information contained therein is approved by them.

Nobody can block somebody else from editing something. If you mean "approve" 
in this direction, it would pretty never happen.

However, the school district can fork the Planet into an own database and move 
newer edits as "act of approvement" to its database. This is a typical use 
case of the idea of federated databases. No work has been done so far, but the 
point

* Tools to move, merge, and diff objects between different OSM databases

is surely a good point for the tools list. The federated databases will also 
solve most issues around imports, including patching an updated import without 
damaging exisiting data.

The second approach is to get a concise report of all updates that happened. 
It is then up to the stuff of the school district to rollback or accept the 
edits. Concering tools to watch updates, a lot of things have happened very 
recently. However, none of these tools work perfectly for the school district 
case yet, but this will significatly improve in the next weeks.

Roland
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20121013/8751ac14/attachment.html>