Hello,

Thanks for marking this as open! However you made an easy-to-make mapping mistake. In the editor there will be an easy way to ignore warnings of crossing highways by simply clicking "Add tunnel." However, in doing this you are adding harmful and incorrect data. (ie. way/1528338833/history) Please physically connect the highways next time with a node with the tags highway=crossing. Thank you!

BubbaJuice

https://www.traversecitymi.gov/government/city-departments/public-parking/parking-rates-and-payments/parking-rates.html, https://experience.arcgis.com/experience/397113f1426a4e509e1f4a72692c8111

Great thanks!

Also the dataset in your source doesn't have this region included?

ie. way/1485094835 & way/1492309473

Hi,

You made many duplicate substations in this changeset, some of which have not been corrected.

Thank you,
BubbaJuice

I don't see any instance of the reference you tagged: "SZ"

Hi Sanjana,

This was just a simple parking-lot resurfacing. See here: https://www.orovalleyaz.gov/Government/News/Community-Center-parking-lot-resurfacing-to-begin-March-26
For construction like this, I would avoid deleting or modifying ways outright. Instead I would tag them as highway=construction or, preferably, using access:conditional=*. This wiki article discusses this concept: construction=*. ("Already existing features may be closed ...") It is preferred to use this because OSM data is often consumed somewhat infrequently so real-time updates aren't very useful if they are short in duration because they could break the map for these infrequent updaters with long-time use cases.

I visited the parking lot today and was able to confirm it was how as it was before the resurfacing, with the complete parking lot open.

Thank you,
BubbaJuice

You damaged the parking lot in this changeset, deleting several correct nodes. I will be fixing it in my next changeset.

Is the SunZia line now operational? What is the source of your reference on the line?

Thanks,
BubbaJuice

Yes, this multipolygon is massive and I really don't like these large polygons because, especially in desert landscapes, there is a lot of variety in landcover. However, this one isn't that bad because all of this area (with a few exceptions) is covered by low-density shrubland (unlike some areas that tag entire mountain ranges with complex forest-scrub areas as a general tag).

There's a lot of purposes that landcover serves but regardless I think that OSM should reflect the ground truth. This area is not sand, but an "Open Shrubland" (https://en.wikipedia.org/wiki/Land_cover#Types) and I think that OSM has adopted natural=heath for this landcover. To show the complexity of this environment, you could use density=* and surface=* or something similar and document the nature of this landscape.

Would you be okay if this was discussed in a channel with more users to give their opinion on the matter? We could do it on the Forum, US Slack, or OSM World Discord. (I see that you have asked in the Slack before but there wasn't too much input). I understand the issue though and OSM doesn't have enough diversity in landcover to classify these areas as one extreme or the other.

Joseph,

The light shrubbery makes this area heath. You can see my guide: osm.wiki/User:BubbaJuice/Heath_vs._Scrub. This shrubland may not be very dense, yet it is not natural=sand.
natural=sand should be reserved for bare sand or sand covered by seasonal grasses. I will be changing this back, if you don't oppose.

Thank you,
BubbaJuice

The way that you made here is not a bridge. way/1377330058 Please avoid making false bridges such as these.
Thank you,
BubbaJuice

Thank you but be careful! You wrongly changed the surface tag for way/16899434.

1. Probably sourced from the linked pdf, however it appears to be a dead link now so I cannot verify that.
2. Put simply, if a transmission grid is fully mapped, you can see where the lines connect and interact. Lines that connect have the same voltage. Therefore, from existing power lines or power lines from known sources, these spur or connected lines can be determined.

If you look on OpenInfraMap (https://openinframap.org/#12.34/35.07433/-106.60227) you can see the physical separation between voltages and it is clear where the boundary is. Let me know if you have any more questions.

BubbaJuice

& Strava Heatmap

To avoid remaking objects, look at the "Split" tool in any editor, where you can split an object into two segments which might make your mapping easier.

Also, the main reason why we don't retrace things is because of the OSM principle "Keep the History" osm.wiki/Keep_the_history.

Avoid connecting roadways to landuse or boundaries. Also, make sure that when you are updating something, like a road, that any other objects that made have changed are updated to. So for example, there was a trailhead parking lot (way/855741080) that now is gone because of the construction, and thus should be removed. I've updated these in changeset/182274121.

Yeah don't map turn lanes separately unless there is a physical barrier. To map turn lanes, refer to the wiki osm.wiki/Lanes.