simonpoole left a comment (openstreetmap/openstreetmap-website#7054)
I've given both the relevant rails and c++ code a quick look, and it seems as
if it would actually be a net gain if the you could provide a list of element
ids + version ((typically ways) to not include in the map call output, and more
importantly not to recursively include any parent relations of those elements
(you probably don't want to do this for relations themselves). This would allow
the caller to avoid multiple downloads of the same data.
Example use case (I just spent half an hour getting a 509 every couple of
seconds doing exactly this): following a way that is a member of multiple
boundary relations. After the initial download the editor/downloader could
exclude the way and just download the literally handful of nodes that are
actually new when panning along the way.
The, downside of this is naturally that changes to the way and parent relations
wouldn't get "automatically" downloaded and there would have to be logic in the
client to now and then download all the data again, but that could be timeout
driven or similar. In any case it would be the callers responsibility to
maintain a consistent state of the data.
Pinging @mmd-osm and @tyrasd for their take on it.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/7054#issuecomment-4667214535
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/7054/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
