Hi Smaug7,
Welcome to OSM and mapping in Utah! We're happy to have you. Because of our slightly unusual street names here in Utah, we have a specific page on the wiki about it (osm.wiki/Utah/Naming_Conventions). Specifically, the "N" prefix that you added to the street in this changeset is already captured in the name:full=* tag, so that the most common name=* tag can match what is visible on the street sign. It would be great if you could change this back (and the other nearby streets), or I am willing to do it for you if you ask. Feel free to ask if you have any questions! We can always use more people contributing to the map.

Hi Calamity_Engine,

Welcome to OSM, and mapping in Utah! We're happy to have you. I'd like to point out that because our street names here are a little unusual, we have a wiki page with specific guidance: osm.wiki/Utah/Naming_Conventions .

Specifically in the case of the edit you performed here, the number for a road that also has an English name goes in the alt_name=* tag, rather than the ref=* tag. ref=* is for route numbers, e.g. US 89 or SR 203. Also the way that the unsigned prefix is broken out into the name:prefix=*/alt_name:prefix=* tags. Please make these fixes, or I'd be happy to do them if you'd rather.

If you have any questions, please feel free to ask!

Hey flug32, I find it highly doubtful that the new residential street lets the creek run across it. Using your Mapillary traces, I went and moved the creek so that it isn't glued to the new roads. In your images, it looked like it went under a tunnel, let me know if that isn't the case. Thanks for collecting those images!

I don't know if you missed this, but the bus number is already present and belongs only in the ref=* tag, not the name=* tag. Is there an app or website you're using that wasn't already prominently showing the ref=* value?

While I'm at it, given this isn't the only edit you've made related to public transit, I want to make sure you're aware of the Utah/Transit wiki page (osm.wiki/Utah/Transit), where we keep notes and links to sources and tools

Hey 007Transformer,

Pretty sure that "Evanston, WY" is a single unit as "city, state", not that "Evanston" and "WY" are two different branch names

Hello Always_Dreamin,

Thank you for all of your recent edits in Utah. In the future, can you please write more descriptive changeset comments than just repeating "Updated tagging"? Phrases such as "Added zip code", "Merged POI into building", or "Removed addr:country" are a lot more helpful for people who are trying to review changesets.

Sounds good. I'll put fast_food back, and move the pin to your new location for you

Hi Ortega, you commented that you changed the address, but what you actually did is deleted the amenity tag so that this is no longer a fast food place. Was this on purpose?

Hi Nikhil, thanks for your edit! You were right the first time, though. These are just footpaths, not pedestrian streets. I've taken care of changing them back already

I did see that sign like that, but didn't notice street names. I think I'll trust the addresses UGRC has and change these names

Hi dsm, 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.

Hey leftybender, where did you get the street name Eaglewood Cove Loop? UGRC claims the name "Wood Oaks Loop" for that street, and I surveyed today and couldn't find any street signs

You are right that as a local if I were to read the full address out loud I'd put a pause after 'West' instead of before, pairing it with the house number instead of the street. Unfortunately, since that cardinal direction is not usually signed on the street sign or on buildings, it doesn't have an obvious home according to typical OSM conventions. However, the local conventions linked above follow the patterns used by most local GIS departments, so that's we've settled on for now. I'm working on a proposal to put forward to the larger OSM community eventually to get more proper support in other OSM based software.

Hi Kuatsystems, please note the callout on the wiki page for basin=stormwater (basin=stormwater) that encourages mappers to use basin=detention instead of basin=stormwater, since they have the same meaning

Hey technicat, a restaurant closing doesn't cause a building to no longer exist. In the future, please only delete the relevant tags instead of the entire way (and you can use the shop=vacant tag)

Hi technicat,
Thanks for all of your work on POIs in SLCo. As you do so, please make sure that your future edits conform to local naming conventions (osm.wiki/Utah/Naming_Conventions) and OSM conventions for expanding abbreviations. In this case, rather than

- addr:housenumber="1835 W"
- addr:street="3600 South"

use

- addr:housenumber="1835"
- addr:street="West 3600 South"

Hi Joseph, I noticed that you edited some street names. Due to the inconsistent ways that TIGER handled them, they are a bit of a mess, so thank you for your work! As you go forward, please make sure that you are following the guidelines set forward at osm.wiki/Utah/Naming_Conventions. In short, since the actual signs on the ground say "1200 East", that's what goes in "name=*", and the full name used in addresses goes in "name:full=*"

I was curious about the roads in this area. Thanks for taking the time to survey!

Hello slcstreetmap, welcome to OSM and mapping in Utah! What exact turn restrictions were you trying to add here? Unfortunately, these restrictions as you uploaded them are invalid/incomplete, as a turn restriction needs a 'from', 'via', and 'to' member. My first guess is that you were trying to indicate that you can't turn left onto 700 East from these neighborhood streets?

Hi truemarmalade, I'm not sure you're using access=yes correctly. Tagging sidewalks this way means that *any* mode of transport is allowed to use this sidewalk, including motor vehicles, which is not true. My first guess of your intention is that you mean to indicate that there is public access to these sidewalks for walking, which is already implied by highway=footway and therefore there is no need for an access tag. If there are signs indicating that bicyclists should also use the sidewalk, then you could add foot=yes and bicycle=yes, but I don't expect this to be the case.