Hello Paul,
Welcome to OSM. I am going to revert this changeset because the frontage road is not this high up in the road hierarchy. If you have questions go ahead and ask me. Thanks

also https://www.fs.usda.gov/ivm/

source=Bing aerial imagery; survey

*From the lower bounds of this changeset

Alright I looked and fixed all the mistagged bridges and culverts along the RR and interstate up to about the CalPortland plant.

Do you know what objects were conflicting and if so can you send them?

I think the angle was meant for the tilt of the roof. I think I just used the wrong tag for the direction. This was quite a bit ago so I don't really remember. Do what you want to the tagging.

-BubbaJuice

I think JOSM didn't upload the ways of the changeset. I'll try and fix this up later today.

Source from Strava Heatmap and USGS 3DEP aswell.

Source from Strava Heatmap and USGS 3DEP aswell.

I'm not sure what happened there I was just using the iD turn restriction editor.

Lanes should not be added as individual lanes unless there is physical separation between the lanes. See osm.wiki/Dual_carriageway#Examples.

Don't add buildings that don't exist. way/1057418851

Thank you.

Yes, sorry it was a copy+paste error. Thanks for catching it.

Also Esri Clarity

I think the research part was in the Pima County dataset. When I look at https://edits.nationalmap.gov/apps/gaz-domestic/public/search/names I couldn't find the gnis tag with that id. What are you using?

There used to be some nodes instead of areas. I recalled they existed when I got the polygons so I had to manually search for them because I had deleted them before that, funny enough. I noticed that the gnis tags got removed at the time as well but I decided to keep them. Perhaps you could use the "was" prefix. ie. "was:gnis:feature_id=37196"

Yeah sorry I forgot to remove those and the correct tagging. I'll fix things up today.

"Brownfield" is not used for farmland. See landuse=brownfield