-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stuck in "rendering geoJSON" #367
Comments
I agree that overpass turbo shouldn't crash on invalid input. But isn't this primarily (?) a bug of the overpass api: drolbr/Overpass-API#463 (falsely returning a deleted way version as not-deleted) |
Yes, exactly, that's what I meant with "Some queries produce really bad data"... :) |
I've just ran into this with the following query:
But it's still the same with the query mentioned in the issue description. |
@gy-mate : I cannot reproduce the issue. On which Overpass instance are you running your query? |
@mmd-osm I'm using The following error appears in the console just when it starts rendering geoJSON:
|
Thank you, I could reproduce the issue for a few minutes only, but now it's working ok again. Note that this issue was originally created for "Error: Invalid LatLng object: (NaN, NaN)". which causes a stuck UI, but likely for different reasons. |
Some queries produce really bad data, triggering error messages like "Error: Invalid LatLng object: (NaN, NaN)" on the javascript console while rendering geoJSON. Unfortunately, overpass turbo gets stuck here forever. It would be better to see at least some of the data (and optionally reporting that there was some issue rendering the result).
Example:
The text was updated successfully, but these errors were encountered: