[OSM-dev] Consensus on areas?

Nicola Ranaldo ranaldo at unina.it
Tue Aug 29 12:05:54 BST 2006


On Tuesday 29 August 2006 12:29, Nick Whitelegg wrote:
> >*) to avoid nodes duplications editors before uploading a new node should
>
> do a
>
> >map request, and should warning the user if there ar a node closest to
>
> the
>
> >new, letting him  in creating a new node or updating the one existing
>
> I think this (and any other similar duplication checking) should be done
> server-side, to avoid undue complexity in editor code and every single
> editor having to implement such code.
>
> Nick

Yes! this would be very very good! and it could be usefull to have a roadmap 
with a prediction of api releases, editors developers so could choose to 
implement or not work-arounds.
About api i was thinking it could be usefull to implement xml formatted 
response. With this you may give to clients a structured response, error 
code, error text and so on. Some weeks ago, some way create requests gived me 
a mysql error. A simple editor not checking data is numerical, could convert 
that string in a '0'. Adopting xml will prevent some similiar race conditions 
and more flessibility in response parsing then actual http codes.

        Niko




More information about the dev mailing list