Opened 3 years ago
Last modified 12 months ago
#4142 new defect
JOSM does not query API for referring relations when downloading primitives
| Reported by: | Nakor | Owned by: | team |
|---|---|---|---|
| Priority: | critical | Component: | Core |
| Version: | latest | Keywords: | |
| Cc: |
Description (last modified by simon04)
Download data using the following bounding box: http://www.openstreetmap.org/?lat=42.65924&lon=-83.3199&zoom=17
Download all members from the relation
Search for way 43418202. It is shown only as a member of relation 308,352 but if it is also member of another relation (see http://www.openstreetmap.org/browse/way/43418202).
This would cause inconsistencies if the way is split.
Attachments (0)
Change History (8)
comment:1 Changed 3 years ago by mjulius
- Summary changed from Incomplete data when downloading all memebers of a relation to JOSM does not query API for referring relations when downloading primitives
comment:2 Changed 3 years ago by bastiK
Ticket #4405 has been marked as a duplicate of this ticket.
comment:3 Changed 3 years ago by bastiK
comment:4 Changed 3 years ago by Nakor
Ticket #4734 has been marked as a duplicate of this ticket.
comment:5 Changed 3 years ago by stoecker
Ticket #5086 has been marked as a duplicate of this ticket.
comment:6 Changed 3 years ago by stoecker
- Priority changed from major to critical
comment:7 Changed 15 months ago by simon04
- Description modified (diff)
Any update on this critically prioritized ticket?
comment:8 Changed 12 months ago by skyper
Maybe a warning with an option to download parents before splitting could help as these ways are outside of the download area.



When downloading primitives from the API (with multi get) the API does not return relations the primitive is member of. There is a special API call for that:
JOSM needs to iterate over all downloaded primitives and check whether they are members of any relation.
Better would be if the API provided a call like
that returns the same kind of data like the map call.