I've been using OSM2PO and it's a great system so far.

However, in version 4.5.2, I can't seem to ignore the one-way restrictions for calculating walk distances.

In the browser version, I check on "Ignore Restrictions" and "Ignore OneWays", but it makes no difference and still obeys the one ways, creating a longer/further walk time than is necessary.

I have tried various settings in the config file, such as these, but they don't seem to help:

graph.build.excludeWrongWays = true graph.support.segments = true graph.support.edgeflags = true graph.support.reverse = false

Am I missing some kind of setting that disables oneways? Could I have done something in the build phase which would have prevented this?

Thanks for your help!

I've been using OSM2PO and it's a great system so far.

However, in version 4.5.2, I can't seem to ignore the one-way restrictions for calculating walk distances.

In the browser version, I check on "Ignore Restrictions" and "Ignore OneWays", but it makes no difference and still obeys the one ways, creating a longer/further walk time than is necessary.

I have tried various settings in the config file, such as these, but they don't seem to help:

graph.build.excludeWrongWays = true
graph.support.segments = true
graph.support.edgeflags = true
graph.support.reverse = false

Am I missing some kind of setting that disables oneways? Could I have done something in the build phase which would have prevented this?

Thanks for your help!