<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#333333" bgcolor="#FFFFFF">
<p><font face="Helvetica, Arial, sans-serif">Thank for your reponses
so far. Any views on loosening the constraints on member types
and cardinalities ?<br>
</font></p>
<div class="moz-cite-prefix">Le 05/09/2019 à 19:33, yo paseopor a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CAAVQmZ2Ukw7RoY22cYott_Fe+QW88LkUje_qz1e76=Pe-uac4A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">Using established is the best way, but look at
this, it could be useful<br>
<div><a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Extended_traffic_signs_tagging#Destination_signs"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Proposed_features/Extended_traffic_signs_tagging#Destination_signs</a></div>
<div><br>
</div>
<div>It covers all kind of traffic signs, also destination
traffic signs, so it would be useful for a pedestrian
destination traffic sign description and your routing subject.</div>
<div><br>
</div>
<div>Salut i mapes (Health and maps)<br>
</div>
<div>yopaseopor<br>
</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Thu, Sep 5, 2019 at 9:31 AM
Antoine Riche via Tagging <<a
href="mailto:tagging@openstreetmap.org"
moz-do-not-send="true">tagging@openstreetmap.org</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 bgcolor="#FFFFFF">
<p><font face="Helvetica, Arial, sans-serif">Hello.</font></p>
<p><font face="Helvetica, Arial, sans-serif">We are working
with SNCF, the french railway company, to provide
pedestrian navigation inside and around railway stations
in the Greater Paris area. A dedicated routing engine,
which provides indoor/outdoor navigation and supports
area routing, has been developed – this will be
presented during SOTM in Heidelberg.<br>
<br>
In order to improve the user experience, we want to
provide walking instructions such as "take the exit 'Rue
de Londres'" or "Walk through the gate labelled
'Northern lines'" rather than "Walk 75 metres then turn
left". Our problem is that such waypoints may have a
different name depending on the direction you cross
them. The solution we used is to create, when there is
such an ambiguity, two destination_sign relations
pointing to the same 'intersection' member, one for each
direction with the 'from' and 'to' members swapped. Here
is an example at Juvisy station : the entrance named
'Accès Danton' when walking in (<a
class="gmail-m_-2949418942772282230moz-txt-link-freetext"
href="https://www.osm.org/relation/9471596"
target="_blank" moz-do-not-send="true">https://www.osm.org/relation/9471596</a>)
is named 'Quartier Seine' when walking out (<a
class="gmail-m_-2949418942772282230moz-txt-link-freetext"
href="https://www.osm.org/relation/9471597"
target="_blank" moz-do-not-send="true">https://www.osm.org/relation/9471597</a>).<br>
<br>
I wish to amend the Wiki to explain that
destination_sign relations can also be used for
pedestrian and indoor routing, not just at "crossroads".
Does that require opening a discussion in the discussion
page, or may I just go ahead ?<br>
<br>
Now since the routing engine supports area routing, we
need to loosen some constraints on the members, that are
documented on the wiki and enforced by the JOSM
validator :<br>
1/ allow areas for the 'from' and 'to' members, as in
this example : <a
class="gmail-m_-2949418942772282230moz-txt-link-freetext"
href="https://www.osm.org/relation/9722912"
target="_blank" moz-do-not-send="true">https://www.osm.org/relation/9722912</a><br>
2/ allow multiple 'intersection' members, so that
multiple doors can be referenced by a single relation –
example in Gare Montparnasse : <a
class="gmail-m_-2949418942772282230moz-txt-link-freetext"
href="https://www.osm.org/relation/9823029"
target="_blank" moz-do-not-send="true">https://www.osm.org/relation/9823029</a><br>
3/ allow multiple 'to' members, so that the same
relation can point to both a line and an area, and cover
linear and area routing (no example but I could create
one).<br>
<br>
Are there objections to this proposal ? Do you recommend
to open this subject on the Discussion page or is it
best discussing it on this list ? <br>
<br>
Regards,<br>
Antoine.</font><br>
</p>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank"
moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-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>
</body>
</html>