<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 30/03/19 11:13, Nick Bolten wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAF0zbxUzdwaLYE4bXL7up73AY+=CsWZep+rF4xCdjtncbg4Ekw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div dir="auto">I like the idea of addressing the area-ness of
steps! Thanks for taking the initiative on this. I have a couple
questions and ideas that are hopefully helpful.
<div dir="auto"><br>
</div>
<div dir="auto"># curb (kerb) lines<br>
<div dir="auto"><br>
</div>
<div dir="auto">What would you think of tagging each step way
as a kerb line? e.g., each step way could be barrier=kerb,
kerb=raised, and could have other relevant kerb tags like
kerb:height.</div>
<div dir="auto"><br>
</div>
<div dir="auto">This would make it very easy to know what tags
to use for virtually any curb-like feature in OSM with
non-trivial length: make it a curb line. This would also
dovetail with other curb line conventions, such as knowing
which side is higher (the side on the right of the way).</div>
</div>
</div>
</blockquote>
<br>
Rather tedious to map anything other than a straight line! See the
Queluz National Palace for example. Or relation 9443810 - it turns 3
right angle corners.. <br>
<blockquote type="cite"
cite="mid:CAF0zbxUzdwaLYE4bXL7up73AY+=CsWZep+rF4xCdjtncbg4Ekw@mail.gmail.com">
<div dir="auto">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto"># Determining upper/lower steps + number of
members</div>
<div dir="auto"><br>
</div>
<div dir="auto">The example says you would set one step to
role=lower and one to role=upper. Does this mean that the
relation effectively applies to a single step? </div>
</div>
</div>
</blockquote>
<br>
No. It applies to a set of steps ... you map the top and bottom and
identify each. You could do it .. very small area! For a single step
I'd rather go with your barrier curb idea. <br>
<br>
<blockquote type="cite"
cite="mid:CAF0zbxUzdwaLYE4bXL7up73AY+=CsWZep+rF4xCdjtncbg4Ekw@mail.gmail.com">
<div dir="auto">
<div dir="auto">
<div dir="auto">On a stairway, a single vertical part of a
step could of course serve as both upper and lower, so we'd
need more information if a single relation described the
whole stairway.</div>
<div dir="auto"><br>
</div>
<div dir="auto">As a follow-up, what about using the order of
relation members, like how bus routes do? This might make it
easier to map whole stairways: order = ascending
(literally). You could then use the role to describe
segments if the stairway splits, though a role like role=1
might be off.</div>
</div>
</div>
</blockquote>
<br>
err does not work. They form a closed way. As such one lateral will
be connecting from top to bottom, while the other will be connecting
from bottom to top. <br>
Best to have the direction of the lateral way point upwards, but
even that does not matter as the top is identified by the role in
the relation as is the bottom. <br>
<blockquote type="cite"
cite="mid:CAF0zbxUzdwaLYE4bXL7up73AY+=CsWZep+rF4xCdjtncbg4Ekw@mail.gmail.com">
<div dir="auto">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto"># one-to-one way nodes?</div>
<div dir="auto"><br>
</div>
<div dir="auto">For mapping a step, the proposal says, "Create
2 ways, one for the upper part of the steps, another for the
lower. They should have the same number of nodes and have
the same direction."</div>
<div dir="auto"><br>
</div>
<div dir="auto">I'm wondering why they need to have the same
number of nodes. It seems to me that the Queluz National
Palace example would actually be impossible to map as a
single area this way, since it splits into two stairways at
the top. But I might be misunderstanding the proposal.</div>
</div>
</div>
</blockquote>
Err no you don't misunderstand it. I think it is a function for the
renders to ease drawing of these non linear ways such as the Queluz
National Palace example, connections between the upper and lower way
nodes form the point where rendering lines change direction... <br>
<br>
The Queluz National Palace example needs 3 areas to be defined. But
the present imagery does not have enough definition for me to do
that. I have roughly done th elower bit, the upper two are simple
ways.. <br>
<br>
The Sydney Opera House has quite a few steps - not all of them
mapped. But they are much easier to map being larger + linear and
with the better imagery we have with the NSW LPI Imagery. I have
just done relation 9443810 for a set as mentioned above. <br>
<br>
<br>
<blockquote type="cite"
cite="mid:CAF0zbxUzdwaLYE4bXL7up73AY+=CsWZep+rF4xCdjtncbg4Ekw@mail.gmail.com">
<div dir="auto">
<div dir="auto">
<div dir="auto"><br>
</div>
<div dir="auto"># In combination with one or more
highway=steps ways</div>
<div dir="auto"><br>
</div>
<div dir="auto">It's fairly complicated to route on areas, and
this one in particular seems even moreso. What would you
think of recommending mapping both an area (which is good
for rendering/barriers/advanced routing) and one or more
highway=steps (which is good for routing + network analysis
+ attaching to a building entrance) ways?</div>
</div>
</div>
</blockquote>
<br>
Yep. I think;<br>
the laterals should be tagged as steps - that way they can be used
for routing and hand rails and number of steps. <br>
the upper and lower ways should be tagged as footways - that way
they can be used for routing .. and tactile paving.. <br>
<br>
This would aid routing as any connecting way to any of the ways -
top, bottom or lateral should route. <br>
<br>
------------------ Still thinking on it. Mixed feeling on the
suggestion of providing a central way of steps .. the 2 sides would
handle routing. <br>
<blockquote type="cite"
cite="mid:CAF0zbxUzdwaLYE4bXL7up73AY+=CsWZep+rF4xCdjtncbg4Ekw@mail.gmail.com">
<div dir="auto">
<div dir="auto"><br>
</div>
<br>
<div class="gmail_quote" dir="auto">
<div dir="ltr" class="gmail_attr">On Thu, Mar 28, 2019, 8:06
PM Warin <<a href="mailto:61sundowner@gmail.com"
target="_blank" rel="noreferrer" moz-do-not-send="true">61sundowner@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
<br>
This one has been sitting for a long while! Still not
certain about some <br>
aspects of it.<br>
<br>
See what you make of it.<br>
<br>
<a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Area-steps"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/Area-steps</a><br>
<br>
<br>
Discussion here for preference.<br>
<br>
<br>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" rel="noreferrer
noreferrer" target="_blank" moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer noreferrer noreferrer" target="_blank"
moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>