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

[stevea]

OK, I get a bit closer to good understanding with this.  You want to distinguish between network=lcn (or any other value) and what we might say is network=generic.

I don't understand WHY.  I don't understand HOW THESE DIFFER.  I don't understand why you or a use-case or a renderer or a router would want to distinguish these, as they are all "infrastructure which is more suitable for bicycles than not," so I would insist upon some very sharply documented reasons for we "other people in other parts of the world who use the existing bicycle tagging schemes OSM now uses, and don't seem to have a problem with any of this."

If you were to do this, and have your (new) ability to distinguish BETWEEN, say, network=lcn and network=generic, it still remains true, valid and worthy that a sub-value in key cycle_network=* could specify whether this one is commuter, that one is touristic, the one over here is basic, etc.  Right?

However, and I've said this before (though I do so carefully as it might appear I am rancorously accusing and calling you / others there "lazy," and I'm not), it seems the root cause of this is a lack of development of structure (of EXACTLY this sort) in the cycle_network=* values namespace (perhaps from "DE: on down").  What remains lacking if you have network=generic and the ability to distinguish with cycle_network=* values?  (It seems like absolutely nothing to me, but I do continue to listen).

> On Dec 1, 2021, at 12:44 PM, JochenB <JochenB at wolke7.net> wrote:
> 
> Am 27.11.2021 um 17:47 schrieb Flips:
>> We do not need the key network:type=basic_network
>> Instead we need a key like network=base, network=basis or network=generic
>> 
>> So we will still have the standard key route=bicycle/hiking/...
>> And we get an extra key to separate the touristic routes or any other
>> routes (l*n/r*n/n*n/i*n) from the noname/nonumber/nospecialsymbol network.
>> 
>> Each of this new routes contains only the way-segments between two
>> signposts.
>> This routes can than again be collected in a network-relation like the
>> big one which is now called NRW.
>> 
>> Renderers can than put the lowest priority to this routes and give
>> them a different colour or line-width.
>> 
>> Routing-devices might find a code, so you can choose which routes to
>> follow.
>> 
> That’s exactly what I’m looking for. I almost don't care what the key
> is, the main thing is that you can distinguish the two things.