<div dir="ltr">I am not opposed to the general concept, however:<div><br></div><div>1) The specific process you plan to use should be documented on the wiki. If it is simple, then this should be easy. </div><div>2) Salt water in Colorado? This seems a little unlikely. I downloaded some of the NHD and I can't see how the original importer determined that these were salt water. There is a possible ftype in the NHD for estuary which would imply salt water, but the features I looked at didn't have this ftype. A mass mechanical edit may simply perpetuate bad data here.</div><div><br></div><div>Mike</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Nov 10, 2021 at 12:53 PM Emil Linus Albrecht <<a href="mailto:admin@sandschmecktgut.de">admin@sandschmecktgut.de</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>
<p>Hi, I was on the Slack yesterday,</p>
<p><br>
</p>
<p>The issue came from an old import and should have been partly
resolved by the importer and will be done. Sorry for not knowing,
before posting to the list.<br>
</p>
<div>Am 10.11.2021 um 20:31 schrieb Andrew
Hain:<br>
</div>
<blockquote type="cite">
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<span style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">This
would clearly be a logical thing to do. It would perhaps be
useful to either add relevant water=* tags (such as
water=lake) to the ways or to flag in a QA check that their
absence is a loose end.</span></div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)"><br>
</div>
<div style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">--</div>
<span style="font-family:Calibri,Helvetica,sans-serif;font-size:12pt;color:rgb(0,0,0)">Andrew</span><br>
</div>
<hr style="display:inline-block;width:98%">
<div id="gmail-m_8200374781611372015divRplyFwdMsg" dir="ltr"><font style="font-size:11pt" face="Calibri, sans-serif" color="#000000"><b>From:</b> Emil
Linus Albrecht <a href="mailto:admin@sandschmecktgut.de" target="_blank"><admin@sandschmecktgut.de></a><br>
<b>Sent:</b> 09 November 2021 19:18<br>
<b>To:</b> Talk OSM <a href="mailto:talk@openstreetmap.org." target="_blank"><talk@openstreetmap.org.></a><br>
<b>Subject:</b> [OSM-talk] Mass-replace outdated water=salt</font>
<div> </div>
</div>
<div><font size="2"><span style="font-size:11pt">
<div>Hi,<br>
<br>
More than 10 years ago, the "Water details" proposal was
accepted. It <br>
included the now well-known tag "salt=yes/no".<br>
<br>
Up to the proposal, the tag "water=salt" was mostly used
for salt <br>
waters. Since its deprecation, the usage has been not
really been added <br>
anywhere and is very slowly getting removed. Currently,
it's mostly <br>
still present in some areas of the USA.<br>
<br>
Since "salt=yes" is now far more popular, I suggest ending
this all with <br>
an automated edit, retagging all "water=salt" to
"salt=yes". What do you <br>
think?<br>
<br>
<br>
Thank you - Emil<br>
</div>
</span></font></div>
</blockquote>
</div>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org" target="_blank">talk@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/talk" rel="noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/talk</a><br>
</blockquote></div>