You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reverting a changeset (e.g., using the JOSM plugin reverter), one needs to obtain a large number of objects in a specific version. At the moment, those are obtained sequentially one by one:
GET https://api.openstreetmap.org/api/0.6/node/618158454/6
GET https://api.openstreetmap.org/api/0.6/node/223240985/18
GET https://api.openstreetmap.org/api/0.6/node/1341712258/2
GET https://api.openstreetmap.org/api/0.6/node/674055923/7
GET https://api.openstreetmap.org/api/0.6/node/31446843/26
To improve performance, it would be great to obtain them in a single call:
GET https://api.openstreetmap.org/api/0.6/nodes?nodes=618158454/6,223240985/18,1341712258/2,674055923/7,31446843/26
Would it be acceptable to enhance node_controller#nodes with this feature? Depending on whether the version is present or not, either a Node or an OldNode would be fetched.
The text was updated successfully, but these errors were encountered:
When reverting a changeset (e.g., using the JOSM plugin
reverter
), one needs to obtain a large number of objects in a specific version. At the moment, those are obtained sequentially one by one:To improve performance, it would be great to obtain them in a single call:
Would it be acceptable to enhance
node_controller#nodes
with this feature? Depending on whether the version is present or not, either aNode
or anOldNode
would be fetched.The text was updated successfully, but these errors were encountered: