tordans created an issue (openstreetmap/openstreetmap-website#6678)
This request is based on
https://github.com/openstreetmap/iD/issues/8991#issuecomment-3711264411
**The use case is:**
iD loads data using
[`/maps`](https://wiki.openstreetmap.org/wiki/API_v0.6#Retrieving_map_data_by_bounding_box:_GET_/api/0.6/map).
However, the API only returns ways when there is at least one node in the
given bbox.
For cases like
https://github.com/openstreetmap/iD/issues/8991#issuecomment-3711264411 this
can lead to a wrong map view. In addition, iD has no way of knowing that data
is missing or help the use to resolve the issue.
[The API
docs](https://wiki.openstreetmap.org/wiki/API_v0.6#Retrieving_map_data_by_bounding_box:_GET_/api/0.6/map)
document this behavior:
> All ways that reference at least one node that is inside a given bounding
> box, any relations that reference them [the ways], and any nodes outside the
> bounding box that the ways may reference.
I suggest we use this issue to talk about how we can resolve this.
Ideally, we will find a way to change this as part of API v0.6.
One way would be to find a way to include all intersecting ways in the data.
Personally I would not consider this a breaking change but more like a bug fix
which means we could change it as part of v0.6.
Does anyone see data users that would rely on this feature as a feature (AKA
they would have issues with this bug fix)?
Alternatively we could add a new endpoint or add a param to the existing
endpoint that changes the current behaviors.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6678
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/issues/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
