I’ve tried to download some objects via overpass API and got this error message, does anybody know what to do?
Many thanks!
OpenGeofiction
I’ve tried to download some objects via overpass API and got this error message, does anybody know what to do?
Many thanks!
Log in to leave a comment
Discussion
Comment from Luciano on 2 February 2019 at 20:51
I don’t read German well, but I get the general concept, maybe.
Are you downloading into a new (blank) layer or into an existing (locally saved from previous work) layer? In the latter case, you will get inconsistencies over time. It is always best to go into an editing session with a new layer.
Comment from mstr on 2 February 2019 at 21:09
Thank you Luciano for your quick response!
Oh, sorry, was stupid to upload it in German. Here is the english version:
I download it into a new layer, and the error appears both when I do the query in JOSM and when I do it in via overpass-turbo and export
Comment from Luciano on 2 February 2019 at 21:23
That is more interesting.
Could you post the text of the query?
Comment from mstr on 2 February 2019 at 21:42
I found out that it happens only for some queries. At the moment I want to download all rivers in Mergany. If I do that, the error occurs. If I do it only in the east of my country it works (https://opengeofiction.net/#map=18/45.62329/130.69732). Doing it in the west where I’ve edited a river a few days ago the error occurs again (https://opengeofiction.net/#map=16/47.9226/130.0291). It seems to be very strange.
[out:xml][timeout:25][bbox:{{bbox}}];
(
node[“waterway”=”river”];
way[“waterway”=”river”];
relation[“waterway”=”river”];
);
(._;>;);
out meta;
Comment from Luciano on 2 February 2019 at 22:16
I’m puzzled.
The result set is missing version numbers for some objects. I can’t determine a reason.
I’ll forward to Thilo.
Comment from mstr on 2 February 2019 at 22:20
Thank you very much! I was hoping it was just a stupid mistake on my part.
Comment from wangi on 3 February 2019 at 17:02
There was a period of time when the Overpass database wasn’t being updated with the metadata, which has caused this. Got this info from Thilo last May.
Comment from mstr on 3 February 2019 at 17:22
@wangi I think it has to do with the data I’ve uploaded a few days ago.
I don’t know how the overpass database works exactly, but it somehow seems to be corrupt. Shouldn’t it be up-to-date immediately?
I’m able to cause the error:
I’ve modified some nodes in a line and uploaded the change.
Then I download it directly (I get the modified version) and with overpass (I get the old version!)
If I try it again after a few minutes I get the error (in the case I’m using overpass).
Comment from Luciano on 3 February 2019 at 19:58
My understanding is that the overpass database is not in any kind of instantaneous sync with the main database. I don’t know the details of that, though.
And so there could be some corruption of the overpass data, for some reason due to some glitch in the update process.
Comment from wangi on 5 February 2019 at 00:15
mstr, here’s the email I got:
“unfortunately, importing to the Overpass database with the –keep-attic option caused a lot of problems, so I had to disable it. This caused also the metadata do be omitted from the import, which I didn’t notice for a while. Now the –meta option at least is activated again, but nevertheless there was a period where no metadata where added. Of course, the solution to this to have a complete reload of the database, which might be expedient also because a new version of the Overpass software was released recently. OTOH, now with the EU GDPR having gone into effect, it might not be advisable to reveal users’ edit histories to the general public. At least this seems to be the route the OSMF will go about their data. Unfortunately, it doesn’t look like it’s possible to supply the version attribute only without username/timestamp. Things are somewhat up in the air for the moment.”
I no longer use Overpass for downloads.
Comment from mstr on 9 February 2019 at 14:26
@wangi @Luciano Thank you!
No good news that overpass does not work quite well since it is a very helpful tool. I was interested in if it was my mistake or not. But it’s okay, I understand that there are more important issues (at the moment). Maybe in the future…