[OSM-dev] rendering: mad ideas

Nick Whitelegg Nick.Whitelegg at solent.ac.uk
Fri Mar 24 11:13:38 GMT 2006

>Maybe implement an interim solution that assumes most changes are made
>with the online applet editor.  The server should deny any edit that
>does not also come with an attached, rendered version of the "changed"
>tile (a PNG).  The uploaded tile image is immediately and cheaply cached
>by the server.  Fewer problems with conflicts, since the newest always
>wins, and almost trivial to implement since the applet is already
>rendering this stuff. 

Does this mean that the non-applet editors will be unable to edit OSM data 
until they too implement this?



More information about the dev mailing list