Consuming highway=path, Take 3

[Tolstoi21]

@Peter_Elderson

@Tolstoi21

there are very few fallback values for any of these highways.

Exactly, and that is what underlies most of the issues.
A tagging scheme to describe all the variations, excellent. But that does not answer the data user’s question: if further descriptive tags are lacking, what do I assume, or do I leave it out altogether? Do I take country-specific notions of what a path/cycleway/footway is, and if so, which countries do I support?

I think the way to go is to define a fixed set of OSM-wide defaults for the descriptive keys.

Okay, now I understood your point! Thank you for responding! True that, though again: I would assume that there are probably very few (mostly access-oriented?) defaults that one can safely assume from the highwaytag alone.

All the other descriptive tags (=designated, surface=, smoothness=, width=, sac_scale=, mtb*=, etc.) will have to be decided and added on a case-by-case basis.