[Tagging] Feature Proposal - RFC - value 'basic_network' for keys 'network:type', 'lcn' and 'lwn'

Peter Elderson pelderson at gmail.com
Tue Nov 16 08:07:28 UTC 2021


Vr gr Peter Elderson

JochenB:

> In the case of node networks, 'network: type=*' is already used
> successfully. There, 'network:type=node_network' describes the type of
> signposting.
>

No, it doesn't! It describes the type of network using labeled Nodes and
Node2Node connection routes to guide the walker, cyclist, horse rider etc
through the area along a prescribed list of labeled Nodes. Each labeled
Node points with labeled arrows to the adjacent Nodes, so the user just
needs to follow the arrow to the next Node on the list (or node strip).
Operators tend to vary a lot in how the signposting is done, but that is
superficial; it's the guidance system that counts, and that is what the
tag is for.
The tag network:type=node_network sets the Node2Node routes and the labeled
Nodes apart from other routes and routing systems, and is used by data
users for specific rendering, planners and network maintenance tools. It
does not imply a specific implementation, a specific design or type of
labeling or signposting; that is up to the operator. In some regions, the
Node network signage is integrated with other types of signage into one
overall signposting design.

The network:type key allows for other values for other specific planning &
guidance systems. I think destination based planning and guidance is
regular routing and navigation, and in itself does not need any special
tagging.

I am fine with tagging <transport>_network for national, regional and local
network plans. Most of those I see as road preference systems, aimed at
channeling traffic. I would translate that into some kind of quality
indicator, to be used as a weight indicator for routing. If it is a
collection of predesigned routes, typically with route labels and
indication of an operator, that's where the <transport_network=* can be
applied, I think, even though I personally don't really care whose route it
is if I'm on the road.

But is it worth it to break down the road system into pieces between every
guidepost,create route relations for all the pieces, and labeling all these
chunks with a *_network=* value? It's a lot of work, it's a lot of
never-ending maintenance, and what does it actually achieve?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20211116/6b2fe535/attachment.htm>


More information about the Tagging mailing list