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.

Hi leftybender,

Please remember to not use abbreviations, in this case in the values of addr:street=*

Hey mvexel,

Please use the modern sidewalk tags `sidewalk:*=*` instead of just `sidewalk=*` (in this case, `sidewalk:both=separate`) as recommended the Pedestrian Working Group (osm.wiki/PWG_Guide)

Hi Flap Slimy Outward,

I discussed this change with multiple other locals in person, and we all agreed that these changes don't make sense. I've taken care of reverting for you.

Hi Flap Slimy Outward,

I discussed this change with multiple other locals in person, and we all agreed that these changes don't make sense. I've taken care of reverting for you.

Hi Melissa, where did you get the dash cam footage you used as a source here? I drove this highway tonight and saw a 55 mph sign at approx. 4250 South and a 50 mph sign at approx. 3300 South

Hi Akgeo,

If you look a little closer at this junction, you should see that the segment you added is unnecessary, because the way closer to Sheep Lane is not oneway, since there's no physical barrier between the left turn lane and the other direction of traffic

Hi jodapop,

Please note the point on the wiki page for natural=sand that using it for baseball diamond infields is incorrect, and for that purpose you should use surface=* instead

whoops, don't know how I made that mistake. Thanks for catching it.

Hello Jerry1178,

Welcome to OSM, and mapping in Utah! We're happy to have you. Are you aware that changeset comments are public information? Are you okay with what you've put here being public? If not, you can contact the Data Working Group at data@openstreetmap.org to have it redacted.

Also, please note that adding the name "Driveway" to a line already mapped as a driveway (with highway=service + service=driveway) is a case of descriptive naming, which is discouraged in OSM (see osm.wiki/Names#Names_are_not_for_descriptions)