OSM object version on areas

[maxerickson]

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.

[matkoniecz]

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

area['name'='województwo podkarpackie']->.searchArea;
(
node['wikipedia'](area.searchArea);
);
out body;
>;
out skel qt;

fails when

[timeout:2550];
area[wikidata=Q54175]->.searchArea;
(
node['wikipedia'](area.searchArea);
);
out body;
>;
out skel qt;

works?

Both try to use https://www.openstreetmap.org/relation/130957 area

[mmd-osm]

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.

[mmd-osm]

[date:"2022-07-20T11:06:24Z"];
rel(130957);
out tags;

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.

[drolbr]

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.

I'm sorry, I missed that issue. Fixed now.