Consider surfaces wood and metal as ispaved

[mapper-of-openstreets]

On many cycle paths there are often small bridges that have wood or metal as a surface. Unfortunately, these cycle paths are currently often disadvantaged or even excluded from routing because the surface is not considered "ispaved".

It would be great if the surfaces wood and metal in the different profiles were also considered as "ispaved".

[poutnikl]

Before eventually implemented in official BRouter/BRouter-web profiles, you may want to try the latest development version of my Bicycle profile template, that is ( rather will be ) functionally identical with the ( future ) baseline profile Brouter-dry.

assign ispaved surface=paved|asphalt|concrete|paving_stones|metal|wood #metal, wood added in v2.7

[mapper-of-openstreets]

Thanks a lot! That's very nice. It would be cool if wood and metal would also be considered in the road bike (fast bike) profiles.

[poutnikl]

I agree the Fastbike could have them too, but it is on Arndt.

About my template, try to set MTB_factor to -1.0 - -2.0 instead of default 0.0 and it would be close. ( Trekking-fast has -0.5 ). Positives are toward MTB, negatives toward fast bikes.

[poutnikl]

After having seconds thoughts, surface=metal|wood should have added explicit smoothness=, as the surface can be perfectly comparable to smooth asphalt, but also perfectly comparable to cobble stones or gravel. So it could conditionally fit to all paved/unpaved/3rd_state categories.

Another thought is, that explicit unpaved surface should never be completely forbidden. With a proper penalty, they would not be taken as a road, but short patches like bridges would not be avoided.