Not yet mapped, but my prototype case can be seen in the Bing Imagery with an 
area that collect water around 33.99268,-116.22239 and flows generally to the 
east and north only to dissipate around 33.06076,-116.06077. The collection 
area is no problem nor is the ephemeral waterway until about 
33.03910,-116.099138 where it start bifurcating into smaller and smaller 
channels which eventually disappear.

Cheers,
Tod

> On Aug 12, 2020, at 10:03 AM, Joseph Eisenberg <joseph.eisenb...@gmail.com> 
> wrote:
> 
> Would waterway=spreads only be used for intermittent streams/rivers where the 
> waterway spreads out and evaporates on the surface?
> 
> If the water appears to sink into sand, gravel or fractured karst rock, would 
> we want a different tag instead, e.g. waterway=sink?
> 
> I understand that natural=cave_entrance can also be used when a waterway 
> drops into a sinkhole or other open cave entrance, often found in limestone 
> (karst) geology areas.
> 
> -- Joseph Eisenberg
> 
> On Wed, Aug 12, 2020 at 9:52 AM Paul Allen <pla16...@gmail.com 
> <mailto:pla16...@gmail.com>> wrote:
> On Wed, 12 Aug 2020 at 17:07, Tod Fitch <t...@fitchfamily.org 
> <mailto:t...@fitchfamily.org>> wrote:
> 
> To clarify it for me, the a “waterway=spread” tag would be used on a node 
> (rendered possibly as an asterisk) or on a way? Or either depending the 
> situation?
> 
> I'd say "spreads" rather than "spread" because that's the term OS uses.  I've 
> only
> ever seen OS use it on the terminal node of a waterway.  More of a crow's-foot
> symbol than an asterisk, usually, but an asterisk works.  I have no idea how
> you'd render it sensibly on a way.  I assume you're thinking of something 
> like a
> very sandy river bed where the water sometimes gets further than other times,
> depending on conditions.  I'd be happy enough with a single node, because
> that's better than we have now.  If you can justify applying it to a way and
> think there's a need then do so, but if you're just trying to keep QA tools
> happy...
> 
> --
> Paul
> 
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org <mailto:Tagging@openstreetmap.org>
> https://lists.openstreetmap.org/listinfo/tagging 
> <https://lists.openstreetmap.org/listinfo/tagging>
> _______________________________________________
> Tagging mailing list
> Tagging@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging

Attachment: signature.asc
Description: Message signed with OpenPGP

_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to