Thank you for reverting.

I would not be surprised if data consumers use ref=* to match addr:housenumber=* in other places, but in this case no, the ref=* on its own is not sufficient, because:

1. That leaves out the street prefix, which is a required part of the address (e.g. "North" in "989 North Highway 89" at way/35936661)
2. It would be unreasonable to expect data consumers to know that "US 89", "Highway 89", and "US Highway 89" can refer to the same thing here, or in other places that "SR 132", "Highway 132", and "State Highway 132" could all refer to the same road.

Thus, in addition to the ref=* value that matches shields, we map name=* (and name:prefix=* and name:full=*) values that match the spelled out name on street signs. (e.g. https://www.mapillary.com/app/user/asellars?lat=40.83269843&lng=-111.91470327&z=17&pKey=919040351973903&focus=photo&x=0.5105628121557317&y=0.4326672500813823&zoom=0)

Hi Halfdeaf007,

Why did you create multipolygons that cut out the parking lots for these landuses? A landuse area is meant to cover the full area used for something, not just the areas that aren't parking.

Hi cache117,

Please note that naming a drive-through after the restaurant it serves is a case of descriptive naming, which is incorrect mapping (see osm.wiki/Names#Names_are_not_for_descriptions). Instead, this could be expressed by adding drive-through=yes to Wendy's and drive-through=no to the other POIs in this building.

Please correct this within 7 days, or I will fix it for you.

Hi Flap Slimy Outward,

When you downgraded this portion of road from highway=secondary to highway=tertiary, did you release that it was at secondary because it is part of the movements for the intersection of State St/12300 S?

This is a special "ThrU-Turn" intersection, where drivers wanting to turn left from southbound State St to eastbound 12300 S must instead go straight south onto Minuteman Dr, do a u-turn, then turn right onto 12300 S.

Hi Flap Slimy Outward,

This is not the first time I've said that there are times when a highway numbers belong in the name=* tag. With you deleting the appropriate name=*, name:prefix=*, and name:full=* tags, the North Salt Lake addresses along this road can't correctly match to this street. Please correct this within 7 days, or I will fix it for you.

And why did you also delete the perfectly valid name="Beck Street" (and subtags) along other portions of this road?

That's precisely my point, that fire station numbers are *not* treated like store numbers. Where store numbers are generally only used by employees and in internal documents (store specific URLs being an exception), fire station numbers are included (sometimes rather prominently) on the building, uniforms, and vehicles.

Only 8 out of 270 fire stations currently mapped in Utah have a ref=* value. Further, I randomly looked at ~15 fire stations mapped in urban areas, and none of them were imported. They all were mapped by survey or local knowledge, and the ~7 different mappers who added them all put the number in the name.

Similarly, of the 34,000 fire stations mapped in the USA, 34% have gnis:feature_id=* (so it's likely that 66% weren't imported), and only 4% have ref=*, further demonstrating that the change you performed here is highly unusual. This is why I think this change is incorrect.

Hi exboyscout, thank you for this edit. A fence sounds much more appropriate based on your reply on your previous changeset.

Since you indicated in your changeset comment here that this is a construction barrier, is there any signage on site, or any online materials, to indicate the length of time this barrier will be present?

Because of the slow cycle that some data consumers use, we generally don't map things that will be there for less than 6 months. This is to reduce the chances that some data consumers show a temporary barrier for a year (or more).

Hello Hypsometric, what was your reasoning for moving the number for this fire station to ref=*?

In my experience, the number for a fire station is treated more like it is part of the name, and less like an identifier. This overpass query also shows that holds true for pretty much anywhere in Utah where multiple stations are run by the same department

https://overpass-turbo.eu/s/2j1X

Hello Caysem, welcome to OSM and mapping in Utah! We're happy to have you. Can you tell me if there's any signage here to indicate the intended users of this path? As you've mapped it so far, some data consumers may assume that it it only intended for cyclists, and not people on foot. If it is intended for both, the more specific thing to do would be to add bicycle=designated and foot=designated. Feel free to ask any questions if this is unclear!

Hello MSK_222, by what reasoning did you remove junction=circular here? This junction is already unusual for this area, but it was the best tag I could find to express that this has two way traffic along part of it and only some roads have yield signs

Hello ItsGav, the entire contents of this changeset is deletion of a traffic signal and its pedestrian crossings. I find that highly unusual. Can you confirm that they really took out a traffic signal here?

Did you miss that there's already three other amenity=bicycle_parking (one for each bank of lockers) right here?

Thanks for this work, looks like a high quality changeset! For future reference, the operator:short=* tag is more commonly used for abbreviations instead of leaving out a single word (check it out for yourself at https://taginfo.openstreetmap.org/keys/operator:short#values)

Hello exboyscout,

What were you trying to map here? On recent street imagery I see nothing that looks like a historic city gate.

Hi jdupuis, welcome to OSM and mapping in Utah! Just a couple notes for you: 1. when mapping the name of a residential development (like the townhomes you did here), the name goes on a residential area covering the whole thing instead of copied on every building. 2. In OSM, we don't use abbreviations in tags. Rather than addr:street="S 900 E", the correct form is addr:street="South 900 East". I've already corrected these issues for you. Feel free to ask any questions you have!

Hi Kirk, do you know if the building is split between Dive Utah and SwimKids, or if it's a case of one borrowing space from another? Do you know if they have separate entrances?

Hey dmcg12, thanks for adding all of these. The issue was that while highway=stop and highway=give_way nodes belong on the highway=* way, traffic_sign=maxspeed nodes belong at the position of the actual sign, not on the highway=* way. While checking all of the street names I think I caught all of them and fixed them for you.

Hey dmcg12, the wikidata=* or wikipedia=* tags that you added to the bank here are for when the entries refer to a specific place. Since in this case it the entries refer to the brand, it belongs in the brand:wikidata=* tag. I've taken care of fixing this one for you.

Hi kylegrieder, welcome to OSM and mapping in Utah! We're happy to have you. In your description for this changeset, you reference that you increased the building level here for basements. However, the wiki page for the building:levels=* tag points out that it is the number of above ground levels, meaning a basement is not included. Did you realize this?

Hi cas79, welcome to OSM and mapping in Utah! We're glad to have you. In this changeset, you left the buildings not quite attached, but in the imagery it looks to me like the buildings are connected. If the buildings are physically connected on the ground, they should be connected (glued) together in OSM.

Also please note that in OSM we avoid abbreviations, so where you used addr:street="N Main St." here, it should actually be addr:street="North Main Street". Please make these corrections, or just ask and I'm happy to make them too. Feel free to ask any other questions you have!