Update trekking.brf

[maciejs]

#743

[polyscias]

Repeating here what I wrote in #746:

I do think it is not a good idea to set the penalty for foot=use_sidepath to 10000, i.e. the same as no.

Not all Openstreetmap data is correct and especially for short segments around crossings I have seen foot=use_sidepath set incorrectly.

10000 means that brouter will never include the way, instead I suggest to set a high penalty like 100 so the algorithm will still have the option to chose it if there is foot=use_sidepath but no suitable sidepath.

Where for bicycle this is less a problem, as the fall back is pushing the bike i.e. foot with this foot change there is no fall-back.

[quaelnix]

@polyscias, I was also sceptical at first, but this change only affects a small subset of one-way streets, and it does work well.

[polyscias]

If "it works well" is your criteria, 100 also works well:

[quaelnix]

I think 10000 is acceptable in this case, but I would also agree with 100. However, the routing and code example you showed belongs to: #746

[maciejs]

@polyscias @quaelnix Thank you for your suggestions, I have updated the value

[quaelnix]

@afischerdev, are you ok with this change?

[afischerdev]

@quaelnix
I don't mind. But the result looks different to the sample above

I could merge if wanted. So we could go on with #753, #743

[maciejs]

@quaelnix I don't mind. But the result looks different to the sample above

I'm not sure if this was an actual change proposal or just for demo, @polyscias could you clarify?