Can you confirm if NC traffic laws prohibit left turns across painted medians? Not all states restrict this sort of turn, so such turn restrictions shouldn't be added to OSM unless required by state law or explicitly signed.

I was just about to fix them myself and saw that you did. Thanks for getting those. I did change back the ones that fell in the area of the work I was doing on the East End Connector, and then I had to resolve an issue from another mapper that involved deleting and recreating some of the ways, and that definitely didn't help reduce the number of conflicts for you...

Please be more careful in merging ways. Some on the Durham Freeway in particular had construction: prefix tags as part of the East End Connector project. For example, the road won't be widened to three lanes in each direction all the way down from the connector to Ellis Road.

Why did you add bicycle=no to many local roads with no posted bicycle restrictions? bicycle=no on a road means that cyclists aren't allowed to use it at all, which is rare.

Additionally, motorway status on a road implies total restriction to motor vehicles only, so bicycle=no (along with foot=no) is not necessary on motorways.

Do you have a source on those turn restrictions under NY state traffic law? Some states restrict left turns over "painted medians" (a term not used everywhere), but not all.

Aaaaand now they're all gone. Thanks for catching that!

It means I'm an idiot who forgot to remove that tag after using it to repeatedly select a bunch of things in JOSM... I'm working on the next section of the Urban Loop right now, so I'll have all of it removed in the next changeset.

US 74 is not a motorway here. The motorway class in the U.S. is used exclusively for controlled-access freeways, which US 74 is not. Though all the median crossings along this stretch were removed and replaced with interchanges, there are still numerous driveways and side streets, disqualifying this stretch from being considered a freeway.

Why did you mark I-277 along the portion of NC 16/Brookshire Freeway west of I-77? This section is not and has never been a part of I-277, so I reverted this change.

Hello. I noticed you remapped the section of US 11/15 between Amity Hall and Selinsgrove as a motorway. The motorway class in OSM is used to represent controlled-access freeways, nearly universally (with very rare exception) restricted to motor vehicles.

US 11/15 here features many at-grade intersections and is thus not controlled-access. Instead, it is mapped as a trunk road, which is used for surface expressways (limited-access roads), major high-speed divided highways, and vital interregional links. It is also not restricted to motor vehicles, even carrying BicyclePA Route J. Please take this into consideration in the future.

I have no idea how, but you accidentally moved a piece of US 422/Penn Avenue near Sinking Spring, PA and superimposed it over a piece of nearby Woodside Avenue, which also ended up with a gap in it. I've fixed these, but I'm not sure if anything else was accidentally messed up in this changeset.

Do not map solely based on satellite view. It's clear that you did because the US 422/Ramona Road intersection was reconfigured within the past few years. Most imagery available in the various OSM editors is too old to show this. When something is mapped with great detail, yet is radically different from satellite imagery, the imagery is most likely outdated.

I should also add that when a ramp splits again after diverging from the freeway mainline, the node of the subsequent split should not be given the same ref as the split from the mainline. It should be left blank unless specific exit numbers are signed at the split. (For example, a ramp signed as Exit 42A-B from the mainline, subsequently splitting into clearly signed Exit 42A and Exit 42B.)

Please don't add destination information to the motorway_junction nodes. Exit destinations are placed in appropriate tags on the ramp way (i.e. destination, destination:ref, destination:ref:to, etc; see osm.wiki/Key:destination). The exit_to tag was used in the past, but these days, the only things that typically go on motorway_junction nodes are exit number information and proper exit names. The latter are rare in America; the PA Turnpike's named exits on the ticket system are a prime example.

We do have an accepted official_name tag exactly for cases like this where something has an official name different from the accepted widely-used name.

That being said, with it certainly opening within the next week, I'm not sure it's worth reverting at this point considering how many small things need to change. I'll clean up your edit and mark it complete.

Source on the new road being open already? It definitely didn't open on New Year's and I find no news articles for its opening today.

I've reverted the southernmost portion of the US 301 spur road to highway=proposed when you had marked it as construction. The spur road was graded with construction of the mainline, but will be seeded with grass and not paved until the entire spur road is built, so it is not currently under construction.

I can't speak for the rest of the world (I know there are many trunk roads in the UK with no intersections), but motorway in the U.S. has been synonymous with fully controlled-access freeways since the beginning, as far as I can tell. Controlled-access means no intersections.

I-93 through Franconia Notch is absolutely dual-carriageway because the directions are separated by a physical barrier. It's no less dual-carriageway than the Pennsylvania Turnpike.

Tisdale is a freeway south of Gilcrease. Gilcrease is a freeway east of where it widens to dual-carriageway. The aforementioned segments should be motorway and the remaining segments of each road should be trunk.