-
Notifications
You must be signed in to change notification settings - Fork 45
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
Autosplit large queries #254
Comments
Thanks @Mashin6, I've actually got code elsewhere that does exactly that. The handling of duplicates is already in-built via the |
I've never wrote a vignette, but I could give it a try. By general procedure you mean how to split bbox, run several separate queries and then manually merge the results into one? A solution to the extensive server load could be restricting this type of querying to kumi OP only. They don't really have any restrictions about usage. |
@Mashin6 yes, a vignette on splitting a bbox, running separate queries, and merging results is exactly what i mean. I've started a generic vignette template in #262 - feel free to extend however you like. If you do contribute, please make sure you add your name both to the |
Currently if query times out or runs out of memory the request is terminated. Given that the amount of data in OSM is growing it might be worth thinking about how to help user in these situations.
A possibility is that if a query fails, the bbox is split in the middle into four equal rectangles and each are submitted one after another. If any of them fails then it is recursively split until the correct size is reached when the query successfully retrieves data.
Similarly as here:
https://github.com/ZeLonewolf/osm-overpass-scripts/blob/7bf5ff10948f50ee5f1e33b08a9d0852274094fb/get_tag_density_map.sh#L139
Notes:
The text was updated successfully, but these errors were encountered: