Closed kapprovalija closed 6 years ago
I'm sure Nils will be along to answer this in more detail soon, but what I do know is that the limits are those of the OpenRoute service
Yep, @carlisle1 is right. See here: https://openrouteservice.org/ratelimits/
It will be quite some time before we can allow higher limits. Towards the end of the year, we'll be able to support continental isochrones.
A workaround I thought about but haven't tried would be to create an isochrone for 60 minutes and then convert it to points so you have a new layer comprising a set of points, each one marking 60 minutes travel time from the origin. If you then use this new layer as the origin for a new set of isochrones, say another 60 minutes, then these isochrones, combined with the original should represent a 120 minute isochrone from the origin.
I'm not sure what the maximum number of points is. I've created isochrones for a layer of almost 100 points before but the API specifies a limit of 5 locations. Does the plugin break requests into groups of 5 and queue them or something?
First of all, I want to say that this is great plugin! I started using it, and it makes routing very fast and easy.
While I was using it I encountered next error.
When I used isochrones with travel time option everything is great until time window is 60 minutes or less. But when I used more than 61 min it reported error: 400 (Parameter 'range=3660.0' is out of range. Maximum possible value is 3600.) Is this intentional limitation or error?
Thanks in advance! Cheers!