[FEATURE] <feature request>

[jedalong]

Hi Mark et al! I am working on building some simple automated tools for combining OSM data with animal tracking data for movement ecology problems (e.g., where and when did the chicken cross the road?). Package osmdata is perfect for this!

One constant issue we run into is that query calls are too large if the bounding box (or volume of features requiested) are too big. But these issues are all situation dependent. Is there any tool/method for in advance getting an estimate of query size that can be used to guess if a query will time out / throw an error (or estimate how long it will take)?

Specifically, what I'm interested in knowing is if there are ways to a priori estimate where queries need to be split, made smaller etc or if that is simply something you find out after trying and failing...

SIDENOTE: The query splitting workflow from vignette 4 was not working as expected (for me), but i can explore what was going wrong when i get a bit more time and provide proper feedback there...

Cheers Jed