Die Overpass QL Query sieht wirklich nicht so schön aus. Eigentlich eine gute Gelegenheit, das Proposal von jotpe wieder aufzugreifen und umzusetzen: https://github.com/drolbr/Overpass-API/pull/225

Bitte mal schauen, ob das so funktioniert und ggfs. direkt im Pull request kommentieren. Das ganze funktioniert bisher nur auf der dev-Instanz. Es kann allerdings noch eine geraume Weile dauern, bis es allgemein verfügbar ist.

{{bbox}} is just semantic sugar, which is only defined for overpass turbo (the Web frontend). Overpass API (the server) really has no idea about it.

When you run a query in overpass turbo, {{bbox}} will be automatically replaced by the current bbox before the query is sent to the Overpass API backend.

The translated version will then look like this:

[bbox: 48, 16, 49, 17];

See osm.wiki/Overpass_turbo/Extended_Overpass_Queries for overpass turbo shortcuts.

Do you know OSM Boundaries Map made by user wambacher? That’s probably all you need: https://osm.wno-edv-service.de/boundaries/

I added this example to the Overpass API Examples page for everyone to edit/further enhance as needed.

Don’t worry, it’s in German right now. Feel free to edit the query and add some comments in English if you like.

I’d propose a slightly modified query to allow an “Export to JOSM” from overpass turbo: http://overpass-turbo.eu/s/4YJ

Changes:

• Output format: XML instead of JSON
• Recurse ways to nodes + output with meta information

but some older data/diffs aren’t quite working.

yes, right. During testing some previously unknown issues were uncovered. Unfortunately, the attic data in the current database cannot be fixed that easily, so a full database rebuild is really needed.

I believe Roland wanted to start this task some time in July, if no other issues pop up until then. Processing a full planet and 2 years of history involves a lot of number crunching and will take quite some time (think ‘a couple of weeks’ rather than ‘a couple of hours’).

then roll it out to the (more widely used?) overpass turbo system.

overpass turbo is more like a web frontend and has no OSM database on its own. All the data really comes from Overpass API. Basically, Overpass Turbo helps you create your own overpass query, sends that query to Overpass API and eventually renders the result on a map (to put it very simple).

Once the attic data is fixed on Overpass API (this is the server where the database resides), Overpass Turbo can immediately leverage that data without further ado.

hth

I don’t think the ‘diff’ command is working in overpass turbo yet. But I’m sure it will be available soon

There’s already a Github ticket out there: https://github.com/tyrasd/overpass-ide/issues/80