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)

Hi Meadowlion,

I see that you requested a review of this changeset. Everything looks good to me!

Thank you for your contributions to the map! Unfortunately, I’m not sure they belong. OSM is intended to be a map as things are on the ground, and that means an office mapped on a house stood out to me. I checked out your website and couldn’t find any addresses for (potential) customers to visit, which is a pretty good sign that this ‘shop’ is not intended to be public and therefore doesn’t belong on the map.

I’d appreciate if you can demonstrate otherwise, such as with an image of signage posted outside. If not, I intend to revert your changes after one week.

Hi Halfdeaf007,

After I pointed out why this mapping style is incorrect on a previous changeset of yours, why do you continue to create multipolygons to cut parking areas out of landuses?

Well, that's a bummer, I didn't realize that CoMaps doesn't expose every field for an address. I would suggest either 1) supplying the parts of the address CoMaps does allow ("2100", "West Pleasant Grove Boulevard", "84062") and adding the full address in the note field at the bottom ("[business] full address is 2100 West Pleasant Grove Boulevard, Pleasant Grove, UT, 84062") or 2) switch to another editor that does supply all necessary fields for the address, such as EveryDoor or Vespucci

1. Automatic imports are far and few between these days. OSM prides itself on being human powered and reviewed, so automatic imports are allowed, but must meet several requirements, including community approval. For more info on this, check out osm.wiki/Import .

In Utah we have a license waiver to use data from the Utah Geospatial Resource Center, which provides us a lot of useful data. You just have to manually review each piece of data before adding it. For more on that check out osm.wiki/Utah#Data_Sources

2. Totally up to you! If you're in a situation where you can survey it regularly, then adding buildings one at a time as they are finished is fine. Or giving it time to finish and then mapping it in one go is fine too. Most places don't get mapped until some mapper happens to scroll past and notices something has changed.

3. Yep, there's definitely opportunities for that (and it's something I'm interested in doing myself, though I'm being slow to get to it). To kick off learning more about that, check out https://www.opendronemap.org/ and https://openaerialmap.org/ and this video from State of the Map US (an OSM conference) https://www.youtube.com/watch?v=VR-cpLep7D0

And finally, to connect with other local mappers, join the OSMUS Slack and look for the #local-utah channel https://slack.openstreetmap.us/

Not sure why you flagged this as review requested, but it looks good to me. The only thing I would nitpick is that I prefer to leave "Suite" out of addr:unit=*, since that seems like the popular thing to do. Or that I didn't even know his legal name is "Michael S Lee", so I would've gone for name=* and official_name=* instead of alt_name=* and name=*

Hi OpenMeatMap,

You've made multiple mistakes with the address on this office, namely placing the unit number in addr:housenumber=* and including the house number in addr:street=*. I've corrected the address on this node for you. Please pay closer attention to where the different parts of an address go in your future mapping. Feel free to ask any questions you have.

Hi zibetnu,

Just because there's no physical separation between the drive-through and the rest of surface in these cases doesn't mean there's not a reason to map them separately. Without mapping them as separate ways, how else would you express that there is a dedicated line along the surface where traffic is one way, and has the purpose of being a service=drive-through where vehicles queue separate from those driving around or parking?

Hello mew1033,

Welcome to OSM, and mapping in Utah! We're happy to have you. Thanks for drawing in this new street. For future reference, if you're from around here you probably noticed how the names on all the streets around here don't look quite like what the signs say. The common way the OSM handles addresses and street names doesn't quite fit how they are in Utah, so we have a wiki page explaining how we as a local community have decided to handle this:

osm.wiki/Utah/Naming_Conventions

The relevant part for this case is that instead of adding name="North 3670 West", you would add name="3670 West" + name:prefix="North" + name:full="North 3670 West". I realize that this doesn't match most of the streets in this neighborhood, Utah County just hasn't received as much effort to match these conventions yet.

Feel free to ask any questions you have!

What do you gain by merging a duplex into a single area?

I feel like it's preferable to keep them as separate areas and tag building=semidetached_house, because then you have the detail of it being a duplex, and which address is which

Hi italics_glowworm,

Please note that according to Utah's local naming conventions (osm.wiki/Utah/Naming_Conventions), the directional between the house number and the street name belongs in addr:street=*, not addr:housenumber=* (despite how a local would phrase it when reading it out loud)

Hi AngMapper, just because it is not public does not mean it is not a campground. Further, the tagged website lists that in the fall this campground is available to rent to public groups.

Hello hlthcarecomppr,

You've added a point to the map marked as a hospital or doctor's office, but in a completely residential area. I also can't find this address anywhere on your website (or any address for that matter). Unless you reply within 7 days showing that there is something here I missed, I will revert this change. Feel free to ask any questions you have

Since you didn't reply to my question on one of your previous changesets, I took the opportunity to adjust this area to use landuse=* and amenity=parking areas in the typical fashion. Let me know if you have any questions.

Thank you for reverting. Those turn restrictions are already in place, added as part of changeset/17169932 in 2013

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)