I think it's the best AND the easiest solution.
Network configuration type is currently not tagged. Nederland, Belgium and
Germany decided to use rcn exclusively for the cycle node networks. Later
they copied that to rwn for the emerging walking node networks.
We now want to correct that, but we
Why don't you continue to use network=* ? Invent a new value for network=
instead of introducing a new, but confusing tag called "network_type".
I understand that using network_type would be easier. You just add the tag to
the already tagged node networks that are currently using network=rwn.
Mvg Peter Elderson
> Op 4 sep. 2019 om 16:30 heeft Simon Poole het volgende
> geschreven:
>
>
>> Am 04.09.2019 um 15:59 schrieb Peter Elderson:
>> Thanks for the illustrations!
>>
>> network=* gives geographical scope (local, regional, national,
>> international) and transport mode
Am 04.09.2019 um 15:59 schrieb Peter Elderson:
> Thanks for the illustrations!
>
> network=* gives geographical scope (local, regional, national,
> international) and transport mode (bicycle, foot, canoe, horse, mtb,
> ski, skate, )
You know what I'm going to point out.
The redundant coding
Thanks for the illustrations!
network=* gives geographical scope (local, regional, national,
international) and transport mode (bicycle, foot, canoe, horse, mtb, ski,
skate, )
network_type gives network configuration type (chain of ways;
node_network=network of nodes)
The network
On Tue, 3 Sep 2019 16:56:49 +0200, Peter Elderson wrote:
> Tagging of regular cycle route relations is route=lcn for local routes, rcn
> for regional routes, ncn for national routes, icn for international routes.
You probably mean network=lcn instead of route=lcn
> I hope this clears things
On Tue, 3 Sep 2019 16:56:49 +0200, Peter Elderson wrote:
> Op zo 1 sep. 2019 om 12:35 schreef Andy Townsend :
>
> > On 29/08/2019 15:52, Peter Elderson wrote:
> > > LS
> > > With the arrival of cycling node networks, the Dutch, German and
> > > Belgian mappers decided to claim (hijack) the
