Long distance isochrones


is it possible to create isochrones for travel times above 60 minutes? Would it be possible to find out, what destinations are reachable within, say, 6 hours, from a given location? I am using the web service, in case it is relevant.

Thank you

I just found this: https://openrouteservice.org/restrictions/
Maximum range time is 60 minutes.
No way to overcome this limitation, I assume?

Hi @ffichtner,

currently not but we are working on an improvement to allow up to 360 minutes - we might be able to release this within the next 2 months, so please stay a little tuned :slight_smile:

Cheers, Tim

1 Like

Hey Tim,

thank you for the information. Sounds promising. I will definitely keep an eye on your project!


Hola, se encuentra disponible la mejora de la opción?

Hi @Ariel,

Please post in English so most people understand your post.

Sadly the implementation for long distance isochrones still needs major refactoring until it can be released and it keeps being pushed back because of higher priority issues.

We currently can’t say when it will be implemented.

Best regards

Hi timothy,
Could you please tell us if there are any news about the expected improvement of isochrones for travel times up to 360 minutes?
It would be very useful for many users!!! Also a beta version, not fully tested would be really ok (I could give you feedback, of course)…
I would be also willing to contribute, if needed and welcome, of course!
Best Regards


new isochrones are in a late stage of dev already. We have tested them for car and hgv and they work well, giving sub 30s request times for isochrones with 3+ h of reach.
We are planning on releasing them before July.

Hi Hendrick,

When you release the new isochrone feature, will there be are hard limit at 360 minutes? Or, can you go longer if you are willing to wait for the computations to finish?



There’ll still be a hard limit. Whether it’ll be at 6 hours or less we can’t tell yet. It’s all about server resources. If you install ORS yourself, you can try 6 hours right now.


Thanks for the idea. With 6.1, we’re seeing 3-5 min for a 6 hour isochrone. If I wanted to try your faster version before it is published, which branch would you recommend: fastisochrones-remove-contraction or fastisochrones-rebase?



Not sure… @HendrikLeuschner is there a out-of-the-box workable branch?

Then it’d be hard to offer support @eeilerts , so you’d be on your own for a while, until it’s fully tested and production-ready.

And thanks for the info, never tried that myself!


Thanks. Happy to work unsupported trying it out. Just curious about @HendrikLeuschner two fastisochrone branches.



fastisochrones-remove-contraction if you want to try it out yourself. You do need to specify additional parameters in the app.config, though. It is mainly adding a weighting parameter to the isochrones field, e.g.

isochrones: {
        enabled: true,
        weightings: "fastest",
        # possible values for maximum_range_distance and maximum_range_time are an integer or a list of values specifically defined for each profile
            {profiles: "any", value: 1000000}
            {profiles: "driving-car, driving-hgv", value: 1000000}
            {profiles: "any", value: 360000}
            {profiles: "driving-car, driving-hgv", value: 360000}
        maximum_intervals: 10,
        maximum_locations: 2,
        allow_compute_area: true

Let me know whether it works. Should create some additional files in your graphs folder.
If you really want to dig into the workings, there is a file calles FastIsochroneParameters.java where you can set some parameters. But that is generally not necessary.


Thanks! I’ll give it a try.