This is a static archive of our old OpenStreetMap Help Site. Please post any new questions and answers at community.osm.org.

OverpassAPI returns a file with old data

0

Hi all.

1) I updated this relation: https://www.openstreetmap.org/relation/4661740
2) Then I send a query: http://overpass-api.de/api/interpreter?data=node(337580513);is_in;out;

In the file within area 3604661740 I don't see any updated info. Is there any delays between OSM and overpass? How long?

asked 11 May '16, 16:47

bear_ukraine's gravatar image

bear_ukraine
41●3●3●6
accept rate: 0%

edited 11 May '16, 16:52

One Answer:

3

You can find the exact timestamps in the Overpass API response, in particular in the attribute values osm_base and areas.

<meta osm_base="2016-05-11T17:18:02Z" areas="2016-05-10T06:41:02Z"/>
  • osm_base refers to the timestamp, when nodes, ways and relations were last updated on the server by applying minutely diff files. Usually the delay will just be a few minutes.
  • areas refers to the timestamp, when the area creation job on the server started to run the last time. The lag can be between 24 and 48 hours at the moment. This is subject to changes in the way the update job runs on the server. Reason being that this is quite a resource intensive task, which needs some time to finish.

Just have a bit of patience, your changes will most likely be reflected in the areas by tomorrow.

answered 11 May '16, 18:24

mmd's gravatar image

mmd
5.7k●1●53●88
accept rate: 37%

edited 11 May '16, 18:28

Just want to mention that in my case it was needed to wait ~48 hours

(18 May '16, 15:37) bear_ukraine

The area creation lag was addressed in the following Github ticket: https://github.com/drolbr/Overpass-API/issues/141 - However, the delta solution mentioned there is not yet productive. In the ticket you will also find some comparison chart from last summer.

(19 May '16, 20:35) mmd

Source code available on GitHub .