[Tagging] RFC new role value for recreational routes

Martin Søndergaard sondergaard246 at gmail.com
Thu Aug 12 08:30:48 UTC 2021


I think the addition of a transfer role would be great. I have hiked a lot
in both Denmark and the Netherlands, and it is not uncommon to have ferry
rides along a trail. This results in the hiking distance calculations (for
example on waymarkedtrails) being incorrect, since the ferry ride distance
is included. I have also been on one hike where a train ride was
necessary and the problem is the same.

In this case the data user could technically fix this by not including
ferry routes or railways in the calculation, but currently this isn't done.
And how do you distinguish between a bus ride and simply hiking along the
road. A transfer role would make it explicit and much easier for any data
user to calculate proper distances, while still keeping the routes fully
connected.

And "transfer" is a perfectly fine english word and I think it is more
appropriate than "connection".

On Wed, 11 Aug 2021 at 11:45, Peter Elderson <pelderson at gmail.com> wrote:

>
> Vr gr Peter Elderson
>
>
> Javier Sánchez Portero:
>
>> I think that many alternatives could exist as 'transfer' to join
>> different route sections. Some people could choose a train, others by bus,
>> rent a car,...  I'm thinking about the w:E4_European_long_distance_path
>> proposed to reach Canary Island. You can transfer by plane or by ferry
>> using some different routes. Are you planning to map only one of the
>> possible transfer routes? If one, which? If there are many ones, how will
>> you deal when there are many subjective options (you can go by motor
>> vehicle using the shortest route, the fastest, the beautiest and so on)?
>>
>
> This is about fixed routes where a transfer is part of the route. So it's
> not just a gap leaving it up to the traveler to get to the next section!
> Still it's possible that the route offers several (waymarked/indicated)
> alternatives. This is true for all sections of a route, so no special
> handling needed here. I usually recommend creating one continuous main
> route, the rest are alternatives.
>
> The transfer role makes it possible to enter a recognizable
> transfer section (with different transport, and maybe ways that are not
> accessible for the original transport) into a route relation. Data users
> can then handle this any way they see fit.
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>


-- 
Martin Søndergaard Pedersen
Simonsstraat 108, 2628TK Delft
The Netherlands
+31 (0)6397870004
sondergaard246 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20210812/0e4a09a3/attachment-0001.htm>


More information about the Tagging mailing list