Question about walk reluctance parameter

[Martin Rohden]

We have a question about the OTP 2.0 which came up during our tests. It looks like the walk reluctance parameter only controls the walk parts within trips, but not at the beginning or end. We sometimes get a string of results, where some trips are combinationa of bus and tram with small walking parts at the beginning and end and also in between the trip. These are the the results we want to get.

However, in addition to that there are also many other results with very long walking parts at the beginning and end of the trip, which we can't seem to get rid of. The walk reluctance parameter doesn't help here.

Does someone here has a solution for this problem?

Thanks,

Martin

[t2g...@gmail.com]

The `walkReluctanse` should be applied to access, transfers and egress. You should be able to debug your request and investigate the generalizedCost for each leg. The access and egress cost should be your walkReluctance * walkTime. 

Thomas