Extra Info - Surface returns paved instead of grass about openrouteservice HOT 3 OPEN

Thanks for filing the issue. The result from your first example is indeed unexpected and needs to be investigated further. For reference here's the direct link to the OSM way.

As for your other examples, it's actually not a 🐛 but a feature 😂 This is so because in the first case the way which is tagged as highway=service is categorized as WayType.STREET and as such receives the assumed surface type paved according to the logic in WaySurfaceTypeGraphStorageBuilder:

In the case of the cycleway and footway the OSM tag highway=path translates to WayType.PATH which is assumed to be unpaved by the above logic. This happens because tags such as footway:surface or cycleway:surface are currently not being parsed, just the surface one.

from openrouteservice.

As for your other examples, it's actually not a 🐛 but a feature 😂 This is so because in the first case the way which is tagged as highway=service is categorized as WayType.STREET and as such receives the assumed surface type paved according to the logic in WaySurfaceTypeGraphStorageBuilder:

But this is wrong. Not every highway=service is paved. One example could be a driveway which is supposed to be tagged as highway=service + service=driveway, but in many cases is not paved, at least in Poland (wiki).

In the case of the cycleway and footway the OSM tag highway=path translates to WayType.PATH which is assumed to be unpaved by the above logic. This happens because tags such as footway:surface or cycleway:surface are currently not being parsed, just the surface one.

Same as above, highway=path doesn't mean the surface is unpaved. A good example is shared foot and bicycle paths, which are tagged highway=path + bicycle=designated + foot=designated and are often made of asphalt or paving stones (wiki).

Anyway, road classification doesn't imply surface in any case, so I think this feature should be disabled.

from openrouteservice.