Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Wong order of coordinates in viewbox parameter of URL request #5420

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 4 comments
Closed

Comments

@openstreetmap-trac
Copy link

Reporter: David_01
[Submitted to the original trac issue database at 11.46am, Monday, 12th September 2016]

On https://nominatim.openstreetmap.org/ if "apply viewbox" is checked, URL request is issued with viewbox=,,, while expected order is ,,,.
This options anyway seems to have no effect without the bounded=1 parameter.
Adding bounded=1 and reordering the coordinates in URL request produces the expected result.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 9.05pm, Monday, 12th September 2016]

I can confirm the bad ordering. mtmail?

The viewbox parameter, when correctly ordered, works fine though. Compare:

http://nominatim.openstreetmap.org/search.php?q=london&polygon=1&viewbox=-81.19806,42.96961,-81.28329,43.01356

vs.

http://nominatim.openstreetmap.org/search.php?q=london

@openstreetmap-trac
Copy link
Author

Author: mtmail
[Added to the original trac issue at 12.48pm, Tuesday, 13th September 2016]

Fix ready in osm-search/Nominatim#527, not live in production yet.

Thanks for reporting David_01!

@lonvia: you're right. When the viewbox parameter gets set via a URL then it is applied correctly. The trouble was that after map interaction it got set wrong on any subsequent requests. Quite confusing.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 8.00pm, Tuesday, 13th September 2016]

Fix is merged but not yet live on osm.org. The code is currently quite a bit behind and the change cannot be easily merged. We'll move to the new version in the next few weeks and then the fix will go live.

@openstreetmap-trac
Copy link
Author

Author: lonvia
[Added to the original trac issue at 8.00pm, Thursday, 13th October 2016]

The code has been merged in the meantime and the issue should be fixed on osm.org as well.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant