Opened 12 years ago

Closed 12 years ago

#1112 closed enhancement (fixed)

<bound> vs. <bounds>

Reported by: bob@… Owned by: framm
Priority: major Milestone:
Component: Core Version:
Keywords: Cc:


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 ( 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.

Attachments (0)

Change History (2)

comment:1 Changed 12 years ago by bob@…

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

comment:2 Changed 12 years ago by framm

Resolution: fixed
Status: newclosed

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.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain framm.
as The resolution will be set.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.