<bound> vs. <bounds>

[bob@…]

The API used to output <bounds request_minlat= request_minlon= request_maxlat= request_maxlon= /> in the map request. I'm trying to get it supported again (​http://trac.openstreetmap.org/ticket/1011) as osmarender really needs it to function at it's best.

It would be nice if josm also used <bounds> instead of <bound>, and also dropping box= in favor of four separate values as you then only need the xml-parser that's already required and not a separate comma-separated parser (yes, it's actually non-trivial in xslt).

Perhaps josm could use request_{min,max}{lat,lon} parameters when reading from the api, and, if it has to generate them for itself, output just {min,max}{lat}{lon}? That sounds like a pretty correct way to handle things.

TomH wants us to clean up the inconsistencies here before he fixes the ticket so I'd appreciate somebody at least having a look at it pretty soon.

[bob@…]

TomH just changed the API to return <bounds minlat= minlon= maxlat= maxlon= />.

[framm]

fixed in r769. <bound> is still written out in its old form, with an added "note" attribute saying that it is deprecated; additionally, <bounds> is written out as specified above (with minlat,maxlat,minlon,maxlon attributes). on read, <bound> objects without "note" attribute are still parsed for backwards compatibility, <bound> objects with "note" are ignored, and <bounds> objects are always parsed. if a <bounds> object on input does not have an origin specified, the "generator" attribute of the enclosing <osm> tag will be used.