Hi, I am sending this type of requests to Overpass API ([http://overpass-turbo.eu/s/8p9][1]): http://overpass-api.de/api/interpreter?data= [out:json][timeout:7]; ( way(around:5000,48.9,2.4) ["highway"~"cycleway|footway|path|track"] ["access"!="private"] ); out geom; It retrieves ways around a certain set of lat/lon. And it works well as long as the number of results is reasonable. Otherwise, the timeout is reached quite easily. For this particular example, the limit seems to be 383 elements in the returned object. I only need the end nodes's coordinates, i.e. `elements.bounds`, as well as `tags.highway`. In this context, do you have any idea I could optimize this request? Maybe only requesting certain elements of the default returned object if it's possible? possible Cheers [1]: http://overpass-turbo.eu/s/8p9

Hi, I am sending this type of requests to Overpass API ([http://overpass-turbo.eu/s/8p9][1]): http://overpass-api.de/api/interpreter?data= [out:json][timeout:7]; ( way(around:5000,48.9,2.4) ["highway"~"cycleway|footway|path|track"] ["access"!="private"] ); out geom; It retrieves ways around a certain set of lat/lon. And it works well as long as the number of results is reasonable. Otherwise, the timeout is reached quite easily. For this particular example, the limit seems to be 383 elements in the returned object. I only need the end nodes's coordinates, i.e. elements.bounds, `elements.bounds`, as well as tags.highway. `tags.highway`. In this context, do you have any idea I could optimize this request? Maybe only requesting certain elements of the default returned object if it's possible? Cheers [1]: http://overpass-turbo.eu/s/8p9

Hi, I am sending this type of requests to Overpass API : ([http://overpass-turbo.eu/s/8p9][1]): http://overpass-api.de/api/interpreter?data= [out:json][timeout:15]; [out:json][timeout:7]; ( way(around:1000,48.9,2.4) way(around:5000,48.9,2.4) ["highway"~"cycleway|footway|path|track"] ["access"!="private"] ); out body;>;out skel qt; geom; It retrieves all the ways around a certain set of lat/lon. And it works well as long as the number of results is reasonable. Otherwise, the timeout is reached quite easily. Given that For this particular example, the limit seems to be 383 elements in the returned object. I only need the end nodes coordinates for the ways that are long enough, nodes's coordinates, i.e. elements.bounds, as well as tags.highway. In this context, do you have any idea I could optimize this request? Only Maybe only requesting only coordinates (no need for certain elements of the street names etc.); requesting only the end nodes; exclude shorter ways? default returned object if it's possible? CheersCheers [1]: http://overpass-turbo.eu/s/8p9

Hi, I am sending this type of requests to Overpass API : http://overpass-api.de/api/interpreter?data= [out:json][timeout:15]; ( way(around:1000,48.9,2.4) ["highway"~"cycleway|footway|path|track"] ["access"!="private"] ); out body;>;out skel qt; It retrieves all the ways around a certain set of lat/lon. And it works well as long as the number of results is reasonable. Otherwise, the timeout is reached quite easily. Given that I only need the end nodes coordinates for the ways that are long enough, do you have any idea I could optimize this request? Only requesting only coordinates (not ways); (no need for the street names etc.); requesting only the end nodes; exclude shorter ways? Cheers

Hi, I am sending this type of requests to Overpass API : http://overpass-api.de/api/interpreter?data= [out:json][timeout:15]; ( way(around:1000,48.9,2.4) ["highway"~"cycleway|footway|path|track"] ["access"!="private"] ); out body;>;out skel qt; It retrieves all the ways around a certain set of lat/lon. And it works well as long as the number of results is reasonable. Otherwise, the timeout is reached quite easily. Given that I only need the end nodes coordinates for the ways that are long enough, do you have any idea I could optimize this request? Only requesting only coordinates (not ways); requesting only the end nodes; exclude shorter ways? Cheers