Not really your fault actually, another user moved it away from where it really is after I first added it

I will be reverting this changeset because you clearly did not check recent imagery before making this change

Forgot to say this but thank you for fixing it though

I'm aware JOSM doesn't do it automatically. I fixed all of the crossing highways warnings that were given to me in the validator

Thank you!

No, I probably just accidentally pressed my balloon key bind. I didn't delete when uploading because I thought it was an artifact from the importing of the boundaries in which case I didn't want to mess with it. It didn't come to me to see if I had made it or not. Thank you.

Reverted because you are putting bridges were there aren't any.

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