<html><head></head><body><div class="ydp10e303cdyahoo-style-wrap" style="font-family:verdana, helvetica, sans-serif;font-size:13px;"><div dir="ltr" data-setdir="false"><div dir="ltr" data-setdir="false">Indian Arm est effectivement un exemple où ses contours sont aussi définis dans Burrard Inlet et Osmose ne rapporte pas de problème.</div><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><span>Indian Arm (8330415) <a href="https://www.openstreetmap.org/relation/8330415" rel="nofollow" target="_blank">https://www.openstreetmap.org/relation/8330415</a></span></div><div dir="ltr" data-setdir="false"><span>Burrard Inlet (8330512) <a href="https://www.openstreetmap.org/relation/8330512#map=11/49.3520/-122.7077" rel="nofollow" target="_blank">https://www.openstreetmap.org/relation/8330512#map=11/49.3520/-122.7077</a></span></div><div class="ydp10e303cdsignature"><div><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;"> </span></div><div dir="ltr" data-setdir="false"><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;"></span>Je vais poursuivre la révision pour remettre les contours extérieurs des Estuaires comme ils étaient auparavant.<br></div><div><br></div><span style="font-style:italic;color:rgb(0, 0, 191);font-weight:bold;"><font style="background-color: inherit;" face="garamond, new york, times, serif">Pierre </font><br></span></div></div>
<div><br></div><div><br></div>
</div><div id="ydpf28bb39dyahoo_quoted_7771130146" class="ydpf28bb39dyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
Le vendredi 11 mars 2022, 16 h 23 min 14 s UTC−5, David E. Nelson via Talk-ca <talk-ca@openstreetmap.org> a écrit :
</div>
<div><br></div>
<div><br></div>
<div><div id="ydpf28bb39dyiv5333118371"><div><div><div>Hence another reason for me using "one point, one name". It would forestall data quality assurance tools such as Osmosis from throwing such errors.</div><div><br clear="none"></div><div>I do not know if we have any existing explicit examples of such a hierarchy, but as a couple of implicit examples, you have the Saguenay Fiord as a child of the St. Lawrence River Estuary in Quebec, and you have the Indian Arm as a child of the Burrard Inlet in British Columbia, which itself is a child of the Strait of Georgia. And I do not particularly believe that you can be in both Burrard Inlet and the Strait of Georgia at the same time.</div><div><br clear="none"></div><div>Perhaps relations with type "boundary" should be used to refer to bodies of seawater that have at least one child, as the role "subarea" is valid for boundary relations, while "multipolygon" relations are used for the lowest level bodies of seawater, those with no children at all.</div><div><br clear="none"></div><div>- David E. Nelson<br clear="none"><div id="ydpf28bb39dyiv5333118371yqt55948" class="ydpf28bb39dyiv5333118371yqt6341366437"><div><br clear="none"><div class="ydpf28bb39dyiv5333118371elided-text">On Mar. 11, 2022 11:55, Pierre Béland <pierzenh@yahoo.fr> wrote:<br clear="none"><blockquote style="margin:0 0 0 0.8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div style="font-family:'verdana' , 'helvetica' , sans-serif;font-size:13px;"><div><div><div dir="ltr"><div><div>
Le jeudi 10 mars 2022, 18 h 04 min 15 s UTC−5, David
E. Nelson via Talk-ca <talk-ca@openstreetmap.org> a écrit :
</div>
<div><br clear="none"></div></div></div><blockquote><div>A simple parent-child approach can be used to associate side bays with
larger straits, gulfs or seas, either explicitly by adding the side bays
to the larger bodies as child relations, or implicitly by observing
that if that you can only enter a small bay from the open ocean by boat
by passing through a larger seawater body, such as a sea, strait or
gulf, then that small bay is a child of the larger seawater body. </div><div><br clear="none"></div></blockquote><div dir="ltr">Si nous retracons les estuaires comme ils étaient originalement en suivant les contours de la rive, nous aurons :</div><div dir="ltr">1. premier niveau hiérarchique avec relation-polygone correspondant à l'estuaire</div><div dir="ltr">2. des relations-polygones qui définissent chenaux et baies (natural=[bay|strait]).</div><div dir="ltr"><br clear="none"></div><div dir="ltr">Avec une telle définition, les polygones vont se superposer et il est possible que les outils de qualité tels que Osmose vont indiquer comme erreur cette superposition des polygones ce qui amenera des contributeurs à venir constamment réviser ces infos.</div><div dir="ltr"><br clear="none"></div><div dir="ltr">A-t-on des exemples existants de telle hiérarchie des différents polygones estuaire, baie, etc ?</div><div dir="ltr"><br clear="none"></div><span style="font-style:italic;color:rgb( 0 , 0 , 191 );font-weight:bold;"><font style="background-color:inherit;" face="garamond, new york, times, serif">Pierre </font><br clear="none"></span></div></div>
<div><br clear="none"></div><div><br clear="none"></div>
</div><div>
<div style="font-family:'helvetica neue' , 'helvetica' , 'arial' , sans-serif;font-size:13px;color:#26282a;">
<div>
Le jeudi 10 mars 2022, 18 h 04 min 15 s UTC−5, David E. Nelson via Talk-ca <talk-ca@openstreetmap.org> a écrit :
</div>
<div><br clear="none"></div>
<div><br clear="none"></div>
<div><div><div><div><div>There wasn't a consensus that my method was unacceptable either, which left me with no such guidance on this. If I was to rewind time and do this over again, I probably would have reached out to the community first, perhaps even put a project page on the wiki, and reached out for such guidance. But obviously, as you can see, I leapt before I looked. Such is the benefit of hindsight.</div><div><br clear="none"></div><div>There are two very simple reasons I used a "one point, one name" system for mapping bodies of seawater. First, I wanted to minimize my own interference with editors wanting to work on the coastline. If they choose to edit the coastline, perhaps splitting or joining parts of it, without downloading any relations first, it would minimize the time I would have needed to subsequently fix up the seawater relations, as as few of the seawater relations would have ended up broken. Second, it is a "divide and conquer" approach, meant to divide the coastline into logical parts so that as few member ways as possible would need to be used to form each of the seawater areas. A simple parent-child approach can be used to associate side bays with larger straits, gulfs or seas, either explicitly by adding the side bays to the larger bodies as child relations, or implicitly by observing that if that you can only enter a small bay from the open ocean by boat by passing through a larger seawater body, such as a sea, strait or gulf, then that small bay is a child of the larger seawater body. I did not mean at all for this scheme to imply any false shapes for seawater bodies.</div><div><br clear="none"></div><div>- David E. Nelson</div></div></div></div></div>
</div>
</div></div></blockquote></div><br clear="none"></div></div></div></div></div></div><div class="ydpf28bb39dyqt6341366437" id="ydpf28bb39dyqt86310">_______________________________________________<br clear="none">Talk-ca mailing list<br clear="none"><a shape="rect" href="mailto:Talk-ca@openstreetmap.org" rel="nofollow" target="_blank">Talk-ca@openstreetmap.org</a><br clear="none"><a shape="rect" href="https://lists.openstreetmap.org/listinfo/talk-ca" rel="nofollow" target="_blank">https://lists.openstreetmap.org/listinfo/talk-ca</a><br clear="none"></div></div>
</div>
</div></body></html>