awesome, thanks!

I believe the wikipedia tag should be `en:Half Dome` with the en: prefix, any chance you can review and adjust as needed?
---

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

@stevea "that the relation IN the Ukraine didn't change" is incorrect, this changeset dropped the natural=wood tag from it. see relation/12412862/history perhaps you can fix the issue.

Pinchot Pass already exists, take a look at node/6227696613

what change was intended to be made here? it looks like the existing way was deleted and it was replaced by a new one with nearly identical geometry
---

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

what change was intended to be made here? it looks like the existing way was deleted and it was replaced by a new one with nearly identical geometry
---

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

k, it does look like a mess up there these days.

curious, did the use trail from New Army to Langley disappear? it was pretty prominent back in 2016 or 17 and (iirc) was showing up on the Strava heatmap as of last year.
---

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

are these actually tracks or paths?
---

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

Same with this one, thx :-)
---

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

Elevations need to be listed in meters not feet, can you fix it?
---

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

Duck Pass was already on the map node/762008590
---

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

most or all of these campsites do not appear to be legal, they're very close to the trail or the river. did you confirm that they are at least 33m/100f from both?

I use a few sources: USGS topos, USGS 3DEP files/layers, and a file proceed by the owner of peakbagger.com to use for OSM updates. I mostly use the latter to programatically identify misplaced peaks and use the USGS sources as the primary, it's a very manual process. There are some cases where the highest point does not match the topos for a variety of reasons. My hope is in a few years we will have LIDAR coverage everywhere and can derive most of this from the data when quality surveys are not available.

maybe, maybe not. I haven't looked into the accuracy of the elevations there but the lat/lon aren't very accurate. they're usually in the general area but that's about it. I only add elevations when there is a trusted reference (surveyed elevations/benchmarks) since I don't know a better reference. the 3DEP lidar data will presumably become this once it's available for the high Sierra. I understand that many changes have been made to the geoid since the 80s (when many of the GNIS entries were last updated) so I wouldn't be surprised if they were based off an old ellipsoid. https://eos-gnss.com/elevation-for-beginners has a quick overview of the challenges around this.

as for moving individual nodes... I haven't seen a way of doing it other than dragging them to the correct position in iD or JOSM. it's possible to do it by creating a .osm.xml file though, just not as user friendly.

I've found many peaks to be off, sometimes by more than a mile. check the change history for each peak and fix up any older ones to the 1990s era USGS quads (pretty accurate), as you see fit. if you question a more recent update just send a message to the author to get more details before making a change that may revert work they have done. in particular areas I may be able to help with getting better quality summit coordinates, just no guarantees.
---

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

This is done in changeset/103853052
---

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

no problem, I sent them an email and I'll update the name here.
---

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

it was previously slightly off too, I updated this using the current 2018 US Topo in https://osmcha.org/changesets/103849283
---

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

while the gnis id and current map show this as Eve Lake, it is clearly Ewe Lake on the older USGS quads. it seems likely that Ram and Ewe Lakes should be next to each other, I'm inclined to say this is a data error in gnis that should be fixed- perhaps send them an email to have it corrected? https://www.usgs.gov/faqs/how-do-i-report-error-geographic-names-information-system-database
---

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