Seems to me that AbstractFlagEncoder:handleNodeTags in combination with adding the possibly bike-ok barriers to potentialBarriers would be the way to go? Not sure how to get the current encoder there, though and if the best practice would actually be to hardcode the specific conditions there...
As a side remark, I used routino for a long time (still do for areas outside D-A-CH since the DB it creates is much smaller and fits on my server), there, all these rules are externalized into a quite elaborate XML. 2015-05-08 10:39 GMT+02:00 XCTrails <[email protected]>: > we have indeed marked some barriers as 'absolute' barriers where even a >> tagging won't help I think: >> >> https://github.com/graphhopper/graphhopper/blob/master/core/src/main/java/com/graphhopper/routing/util/BikeCommonFlagEncoder.java#L84 >> > > yep, I already found that and commented it our for my server. But I'm not > deep enough in your code to make any guesses as to what the best fix would > be. > > >> Please create an issue for this if you think this should be improved. >> > > Done: https://github.com/graphhopper/graphhopper/issues/407 > > cheers, > Armin > >
_______________________________________________ GraphHopper mailing list [email protected] https://lists.openstreetmap.org/listinfo/graphhopper
