[OSM-dev] Representing differences between sets of OSM data

[80n]

On 8/20/07, Jon Burgess <jburgess777 at googlemail.com> wrote:
>
> On Mon, 2007-08-20 at 13:16 +0100, 80n wrote:
> > Would it be helpful if non-standard extensions to the xml file made
> > proper use of xml namespaces?  It would prevent trouble in the future
> > with conflicting and misinterpreted attributes.
>
> It might be handy to add <bound ...> like JOSM does for downloads via
> the map API to indicate the original download bounding box. This gives
> an indication about how much of data is 'complete' and how much is due
> to ways which stretch outside of the requested bounding box but may not
> be complete (if the data is used to render a map, for example).


The <bound> tag did get generated by the 0.3 api, but it appears to have
gone missing in 0.4.

It is really useful for rendering using stand-alone Osmarender as it can use
this information directly instead of having to calculate a bounding box the
hard way.



> Of course, an agreed diff format would not be an extension and so
> > would not need to use a distinct namespace.
> >
> Currently each of the diff application uses something other then <osm>
> at the top level and should not get parsed by accident. JOSM however
> does claim to be a valid <osm> file, so yes it could use a namespace or
> emit <josm> files.
>
>         Jon
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20070820/69670b7a/attachment.html>