tyrasd / overpass-turbo

A web based data mining tool for OpenStreetMap using the Overpass API.
https://overpass-turbo.eu
Other
920 stars 130 forks source link

GUI hangs when using "out meta noids;" #547

Open ltog opened 2 years ago

ltog commented 2 years ago

I was testing the different output options given at https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#out and believe to have found a bug (on https://overpass-turbo.eu/ ) when using out meta noids;:

How to reproduce:

Use the following query:

nwr({{bbox}});
out meta noids;

The GUI will show:

processing query...
    -> parsing data
    ✓received about 10 kB of data
    ✓calling Overpass API interpreter
    ✓building query

and does not continue...

mmd-osm commented 2 years ago

(side note: probably this issue is very niche. In millions of queries I haven't found anyone using noids)

HolgerJeromin commented 2 years ago

In millions of queries I haven't found anyone using noids

https://en.m.wikipedia.org/wiki/Survivorship_bias Nobody was able to save such a query?

mmd-osm commented 2 years ago

I’m talking about Overpass API server logs here. Overpass turbo getting stuck obviously won’t matter in that case because there are always other clients/users directly sending their query to the API, thereby bypassing overpass turbo.

ltog commented 2 years ago

I have added a table to the wiki documenting the different options, thus giving noids a bit more visibility. But probably it won't change much on a grand scale...

b1tw153 commented 11 months ago

I came here after finding that Overpass Turbo still has this bug. So that's one query using out meta noids;

This won't show up in anyone's logs because I'm using a local Overpass server.

For what it's worth, I was just trying to do a quick check on users who have edited ways that use semicolon separated values for natural=* where one of the values is coastline. It's a small set of data, and it would be easily readable if the node IDs weren't in it.