<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">The 'fish passes' I am familiar with
are all man made, they provide fish a way around weirs, dams and
locks. <br>
They certainly are not intended for human transportation and
should not provide a lot of water flow.<br>
They are different from spillways, canals and other man made
waterways, they are not a sub class to them. <br>
If they are not to be considered part of the waterway key then
possibly they can be added to the key man_made. <br>
<br>
<br>
On 19/07/18 17:57, Javier Sánchez Portero wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAFZgtEhiemj1Jxwa9JeqDNx6xLYS7CxTeK_r=yGpPbF7PorD_w@mail.gmail.com">
<div dir="ltr">
<div>Hello</div>
<div><br>
</div>
<div><span id="gmail-result_box" class="gmail-" lang="en"><span
class="gmail-">I personally prefer a few main values in
the waterway to define the general cases and subtags for
specific cases like this, of the type of usage =
fiss_pass.</span> <span class="gmail-">If I am in front
of an infrastructure of this type, its physical
characteristics will allow me to distinguish if it is a
channel, ditch or brook.</span> <span class="gmail-">If
it was built for the purpose of fish passing it is a
separate issue.</span> Are a fish_pass different in nature
to any other waterway? Waterway different in it's
construction nature could be used as a fish_pass? If the
answers to this questions are no and yes, put the fish_pass
value apart of the main waterway key. <span class="gmail-">This
form seems simpler and more versatile to me.<br>
</span></span></div>
<div><span id="gmail-result_box" class="gmail-" lang="en"><span
class="gmail-"><br>
</span></span></div>
<div><span id="gmail-result_box" class="gmail-" lang="en"><span
class="gmail-"><span id="gmail-result_box" class="gmail-"
lang="en"><span class="gmail-">By the way: in the table
of values added to the wiki there is a strange blank
gap between the blue cells of ditch/brook and
pressurised.</span> <span>Also the culvert cell is
misaligned with respect to the cave cell and others.</span>
<span class="gmail-">Is this intentional and has a
meaning or an error when constructing the table that
can be corrected?</span><br>
<span class="gmail-"></span></span></span></span></div>
<div><br>
</div>
<div>Regards, Javier<br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2018-07-19 8:30 GMT+01:00 Mateusz
Konieczny <span dir="ltr"><<a
href="mailto:matkoniecz@tutanota.com" target="_blank"
moz-do-not-send="true">matkoniecz@tutanota.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<div>In case of waterway=fish_pass I think that a new
waterway is OK as</div>
<div><br>
</div>
<div>- it is drastically different from other defined
waterways</div>
<div>- is not a navigable waterway<br>
</div>
- is not redefining already mapped objects<br>
<br>
17. Lipiec 2018 23:04 od <a
href="mailto:fl.infosreseaux@gmail.com" rel="noopener
noreferrer" target="_blank" moz-do-not-send="true">fl.infosreseaux@gmail.com</a>:
<div>
<div class="h5"><br>
<br>
<blockquote
class="m_-2584506248121573454tutanota_quote"
style="border-left:1px solid
#93a3b8;padding-left:10px;margin-left:5px">
<div>
<div>Hi all,</div>
<div><br>
</div>
<div>A discussion has recently started about
waterway=fish_pass here :</div>
<div><a
href="https://wiki.openstreetmap.org/wiki/Talk:Tag:waterway%3Dfish_pass"
rel="noopener noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.<wbr>org/wiki/Talk:Tag:waterway%<wbr>3Dfish_pass</a></div>
<div><br>
</div>
<div>While writing <a
href="https://wiki.openstreetmap.org/wiki/Proposed_features/Hydropower_water_supplies"
rel="noopener noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.<wbr>org/wiki/Proposed_features/<wbr>Hydropower_water_supplies</a>
it was asked to not clutter waterway=* with
spillway since it was a specific usage of a man
made canal.</div>
<div>Such ideas lead to separate waterway nature,
usage and sometimes supporting infrastructure to
get a tagging model with 3 different
corresponding keys.</div>
<div>A comprehensive table of waterways natures
has been set here : <a
href="https://wiki.openstreetmap.org/wiki/Key:waterway#Values"
rel="noopener noreferrer" target="_blank"
moz-do-not-send="true">https://wiki.openstreetmap.<wbr>org/wiki/Key:waterway#Values</a><br>
</div>
<div><br>
</div>
<div>May it be great to consider usage=fish_pass
with waterway=* (canal, presumably) for sake of
consistency?</div>
<div><br>
</div>
<div>Feel free to read and comment on the Talk
page</div>
<div><br>
</div>
<div>All the best</div>
<div><br>
</div>
<div>François<br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
______________________________<wbr>_________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org"
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.<wbr>org/listinfo/tagging</a><br>
<br>
</blockquote>
</div>
<br>
</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>