The Overpass QL language is the most...bizarrely constructed language I've ever had to use. It's a bit hard to believe that the person who designed the language thought this was a perfectly reasonable statement:
(._; >;);I then promptly forgot everything and find the syntax very annoying again nowadays... seriously, it's weird remembering having knowledge but not having the knowledge itself anymore
I'm a really big fan of clear and legible code. I'm not at In-n-Out with a secret menu. I'm trying to make changes/updates to code someone else wrote. I don't care how clever they felt they were by using esoteric shortcuts that might make things short and fit on one line. I want to be able to read the code and follow what it does in the least amount of time. Now, if the compiler makes different/better decisions when reading something like that vs much more legible code, we can maybe have a discussion.
Depending on the use case, the shortcut is often to add `geom` to the print statement, so instead a line with the above and a line with `out;` you just write `out geom;`.
Could even make prompts like "Can you find the buildings closer than 500m to a café?"
This is sad because overpass is extremely powerful tool.
I’ll give the tutorials other commenters linked a try.
OK, I had a hard time understanding that the link given above is the demo of this paper.
https://overpassnl.schumann.pub.
Very interesting. Quite surprising too : it can find non trivial searches like "bars with darts" ("bars à fléchette" in French), but not easy ones ("fromagerie" or "dermato").
More complex queries did not work : "cafes close to the river" returned nothing, neither did "touristic site close to a pedestrian area" or "touristic streets".