New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OSM object version on areas #677
Comments
On looking at it again: is answering what is going on (sorry for image but as this appears as popup there is no way to copy text) Slack question was: Any idea why
fails when
works? Both try to use https://www.openstreetmap.org/relation/130957 area |
Out of date areas seems to be an operational issue affecting both production instances. The xml response should return the exact timestamp of the areas. You can use this information to find out how the relation looked back then. |
would be the respective query. If I'm not completely mistaken, the very first character in the name field was changed to a lowercase character in the meantime. |
I'm sorry, I missed that issue. Fixed now. |
A question on the OSM US Slack arose out of the name of an area falling out of sync with the source relation. Querying for a id based tag that hadn't changed worked as expected, querying by name returned no areas.
Would it break anything to add the version of the source object as an attribute in the xml?
Then there is a least a bread crumb for debugging a seeming inconsistency.
The text was updated successfully, but these errors were encountered: