Change in API behavior: Higher level relations are not returned #2699
Comments
Author: TomH Please do provide an example... |
Author: sebastiank
A view weeks ago, the relation 22956 was returned by the bbox request, already. |
Author: amm Oh, my comment didn't seem to have made it... (forgot to save it) The patch is probably still broken, definitely needs more testing, and is rather ugly. So I have only attached it for reference in case someones else gets the time to look at it. |
Author: malenki Today I ran into this one. To make it short: After all I created three parent relations for the same issue but could see none after i downloaded a part of the ways afresh (working with josm). I discovered the parent relations by incident via osm => data => details. |
Author: zere (In [21049]) Added functionality to fetch meta-relations with cgimap. Should fix #2699, but needs performance testing. |
Author: zere (In [21059]) Better relations query for cgimap - this time actually fixes #2699 as far as i can tell. |
Author: zere (In [21062]) Fixed another bug - should have been pulling in unwayed nodes into the relation lookup too. Refs #2699. |
Author: Matt Ran OsmMapCallValidator on the bbox (13, 54, 13.5, 54.5) and after 1000 checks there were no errors. I think it might be fixed, finally! |
Reporter: sebastiank
[Submitted to the original trac issue database at 3.18pm, Sunday, 7th February 2010]
For quite some time, the API did return network relations for a bounding box request. (I. e. parent relations of the relations that have members in the bounding box.)
This is no longer the case. It was speculated, that it has something to do with the change of the API from ruby to C++ in the beginning of February.
The problem is, that these network relations are now very hard to find. Because they are never returned for a bbox request, you have to guess or know a child relation and then go to the
relation dialog -> parent relation tab
and clickreload
(In JOSM). However most relations don't have any parent relations, so you are looking for needles in a haystack.I am aware that the doc on the wiki does not guarantee to return parent relations, but it is a regression nonetheless and it would be very helpful if the old behavior could be restored.
The issue came up 2 times on talk-de:[[BR]]
http://lists.openstreetmap.org/pipermail/talk-de/2010-February/062456.html [[BR]]
http://lists.openstreetmap.org/pipermail/talk-de/2010-February/062713.html [[BR]]
I can provide examples if needed.
The text was updated successfully, but these errors were encountered: