Error in bounding box constraints for XAPI relation queries #1839
Comments
|
Author: rjw62[at]cantab.net Just to add that new erroneous relations seem to be appearing in answer to the above API calls. The new appearances are not always new relations, but their appearence seems to be triggered by them being editing by someone. |
|
Author: Mikado I'm having the same problem with relations of "restriction" type. At some point it seemed that errorneous relations are returned along with the requested, but now there are some valid relations outside the bbox in the output. |
|
Author: pnorman Closing as this relates to the old XAPI which is no longer maintained. The new jxapi can be found at https://github.com/iandees/xapi-servlet and issues should be reported there. |
Reporter: rjw62[at]cantab.net
[Submitted to the original trac issue database at 8.10am, Wednesday, 20th May 2009]
I've been playing with the OSM XAPI, trying to extract a list of all the
relations for bus routes in Oxford, UK.
I've been using http://www.informationfreeway.org/api/0.5/relation[route=bus][bbox=-1.33827,51.70745,-1.16867,51.79290] and more recently http://osmxapi.hypercube.telascience.org/api/0.6/relation[route=bus][bbox=-1.33827,51.70745,-1.16867,51.79290] but both give odd results.
What's returned seems to include a lot (probably all) of the routes I was
expecting, but also many other relations that don't appear to be anywhere near the specified bounding box.
For instance, the first call above also returns
http://www.openstreetmap.org/browse/relation/81619 and
http://www.openstreetmap.org/browse/relation/61335 and
http://www.openstreetmap.org/browse/relation/61333
These are no-where near the bounding box specified in the XAPI call:
http://www.openstreetmap.org/?minlon=-1.33827&minlat=51.70745&maxlon=-1.16867&maxlat=51.79290&box=yes
The text was updated successfully, but these errors were encountered: