Hi,
I understand that in the Overpass API world, areas are “virtual” objects that enrich the OSM data and are added by the API to help for some use cases, and that their generation is not real time; currently areas seem to have been last generated on May 20th on overpass-api.de
which I use.
I have a query on the Overpass API that returns areas that refer to multipolygons that were deleted more than a year ago; two examples, the first for the Amedée-Roy Stadium and the second for the Kiwanis Park:
{
"type": "area",
"id": 3611605371,
"tags": {
"leisure": "stadium",
"name": "Stade Amédée-Roy",
"sport": "baseball",
"type": "multipolygon"
}
},
{
"type": "area",
"id": 3613545847,
"tags": {
"landuse": "recreation_ground",
"name": "Parc Kiwanis",
"type": "multipolygon"
}
},
I’m first wondering, is it expected to receive such stale data from the Overpass API?
Then I’m wondering, did I do something wrong that created that situation?
Those two deletions were done by me, using the josm
software to turn (trivial) multipolygons into ways (via the “Reconstruct polygon” feature part of the Relation Toolbox (reltoolbox) plugin). Perhaps the plugin is not thorough in deleting the original multipolygon? Perhaps there is an extra step I should take care of to avoid leaving dangling data behind?
I don’t think the query I send to the API is relevant to the issue, but for sure I can paste it here if you feel it will help.
Thank you for your time and answers,