<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">I try to make separate ways for the
river & the admin boundary. People tend to move the rivers
around and when a river is also an admin boundary there is no
visual difference in iD. (I mentioned this (as Thorwynn) in an
issue with iD (initially unrelated) but they ignored it.) <a
href="https://github.com/openstreetmap/iD/issues/6162">https://github.com/openstreetmap/iD/issues/6162<br>
</a></div>
<div class="moz-cite-prefix">(It turned into a long discussion about
admin boundaries also being other things)</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Someone in that thread quoted the wiki
: <span style="color: rgb(106, 115, 125); font-family:
-apple-system, BlinkMacSystemFont, "Segoe UI",
Helvetica, Arial, sans-serif, "Apple Color Emoji",
"Segoe UI Emoji"; font-size: 14px; font-style: normal;
font-variant-ligatures: normal; font-variant-caps: normal;
font-weight: 400; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; background-color: rgb(255, 255,
255); text-decoration-style: initial; text-decoration-color:
initial; display: inline !important; float: none;">"Avoid
connecting boundaries to physical features like woods or rivers.
Sooner or later these features change in reality and get updated
in OSM – but usually the shape of the boundary remains. An
exception is if the boundary is legally defined to be the
physical feature."</span></div>
<div class="moz-cite-prefix">It seemed most in the thread agreed
with this. In my experience the official boundaries from MassGIS
don't always align with the river center or thalweg, and
especially in marshy river areas I have found that rivers-as-admin
borders have been moved far from the official line.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I have always made sure the
"boundary=administrative", "admin_level=X" were on the ways. (only
a few were missing them) I know others think they are not needed,
but the tags are already there and make it easy for a mapper to
distinguish what type of boundary it is.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">-Wayne<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 5/28/2020 5:24 PM, Yury Yatsynovich
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAJbo8cHUR+CdK5yjR9VFQFXGEhtDddg10uVKPonyo7T=HBhGxg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi!<br>
</div>
<div>I was wondering if everybody is comfortable about aligning
towns' borders with the waterways (where the borders actually
go along the waterways) and removing the redundant ways with
tags "boundary=administrative", "admin_level=X" that currently
serve as segments of borders?</div>
<div>For instance, I did it this way here:</div>
<div><a href="https://www.openstreetmap.org/way/809321106"
moz-do-not-send="true">https://www.openstreetmap.org/way/809321106</a></div>
<div>
<div><br>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Yury Yatsynovich</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Talk-us-massachusetts mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Talk-us-massachusetts@openstreetmap.org">Talk-us-massachusetts@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/talk-us-massachusetts">https://lists.openstreetmap.org/listinfo/talk-us-massachusetts</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>