<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 18/10/2020 07:46, Volker Schmidt
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALQ-OR4+zG8Xft7y58RGhXZcPGYozXq0ntztJa-PhVEC51XBAQ@mail.gmail.com">
<div dir="auto">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, 15 Oct 2020 at
09:46, Martin Koppenhoefer <<a
href="mailto:dieterdreist@gmail.com" target="_blank"
rel="noreferrer">dieterdreist@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div dir="auto">
<div dir="ltr">
<div dir="ltr">Generally, I would propose to only tag
crossing =* on the crossing node, but refrain from
access like tags on this node (no bicycle or foot
tags). The access should be derived from the
crossing ways.<br>
</div>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>This statement is only correct if there are crossing
ways using the crossing node.</div>
<div>However, in practical terms it happens very often that
in a first mapping of a road the foot and/or bicycle
crossings, as they are nicely visible on aerial imaging,
ar mapped, but not the crossing foot- and/or cycle-ways,
mainly because the details are not visible on aerial
imagery or the mapper is not interested, at that stage, in
foot/cycling details. And the distinction, at least in
Italy, between foot-only and combined foot-cycle crossing
are well visable on satellite imagery. Also
traffic-signals are often clearly visible because of the
stop lines. Hence in that first round it is easy to map
crossings and basic crossing types. The crossing way is
then often added later. To me it comes natural not to
remove the existing tagging on a crossing node when I add
a crossing way later.</div>
</div>
</div>
</div>
</blockquote>
<p>But what is the use of adding bicycle=no/dismount for, let's call
it a solitary crossings?</p>
<p>When in a later stage the crossing way is added this information
is not needed and in the first stage it does not add value to
routers.</p>
</body>
</html>