[Tagging] cyclist profiles - was:Feature Proposal - RFC - value 'basic_network' - cycle_network?

[JochenB]

Am 01.12.2021 um 23:05 schrieb stevea:
>> It needs a feature by which e.g. a renderer can easily recognize whether
>> the relation / path belongs to type A or type B.
> So, this really IS "tagging for a renderer," right?
When I tell a freeway per tag that it is a freeway, I do that so that
the render can show the freeway as a freeway. So we all tag for renderers

It is reprehensible to tag a dirt road as a motorway because it looks
better on the map.


>> This should not be done
>> based on the network names in e.g. B. in 'cycle_network', because the
>> name can be different in each region.
> Of course it can!  But this isn't a problem, because each region has the ability to say "OUR part of the namespace (e.g. of cycle_network values) means that we use THIS name here, while over there in THAT part of the namespace (e.g. another country, region or locality), we use ANOTHER name.  (Because we can, and appropriately DO, since it has been "carved up" so that these values are understood in any given country, region or locality).  This can only happen as the cycle_network=* namespace has had the time to have its values, for any country, region or locality, agreeably "carved up" into these values (including what I'm suggesting are sub-values that denote PURPOSE of the network in that country, region or locality).  Yet, it appears to remain true that this "work" (early suggestions, development, agreement, consensus) has not happened.
>
>> A simple key 'xyz = A' is required
>> and not a key that contains long texts that have to be interpreted.
> No, I don't believe this is correct.  You might believe it is true because of the ease with which "a renderer or router can grab this as a simple 'one-off' parsable string and know definitively that THIS is one of THOSE."  But that is the very definition of "syntactic sugar," something I think OSM (and especially participants in this tagging list) wish to avoid.  Scrupulously avoid.  (Hence what feels like one of the longest threads I've ever seen).

I do not believe that a majority prefer to hide a simple property in a
key, the content of which is designed differently in each region, in
which freely defined names are separated from one another and put in
order with a colon, the key names of which do not infer the property and
where a data evaluator first has to program regionally specific special
loops in order to filter out the individual property from many different
types of information.

With every line in which you advertise the 'cycle_network' it becomes
clearer to me that 'color=green' is better than 'xxx_network=yyy:green:zzz'


>> This
>> key should also not be region-specific.
> Why not?!  It IS region-specific!  We (in the USA) don't have these here.  And why a key, when values will do?

Why do we tag motorways around the world with the same tag, we could do
it differently in each country?

I stop here.