Unless some significant construction slipped under my radar, all of the campgrounds here have pavilions, not cabins. Can you confirm?

I also suspected that "Mountain Dell Ranch" was a case of UGRC assigning the name of a destination as the name of the road to get there. But, checking the council's website, they apparently aren't sure themselves. The registration information page says "Mountain Dell Ranch Road", but the information booklet says "Sky Haven Drive". Maybe if one of us contacts the council or the county, they'll have a concrete answer?

Hi Gorger, it appears that on some of these streets, you remove the construction=residential tag, but did not do the corresponding update from highway=construction to highway=residential. Are those roads still under construction (and therefore the delete was accidental) or is every road here done (and therefore you forgot to do the matching tag change)?

Hi jacceber, I've never seen highway=pedestrian used like this, and I don't think it's correct. highway=pedestrian is meant more as a standard street that has been closed to (most) motor vehicle traffic, but still has residences and buildings along it. A schoolyard doesn't fall close to that, as just a large paved area for schoolchildren to play at. What is your logic for adding it here?

Hi cbmiller2610, please note that due to the unusual addresses we have here in Utah, we use additional tags to represent street names. In this case, the "West" part of this street name was already correctly represented in the name:prefix=* and name:full=* tags. For more information, see osm.wiki/Utah/Naming_Conventions . If you have any questions, you're welcome to join us in the OSMUS Slack at https://slack.openstreetmap.us/, and find fellow locals in the #local-utah channel

Hello santoshipanwar, the road did not cross the railroad here because this crossing has been indefinitely closed (as announced by the city at https://www.slc.gov/district2/bulletin-board/indefinite-closure-of-200-south-between-montgomery-street-and-approximately-1640-west/) (which you would have seen if you checked the history of the road ways). Please revert.

Yes, I suppose disused:*=* is a good place to start for stops that are no longer serviced

Hi Josh, in the future can you please use descriptive changeset comments? Based on some of your recent edits, I'd suggest things such as "added cliff", "added stream", or "changed name of piste". This would be a lot more helpful than just "q"

As you import buildings, please make sure that the footprints actually line up with the building, and to square the buildings which are made of 90 degree angles

yesss. We love more green landcover getting drawn

Unfortunately, as part of previous mapping, I've discovered that UTA removes a stop from their published datasets when it is not in service, but if a stop in a similar location gains service in the future, the stop code may be reused. Like you, when I didn't yet know this, I left a fixme=* on all the out-of-service stops. To make it easier to keep stops up to date going forward, I am now inclined to just delete out-of-service stops from the map (regardless of what the wiki says about keeping out-of-service stops as long as there's still physical evidence). What do you think?

Hi sun_lab, welcome to OSM! Thanks for your contributions. Please note for future edits that the sidewalk=* tag has been deprecated in favor of the sidewalk:*=* tag to reduce ambiguity.

In simple cases this just means using sidewalk:both=no or
sidewalk:both=separate instead of sidewalk=no or sidewalk=both, but gives the ability to be more specific in unusual cases. For more information about levels of detail in sidewalk mapping, check out the resources put out by the Pedestrian Working Group (osm.wiki/Foundation/Local_Chapters/United_States/Pedestrian_Working_Group)

Hi cbmiller2610, thanks for your contribution and welcome to OSM! There's certainly a lot of buildings left to fill in around here.

Please note for future edits that OSM prefers expanding all abbreviations to avoid ambiguity (e.g. "Ln" -> "Lane"). For more info read up about at osm.wiki/Abbreviations

Hi sbedwal_Lyft, please note that because of the unusual way we name streets here in Utah, we have specific guidelines on a dedicated wiki page: osm.wiki/Utah/Naming_Conventions. In this case, this street already had correct name tags, representing the "North" prefix in the name:prefix=* and name:full=* tags, making it incorrect to include it in the regular name=* tag.

Thank you for your contributions to the map! Unfortunately, I’m not sure this edit belongs. OSM is intended to be a map as things are on the ground, and that means a business mapped on a house stood out to me. I checked out the website you added and couldn’t find any addresses for (potential) customers to visit, which is a pretty good sign that this business location is not intended to be public and therefore doesn’t belong on the map.

I’d appreciate if you can demonstrate otherwise, such as with an image of signage posted outside. If not, I intend to revert your changes after one week.

Thank you for your contributions to the map! Unfortunately, I’m not sure this edit belongs. OSM is intended to be a map as things are on the ground, and that means a business mapped on a house stood out to me. I checked out the website you added and couldn’t find any addresses for (potential) customers to visit, which is a pretty good sign that this business location is not intended to be public and therefore doesn’t belong on the map.

I’d appreciate if you can demonstrate otherwise, such as with an image of signage posted outside. If not, I intend to revert your changes after one week.

Hi Christopher Z, welcome to OpenStreetMap, and editing in Utah! While the format this address was in before may look a little weird to a local, it is the format the local community of mappers has found will best handle the unusual pattern of Utah addresses. For more information, check out this wiki page osm.wiki/Utah/Naming_Conventions and feel free to join the OSM US slack and ask any questions you have for fellow locals over in the #local-utah channel

Hi Mashrafi Rian, why did you come back to this point to move information back to non-standard keys? OpenStreetMap operates on a pattern of keys and values where keys are technically allowed to be anything you want, but to improve the quality of the data, we as a community agree to a standard set of keys wherever possible as documented on the wiki (osm.wiki/). By using nonstandard keys ("Facebook" instead of "contact:facebook"), you are hiding that information from users of OSM data that expect the documented key

Hi carlosguerrero, as a local who has driven on these roads, I can verify that this traffic light operates on a specific cycle to make this movement possible and this turn restriction is incorrect. I could see an implicit restriction for HGV vehicles, since the space between lights is so short, if you feel that necessary.

Did you do anything weird while working on this changeset (intentionally or accidentally) that you think would have caused the history of a lot of these ways to be deleted and re-added as new ways?

Take that lol