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.

Hi Flap Slimy Outward, I discussed this changeset on the OSMUS Slack, and others agreed that this is incorrect mapping. SR 30 is not unsigned between the segments, it is legally defined as discontinuous. Therefore, the existing way it was already mapped is all that should be mapped. Please revert your changes related to the two extra relations related to SR 30.

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 numerical alternate street name "West 3940 South" was already captured in alt_name:full=* according to osm.wiki/Utah/Naming_Conventions. Additionally, name_1=* has been deprecated and should not be used, according to osm.wiki/Names#Deprecated_tags

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 "East Kennedy Drive" was already captured in name:full=* according to osm.wiki/Utah/Naming_Conventions. Additionally, name_1=* has been deprecated and should not be used, according to osm.wiki/Names#Deprecated_tags

Hi Kepler, thanks for all our recent edits! Little things like parking spaces and grass strips really help to make the map look more full. Just a couple points for you:

1. amenity=parking is meant to cover entire parking lots, not each little cluster of parking spaces. In this little area, I'd probably combine this into just 2 areas. You might be able to argue splitting it into 3, if any of the businesses have "XX customer parking only" signs.

2. "Micromapping" is not a very descriptive changeset comment. Since it looks like you're already splitting your changesets into categories like parking, landcover, buildings, or roads, I would appreciate if you could include details like that in your comments.

I've reverted this change in changeset/184064467. PLEASE, start looking at the history of a road before changing its name like this. If an experienced local mapper has already worked on it, then the name is probably already correct.

I admit, the street names for these frontage roads are unusual. That's why I've already taken the time, as a local, to survey the street signs along these frontage roads multiple times.

Additionally, it's perfectly acceptable for a road to have a ref=* and not a name=*. Especially when that name you incorrectly tagged doesn't fit its placement in the street grid.

Also, route_ref=* and street:name=* are existing tags that have meanings documented on the wiki, which are not the meanings you've used here. Please don't make up new meanings for existing tags.

Wonderful, thank you

Whoops, that's a tag from the data set I'm conflating against. Guess I accidentally included it on this one road. I've gone back and removed it now.

Hi Rax,

When you added this name, did you realize it was a kindergarten? Is ARUP really operating a kindergarten inside their lab?

Hello visitingangels,

You've added a point to the map labeled as an assisted living facility, as in a place where people move in a receive constant care. This building appears far too small for that kind of facility, and based on your website this is not the kind of service you provide. I'm guessing this is actually an office your employees operate out of?

If this is true, something like `office=healthcare` would be more appropriate than `amenity=social_facility`. Let me know if I've guessed correctly, of if this is another situation.

Hi Spanwar, if you have access to proprietary post-construction imagery, rather than just deleting the old lanes=* values, could you please take the time to add the new lanes=* (and destination:lanes=* and placement:*=*) values?

Hi Viktoryia, mappers in Utah as a local community have already worked very hard to correct all TIGER names in Utah, as it did a very poor job of handling our street names (In this case, "University Village" is the name of the complex, not a street name). In the future, please do not use TIGER as a source in Utah.