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

Hi Murali3, please note that because of Utah's unusual street names, we have a wiki page dedicated to it: osm.wiki/Utah/Naming_Conventions. According to those guidelines, the correct way to tag this street is: name="2475 West" + name:prefix=North + name:full="North 2475 West" (when also following general OSM guidelines to avoid abbreviations).

Additionally, could you please more descriptive changeset descriptions? "Modified tags" doesn't really say much, compared to "Added new street" or "added missing street name" or "added address", which are much more useful to people trying to review changes.

Finally, what was your source for this change? I see that you put "survey" on multiple changes that span the continental US, which unless you've been keeping notes across a many month journey or invented teleportation, I find improbable.

Hi marialoyko, please do not use TIGER as a source for road names in Utah, it is very inconsistent about how it handles them. For more information about our unusual road names and how the local community has settled on handling them check out osm.wiki/Utah/Naming_Conventions . If you have any group resources at Mapbox, please make sure this is part of it as this is not the first time I've had to point this out to your team.

Hi wvdp, what is your source for naming the datacenter you added here as name=Verizon? That's a value I would expect to belong instead to operator=*

Hello eaglespringspest, welcome to OSM, and mapping in Utah! We're happy to have you. For future reference, I want to make you aware of the following guidelines for OSM.

1. Avoid abbreviations. Because it's easy for a computer to abbreviate something, but not as easy to unabbreviate, we always aim to use full names (e.g. "North" over "N", "Drive" over "Dr"). For more, see osm.wiki/Abbreviations

2. Because of the unusual way we name streets here in Utah, we also have specific guidelines on a dedicated wiki page: osm.wiki/Utah/Naming_Conventions. In short, this specific street rather than including the direction prefix in the name, it goes in a dedicated name:prefix=* key. Updating the whole state to match this is an ongoing effort, but I went ahead and did this block for you.

If you have any questions, don't be afraid to ask. You're also welcome to join other locals over in the #local-utah channel of the OSMUS Slack.

Hi viktoryia, please do not use TIGER as a source for road names in Utah. TIGER did a horrible job of handling our multiple street names and the local community has put in a lot of effort to clean up the mess. Specifically in this case, note that the full street name "West 7800 South" was already captured in name:full=* according to osm.wiki/Utah/Naming_Conventions.