<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 28 Jan 2025 at 20:02, Tom Brennan <<a href="mailto:website@ozultimate.com">website@ozultimate.com</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">> I was also thinking if we separately set official_name https://<br>
> <a href="http://wiki.openstreetmap.org/wiki/Key:official_name" rel="noreferrer" target="_blank">wiki.openstreetmap.org/wiki/Key:official_name</a> where the name is in <br>
> the GNR. It's just that the current use of that tag is only where<br>
> there is a different official name to the one signposted/in common<br>
> use.<br>
<br>
Doesn't seem like a bad idea to set the official_name - is that something that can be done in bulk? I haven't thought through the implications!<br></blockquote><div><br></div><div>It could, though would still need to have some manual review since there's always going to be matching issues.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> We have natural=gorge <a href="https://wiki.openstreetmap.org/wiki/" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/</a><br>
> Tag:natural%3Dgorge documented for a canyon. It's not mentioned on<br>
> that page but on natural=valley <a href="https://wiki.openstreetmap.org/wiki/" rel="noreferrer" target="_blank">https://wiki.openstreetmap.org/wiki/</a><br>
> Tag:natural%3Dvalley it recommends to have one way for the waterway<br>
> and another way for the valley sharing nodes, so I would do the same<br>
> for natural=gorge.<br>
<br>
One challenge with using natural=gorge is that most canyons have multiple sections. So there will be multiple sections of the creek that have natural=gorge. I assume there would then need to be some kind of relation? to connect them together? I haven't done much with relations, so I'm only vaguely familiar with their use.<br></blockquote><div><br></div><div>True. Mindful of <a href="https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element">https://wiki.openstreetmap.org/wiki/One_feature,_one_OSM_element</a> we could still just repeat the tags along each section as we do with waterways or highways, but still they will have gaps so not ideal. Perhaps then <a href="https://wiki.openstreetmap.org/wiki/Relation:multilinestring">https://wiki.openstreetmap.org/wiki/Relation:multilinestring</a> would be ideal, which is analogous to a multipolygon relation. </div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">> You have to make a call if those "made up" creek names like "Firefly <br>
> Creek" are in sufficient use to justify applying them to the<br>
> waterway.<br>
<br>
I probably need to make a map and start putting the creek names on it. Once it gets sufficient traction in the canyoning community, I can then back populate it into OSM :)</blockquote><div><br></div><div>Better than issuing an executive order to the canyoning community directing them to adopt your new name within 30 days.</div></div></div>