@ratrun I found this old topic due to the other issue 
De-prioritize highway=track missing further details for bicycle profile by ratrun · Pull Request #3196 · graphhopper/graphhopper · GitHub
I found that several cases regarding highway=path are inconsistent (leading to strange differences for e.g. bike and mtb) and will submit a PR shortly to propose a solution.
For the highway=track problem I can imagine that we do not need to add code that makes it more complex and instead we should streamline the current code.
But before I can do this I have some questions as I didn’t find a solution yet (for these problems in my dev branch):
- We have two similar code sections where we handle tracktype and surface and both use different definitions of “is designated for bike” (see priority parser and speed parser). Do you know if there was a reason for this difference?
- Furthermore the handling of tracktype and surface for track and bridleway is different to that of the “pushing sections” (a term which I’m going to change to
slowByDefaultHighways). Why don’t we increase the speed of the “pushing sections” for good surface tags too? Could we add track and bridleway to the “pushing sections“ and have one place for all of them that also handles the surface and not only the tracktype? Or is there a reason we don’t do this?