You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just wanted to quickly comment on your Overpass example in the README. The reason why this query aborts is not the rate limiting, but the missing timeout parameter you would have to provide. In that case, you can download all highway=cycleway ways in England without any issue.
[timeout:600][out:json];
area[name="England"];
(way(area)[highway=cycleway];>;);
out meta;
This is not to say that working with extracts is a bad idea (quite the contrary), it's just that the explanation is at odds with what's happening here.
The text was updated successfully, but these errors were encountered:
Hi @mmd-osm and thank you for your comments. Clearly, I should study the Overpass API user's manual and osmdata docs much better.
This is not to say that working with extracts is a bad idea (quite the contrary), it's just that the explanation is at odds with what's happening here.
I will run some tests during the weekend and then update the README. Again, thanks for the feedback!
Just wanted to quickly comment on your Overpass example in the README. The reason why this query aborts is not the rate limiting, but the missing timeout parameter you would have to provide. In that case, you can download all highway=cycleway ways in England without any issue.
This is not to say that working with extracts is a bad idea (quite the contrary), it's just that the explanation is at odds with what's happening here.
The text was updated successfully, but these errors were encountered: