there are only 11 instances of this tag worldwide, why the change? https://taginfo.openstreetmap.org/tags/shop=camp#overview
---

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

should this node be expanded to an area that includes the mine shaft? osm.org/node/369167242
---

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

I reverted this change in osm.org/changeset/156021358

awesome, thank you!

does that imply that this is an official maintained park trail? when I have been on this it was a use trail (informal=yes)

should this be “Forces”? osm.org/node/11189397550

no worries, thanks for the edits!

should this long section be a bridge? osm.org/way/1300135686#map=17/37.74902/-119.58279&layers=N
---

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

is this correct? there is a metal pipeline visible in areas that this changes to a culvert.
---

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

can you update the cabin numbers to be on the ref tag instead of name? this is the convention for building numbers
---

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

the western service road added here crosses over Porcupine Creek a couple times, is that accurate?

thanks for working on features out here, lots of tracks and streams can use a lot of work still!

be aware that Bing has gotten better over the last few years but still has issues on the steeper slopes. at some point there will be LIDAR coverage and we can have excellent alignment once and for all. but until then it’s not a bad idea to use a couple sources, a gps survey, or Strava to cross check. sometimes Bing can be off by many meters. and very occasionally by 50 meters or more.

one thing that would help us review these changes is to include a brief summary of the edits you are making- something like “making track adjustments to Bear Diversion” would be great. otherwise we have to figure it out entirely by looking at a diff.

thanks again!

I have wondered about this but never did the research, thank you. Next time I would recommend grouping the relation edits together since they were all in the same (small) area.

ok, so it is open to foot/bike? I added what is probably an overly restrictive access tag to the road and barrier. any chance you can take a look and update it?

is there a barrier somewhere? the road status should probably go in an access tag and barrier, not in the name.

on Strava and Bing it looks like there may be a barrier here osm.org/node/3674125303 with no access to the east. does that sound right?

Yosemite isn’t too bad since most of the creeks have been drawn by hand, but they are often split with culverts… compare that to most of the rest of the Sierra where it is terrible NHD flow lines, and there are lots of two node ways near the wikidata coordinates.

appreciate the help though!

thanks for helping with tagging. the osm.wikidata.link app doesn’t support waterway relations and often adds duplicate or redundant tags. any chance you could take a pass through these changes and see if the relation is tagged appropriately (if there is one)? I have been trying to keep tags on the relations
---

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

I've never found a tutorial that makes any sense to me, I just beat my head against the wall every time and hope something eventually works.

I assume that the data is correct and my query is wrong, and iterate until the query is more or less correct.

that query does return buildings but it doesn't render them.. try this instead, it shows the ways AND the nodes: https://overpass-turbo.eu/s/1GdG

what is the overpass query you are using?