Has it worked?

Well, it would be interesting to hear if you’ve got any feedback from new mappers? Did they find the welcoming message useful/interesting/helpful?

The message is not customised as from the beginning

I used to monitor my area for new mappers for some time, try to guess what they’re most interested in and sent them some customized hints. Certainly, that approach doesn’t scale at all, but it would be interesting to if such targeted hints would be more effective, or if it just doesn’t matter.

btw: the project’s name was changed to OpenStreetCam very recently : see https://lists.openstreetmap.org/pipermail/talk/2016-November/077058.html and osm.wiki/OpenStreetCam

Forgot to mention that there are already some QA tools out there reporting railway crossings without tag. As an example here’s a link to keep right! As the source is freely available you might take a look how their analysis looks like.

Another route for your data would have been Overpass querying for highways sharing a node with a railway.

That’s fairly easy to find out, actually: http://overpass-turbo.eu/s/jLw

Getting those missing intersections is a bit trickier: http://overpass-turbo.eu/s/jLx - showing railways in blue color and highways in red. There’s some glitch in the query I left as an exercise to the interested reader. Make sure to zoom in quite a bit, otherwise highways and railways cancel out each other in some cases.

I’m quite sure we should be able to do a single Overpass API query to get the pubs of London (as centroids for ways).

Since you asked: http://overpass-turbo.eu/s/gDj -> returns the same list in CSV format

Cheers

GPSBabel has some option to split GPX tracks based on distance/time, see online docs, option ‘sdistance’. Maybe worth a try to get rid of the noise.

Thanks for testing the Multiple user support for (user:…) and (uid:…) in your overpass turbo query. Hope you found it useful :)

Zu Zeiten als JOSM 59xx noch (un)freiwillig das genutzte OS im Changeset übertragen hat, haben die dt.sprachigen Mapper 3-4x soviele Edits (“num_changes”) mit Windows im Vergleich zu Linux gemacht. Mac hängt in der Tat etwas hinterher. Lässt sich mit 2-3 Zeilen Sql recht einfach ermitteln. Vielleicht ist da talk-de nicht (mehr) repräsentativ genug.

Why not use case insensitive search rather than listing all variations in the regular expression?

http://overpass-turbo.eu/s/dnw

Quicklink for the query above: http://overpass-turbo.eu/s/bGQ

Note: complete is not yet part of the official Overpass API and only included in the Overpass Lab Preview version at this time. An official release date is not known as of today. Read more about it. Please add comments/feedback to the GitHub ticket.

Hinweis: das complete Feature ist noch nicht Teil der offiziellen Overpass API, d.h. die genannte Query läuft in der Form nur auf der Overpass Lab Preview Version unter dev.overpass-api.de. Mehr Details dazu.

Thanks for an interesting Overpass use case.

Please note that the Overpass API dev instance you used to pull out your stats only dates back to March 2015 (unlike the official Overpass API instance, which has all the object versions back to September 2012).

This might skew your figures a bit: let’s assume a node has been created in Jan 2014 and last touched in Feb 2015. The dev instance would could recognize it for Feb 2015. as the Jan 2015 version is not known (it was no longer part of the March 2015 planet file I used to initially set up the database).

This restriction is documented on the following wiki page: link

As overpass can’t count tags (yet), it’s not possible to use overpass to get your original list of ids AFAICS.

That’s correct. At this time, there’s only a GitHub issue as feature request:

https://github.com/drolbr/Overpass-API/issues/197

Feel free to comment, if you like.

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