Can you give examples of breakage? I'm not aware of any problems with a way tagged as highway=* as well as piste:type=*. It accurately represents that the road is closed in the winter and becomes a snow covered ski trail.

Private toll roads up mountains are quite minor and should not be secondary. I've reverted this changeset:
changeset/111671942

This is incorrect. The toll road up Mt Mansfield is a very minor road and should not be secondary. You also removed the piste:type tag which is incorrect because the this road is a ski trail in the winter. I have reverted this changeset.
changeset/111671808

I see you did the same thing to the Mt Washington auto road. Please stop doing this. changeset/111541651

Hi, this changeset deleted the piste:type and piste:difficulty tag from several ski trails at Mad River Glen. Did you do this for any particular reason, or just a mistake?
way/31477640/history
way/31433493/history
way/44626947

Please put them back so the trails won't be removed from:
https://openskimap.org/#16.78/44.190506/-72.929419
and
http://www.opensnowmap.org/?zoom=17&lat=44.19076&lon=-72.92858

If you have no other source than Strava then you don't know there is a trail there. All you know is that "there is a heavy walking activity". This does not necessarily make it a trail.

Thank you!

Thanks for adding the address, but why did you change this building's name. As far as I know, it is still called "Hotel Jay". https://jaypeakresort.com/trip-planning/lodging/hotel-jay-conference-center
The name "Jay Peak Resort" refers to the entire ski resort area, not just this building.
---

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

Hey Jeff, thanks for updating this area. Looks like this building got a little messed up though: way/201655043
The way isn't closed and it looks like the tags got moved to a relation? I know there has been recent construction in the area so I don't really know what the current state of things is. If you have on the ground knowledge and can fix it up how it should be that would be great.

Oh yes, jared is another VT based mapper I've chatted with on Slack. They've been adding addresses and buildings all over the state with the RapiD editor (an iD fork with access to external data sets).

@jared
osm.wiki/RapiD

I was worried there was some larger automated editing going on that I should be aware of. From what I've seen these changes seem to be in small batches and getting verified against aerial imagery. Obviously that can be out of date though, and I'm sure your on the ground knowledge of the area is better!

Thanks, for the reply. Always good to make contact with another VT mapper.

Hi A Hall,
Thanks for your work improving the map in Vermont. I saw your changeset comment and was just wondering what the incorrect automated edits you noticed where. Looks like this changeset mostly deleted some address nodes and copied the tags over to a nodes on the corresponding building outlines. Also if ever need to get in touch with other Vermont mappers join us in the #local-vermont channel on the OSM US Slack https://slack.openstreetmap.us/
---

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

Thanks! Glad you like them. My office is on church street so I've been walking around and surveying a bit on my lunch break. I've been learning the history of some of these buildings too from this UVM project: http://www.uvm.edu/~hp206/2018/

Looks right to me, Stan, although I was under the impression most OSM based routers assumed bicycle=no on highway=trunk roads unless otherwise tagged. Sounds like that wasn't your experience though. What routing service were you using?

Did you notice that this island is no longer visible due to changing natural=coastline to natural=coastline;glacier? I suggest mapping the glacier as a separate object from the coastline

RunTrails and WambacherWest, I've raised this issue on the OSM US Slack and the Talk-us mailing list if you care to join.
https://slack.openstreetmap.us/
https://lists.openstreetmap.org/pipermail/talk-us/2021-April/020969.html

It's important to understand that the OSM tag "boundary=national_park" does not have the same meaning as "National Park" defined by the US National Park Service. They often overlap, but not always.

Looks good. Since it looks like the road is mostly blocked off I went ahead an disconnected the streets. I does look there is enough room for bicycles though so I added a little cycleway connection. Feel free to adjust if you have better information! changeset/102760709
---

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

👍 I support this change. So there's a VT consensus of at least two.

The thing with OpenStreetMap is that the data can be rendered into many different ways. The transit layer focuses on public transit, not paths or roads so it shows them as simple gray lines without differentiation. Other layers like CycleOSM or Cycle Map show different types of paths differently.

Also, jmoran314, there are limits on mapping private information. See: osm.wiki/Limitations_on_mapping_private_information
A toilet in a private resident is not appropriate for inclusion in OSM and would be removed.

Looks pretty good to me, Alaina. I saw the fixme note about how all the features of the Blue Hill trail ought to be connected but you didn't know how to do that. I checked for disconnected ways and didn't find any so I don't think there is a problem with it. Maybe I'm not quite understanding though. I also saw you were wondering how to separate a road into two sections, but it look to me like you had figured that out.

I think the access tags may still need some adjustment but that's ok. You're dealing with a complicated situation here! I'll send you a separate message with some more information about more complex accessing tagging.

Also if you want to join the OSM US slack, it's a great place to ask questions. You'll find discussions about this kind of stuff in the #trails channel. https://slack.openstreetmap.us/
---

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