[osmosis-dev] bound/bounds element in OSM XML

[Brett Henderson]

On 11 December 2011 15:00, Tobias Knerr <osm at tobias-knerr.de> wrote:

> Hello,
>
> I'm using Osmosis as a library for reading OSM files in OSM2World. It
> works well for this task and allows me to easily support various input
> formats. Recently, though, I added handling of files' bounds to
> OSM2World. This worked well with .osm.pbf files, but not with .osm
> files. Bounds in the latter were ignored entirely.
>
> Looking at the Osmosis source code on GitHub, I noticed several
> differences to the XML format as described on
> http://wiki.openstreetmap.org/wiki/OSM_XML
>
> The first difference is that OsmElementProcessor [1] looks for a
> "bound", rather than "bounds", element.
>
> More differences are visible in BoundElementProcessor [2], particularly
> that the "origin" attribute is considered required by Osmosis, and that
> Osmosis expects a "box" attribute with 4 comma-separated values, rather
> than the 4 attributes "minlat", "minlon", "maxlat" and "maxlon" used in
> the wiki.
>
> My question is: Why do these differences exist? Are they intentional?
>

I'm not sure of the exact history here, but I think bound existed before
bounds.  bounds is a newer concept with different attributes that has never
been implemented in Osmosis.  I'm not sure what would be involved in
updating Osmosis to support it, but perhaps it's just a matter of updating
the XML tasks to use the different element and attributes.

Brett
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osmosis-dev/attachments/20111214/a61681a5/attachment.html>