is 峽 the most common translation for a mountain pass or saddle point?
---

Published using OSMCha: https://osmcha.org/changesets/179335249

is 峽 the most common translation for a mountain pass or saddle point?
---

Published using OSMCha: https://osmcha.org/changesets/179335249

is 峽 the most common translation for a mountain pass or saddle point?

my guess is Nalon was a typo of "Nason Creek Game Reserve" https://lawfilesext.leg.wa.gov/law/WSRAgencyFilings/Community,%20Trade%20and%20Economic%20Development,%20Department%20of/2138.pdf - abolished in 1968, replaced with a bow and arrow hunting zone.

I couldn't find anything regarding Chelan County Park. I assume it was incorrectly placed there on some old map that the GNIS team added. since they've rescinded all of the park IDs it's probably not something they'd research now. I'd just retag with a `was:` prefix, otherwise it'll probably show up again in the future due to GeoNames.

this was an automated edit, but from what I can tell this:
* was on a USGS map (https://prd-tnm.s3.amazonaws.com/StagedProducts/Maps/HistoricalTopo/PDF/WA/250000/WA_Wenatchee_244605_1957_250000_geo.pdf as an example)
* made its way into GNIS (though has since been rescinded, all parks have been removed)
* then copied into GeoNames, Wikidata, Wikipedia

so... probably was a real thing of some sort 50-70 years ago, and is now difficult to completely scrub.

as for OSM: prob start with adding a lifecycle prefix to destroyed: or something? I can update OSM and Wikidata if you can't but don't have delete access to Geonames.

the wikidata tag is on relation/12144066 - aside from the sign at the JMT intersection all of the maps I have only call these the "Davis Lakes" and don't specifically name either one as "Davis Lake". do you have a source that does?

otherwise I by convention around here the individual lakes would be known as "Upper" and "Lower"
---

Published using OSMCha: https://osmcha.org/changesets/177219459

the north side has a name on TNM now, I added it here too
---

Published using OSMCha: https://osmcha.org/changesets/174800647

sure, and that's good. we can definitely use one.

couple things to note:
* passes/mountains shouldn't be moved unless there is a reason - we've been trying to get these aligned with the latest 3dep lidar scans, which are unlikely to coincide with administrative boundaries. moving Arc Pass, as an example, puts it quite a ways to the south of the true saddle point
* adding them to the boundary makes importing boundary updates somewhat more tedious/annoying and (tool dependent) can break the somewhat questionable practice of linking these nodes from their wikidata entities
* the Sierra runs much further north and south than is currently modeled
* type=multilinestring isn't a valid outer for the Mojave boundary relation - the Sierra crest is quite a ways away anyways
* and the new Mojave looks like a duplicate (same wikidata/etc) of the existing Mojave relation

mountain range tagging is fairly nacent, and inconsistent. take a look at other examples around the US (and world) https://overpass-turbo.eu/s/2fXO for ideas. there has been a somewhat recent push to revive type=multilinestring.

anyways, hope this didn't come off as too abrasive. it's something that is useful just a bit complicated to complete.

this looks a bit odd, what are you trying to accomplish with the Sierra Nevada relation?