Make the Public transit isochrones more relevant


Here’s my use case:

We are using GraphHopper to generate public transit isochrones around a point. The isochrone generated is used to return a list of geographical points.

With the current status of the public transit isochrones, it’s nearly impossible to get the optimal isochrone since a start datetime has to be submitted to generate it.

The issue we would like to overcome:

In a perfect situation, there would be no required start datetime when generating a public transit isochrone. I am assuming that the initial wait time for the reached transit stops would need to be ignored.

I have spent time attempting to understand the transit isochrone generation but my lack of knowledge of the routing engine is slowing me down.

I’m interested in contributing to the project with minor guidance from the maintainers.

Thanks in advance for your help on this!

Powered by Discourse