Hi oscarm, given the newer imagery you have access to, can you please check the arrangement I guess at with the proposed alignment that left turns on to the north end of Towne Commons Dr (from WB Herriman Rose Blvd) are possible, but left turns onto the south end of Towne Commons Dr (from EB 13400 S) are not possible?

Hi alena karpenka,

This slip road has been removed as part of a recent construction project. You would have known this if you noticed the demolished:highway=trunk_link that you drew this new one on top of. Please pay closer attention next time.

Hi CoolMan,

Have you seen osm.wiki/Utah/Naming_Conventions ? Because of the unusual way that street addresses work here in Utah, we have a dedicated wiki page to explain that, even though a local may read this address as "448 East, 400 North", we as a local community have decided it's best to map it with addr:housenumber=448 and addr:street=East 400 North. After all, the "East" part of the address that you deleted here is necessary information for the address. Let me know if you have any questions.

I see the note you left on the trailhead, and you're absolutely right! That is bad form! Even if you can't find it spelled all the way out as "500 South" in any official materials, that doesn't mean it's not an abbreviation that should be spelled out. The fact that it's namesake street is right there should make this obvious that the real name is "500 South Trailhead".

At the same time, I see you're not the one who originally tagged it as a rest area, but given the fact that it has "trailhead" in the name, you probably should have changed it to highway=trailhead, which just happens to be next to a highway

Hi Warren, did you realize that you changed the outline of the river to have highway=secondary? Since this is obviously a mistake, I've already taken care of reverting this change. What part of the bridge were you trying to fix? It appears to already have the construction tags removed from both the road and the sidewalks and cycleways on both sides.

I've created a forum post at https://community.openstreetmap.org/t/what-service-value-for-fuel-pump-aisles-at-amenity-fuel/148007/2

Yes, definitely a mistake! Thanks for catching that, I've fixed it.

Hi carlosguerrero, what is your reasoning for removing service=drive-through on the gas station pump aisles here? While I admit it is a small stretch of the definition of drive-through, I have found no better tag to indicate the usage of these aisles, and find it useful to indicate the lesser significance of these ways compared to other service roads for entering/exiting the gas station.

Reverted for you in changeset/189271627

Hi JustClay, welcome to OpenStreetMap and mapping in Utah! I see that you requested a review of your changes on this and a couple other changes on this apartment building. While every tag on OSM technically is free form entry, there are agreed upon patterns we use to make it easier to use the map. These patterns are documented on the OSM wiki, such as the pages for opening_hours=*, phone=*, or addr:*=*. I've taken the time to adjust the changes you made here to the standard formats.

I'll also point out that because of the unusual way that road names and addresses work in Utah, we have a dedicated wiki page about it: osm.wiki/Utah/Naming_Conventions

If you have any questions, feel free to ask. You're also welcome to join other local editors in the #local-utah channel of the OSMUS Slack at https://slack.openstreetmap.us/

Hi EzyPup, have you been to survey this in person recently? According to another local, this painted path was part of an event (Green Loop pop-up), was intended as temporary, and is already fading. At least, the northern block of the edits you did here.

Hi icarus72180, your recent edits give the impression that you have recently discovered multipolygons, and are a bit too excited to use them, applying them where it is unnecessary or incorrect.

In this case, consider what your edits state: by making the park into a multipolygon and using all the pitches, playgrounds, and parking lots as inners, you say that while they are inside the outer line of the park, they are not actually part of the park. In reality, pitches, playgrounds, and parking lots *are* considered part of a park, so having them inside a plain leisure=park area is the correct way to map them. If a thing is normally considered within another thing, it is totally fine to have overlapping areas and not cut out multipolygons.

Also, on a handful of your other recent changes, I see you created grass multipolygons that have very thin portions along the property boundary, which I expect are much more likely to just be the parking lot going all the way to the fence. Additionally consider that the grassy areas behind/next to an LDS chapel are not normally signed as a public park or expected to be used a such by the public, and are very likely to instead just deserve to be mapped as grass (and the rare pitch).

I see that on this changeset you only listed Bing aerial imagery as a source, but you changed speed limits along a decent portion of some roads, which you cannot find on aerial imagery (except in very rare cases).

Can you tell me what source you used for these speed limit changes?

Hi jmsmucker,

The combination of tags you've used here (and a few other similar changesets) of highway=construction and access=destination doesn't really make sense, as according to the wiki page, highway=construction is for roads that are completely unusable to the intended traffic, which doesn't match with access=destination.

Also, what are the expected timelines for these construction projects? Are you aware that, due to the slow cycle some consumers update their OSM downloads, it is recommended to only map projects that will last 6+ months in this pattern, and for shorter projects to instead use conditional access (access:conditional)=*?

Hello,

In OSM, we aim to have the map match what is physically on the ground (osm.wiki/Good_practice#Map_what's_on_the_ground). A mapper previously mapped that this road is named East Canyon Road (in addition to being SR 66).

The nearest street sign I can find in street level imagery is at the junction with Morgan Valley Rd north of here in Porterville, which does indeed sign this road as East Canyon Road. However, that imagery is almost a decade old. Can you confirm whether the nearest street sign for this address reads "East Canyon Road", "Highway 66", or something else?

Unless some significant construction slipped under my radar, all of the campgrounds here have pavilions, not cabins. Can you confirm?

I also suspected that "Mountain Dell Ranch" was a case of UGRC assigning the name of a destination as the name of the road to get there. But, checking the council's website, they apparently aren't sure themselves. The registration information page says "Mountain Dell Ranch Road", but the information booklet says "Sky Haven Drive". Maybe if one of us contacts the council or the county, they'll have a concrete answer?

Hi Gorger, it appears that on some of these streets, you remove the construction=residential tag, but did not do the corresponding update from highway=construction to highway=residential. Are those roads still under construction (and therefore the delete was accidental) or is every road here done (and therefore you forgot to do the matching tag change)?

Hi jacceber, I've never seen highway=pedestrian used like this, and I don't think it's correct. highway=pedestrian is meant more as a standard street that has been closed to (most) motor vehicle traffic, but still has residences and buildings along it. A schoolyard doesn't fall close to that, as just a large paved area for schoolchildren to play at. What is your logic for adding it here?

Hi cbmiller2610, please note that due to the unusual addresses we have here in Utah, we use additional tags to represent street names. In this case, the "West" part of this street name was already correctly represented in the name:prefix=* and name:full=* tags. For more information, see osm.wiki/Utah/Naming_Conventions . If you have any questions, you're welcome to join us in the OSMUS Slack at https://slack.openstreetmap.us/, and find fellow locals in the #local-utah channel

Hello santoshipanwar, the road did not cross the railroad here because this crossing has been indefinitely closed (as announced by the city at https://www.slc.gov/district2/bulletin-board/indefinite-closure-of-200-south-between-montgomery-street-and-approximately-1640-west/) (which you would have seen if you checked the history of the road ways). Please revert.