Heads up: SR 37 won't be signed along I-69 between Martinsville and Indianapolis, so it shouldn't be in the ref tag; only unsigned_ref. This is already in the note:ref tags along this section. It doubly shouldn't be in fut_ref on the closed section because it isn't "future" SR 37 at all.

Why do you keep reverting this? The "ramp" in question is the physical freeway mainline. I-83 bears off onto a ramp and the freeway continues, with US 322 immediately merging in. It being signed as a numbered exit doesn't make it physically a ramp.

Do you have a source on PA 299 still existing or being reinstated? It was cut back to just the railroad bridge in 2011, and even that is unsigned. I've reverted this change because I was unable to find anything to back it up. It's already tagged correctly with old_ref and unsigned_ref where applicable.

The very paragraph you quoted contradicts the edit you just made. This section of freeway (alongside the Brookshire Freeway) *are* connected to the greater freeway network.

Please stop demoting random roads from trunk to primary just because you don't think they're "special" enough. Significant length is not the sole deciding factor in whether a road qualifies as trunk. In the case of VA 28, it's a high-speed, limited-access road with expressway-like design (though not a freeway) and which carries significant traffic volumes. By established tagging conventions, it qualifies as trunk.

Please do not leave unhelpful changeset comments, and do not keep making the same edits if they are reverted. If you feel strongly enough about something, discuss it in the talk-us mailing list.

Do you have a source for these turn restrictions? Having driven this stretch of road, there is no signage indicating these turn restrictions, and to restrict left turns would certainly defeat the purpose of the median breaks that are already mapped.

Thanks for contributing! Just an FYI, objects on the ground by themselves are considered layer 0 by default, with tunnels being put on layer -1 and bridges on layer 1. Only when multiple bridges cross on different levels are higher/lower values used (e.g. layer 2, layer -2, etc.). Tagging a bridge with layer 2 and the ground-level road beneath it with layer 1 is unnecessary.

I believe I traced it from preliminary construction plans which were at the time available on a project website, though I can't find the website anymore, nor do I seem to have saved the image, unfortunately.

A partial screenshot of those plans is in the background of this PDF that I found from a Google image search, though: https://www.roads.maryland.gov/ohd2/GA6465270_Triton_TP.pdf

Well movable bridges on even Interstate highways aren't unprecedented, even on relatively new bridges like the Woodrow Wilson Bridge on the Capital Beltway. Even I-278 nearby crosses the Bronx River on a drawbridge. At that point it's less "there's a gap in the freeway here" and more "substandard freeways occasionally have movable bridges on them."

At minimum the bridges should be mapped as trunk roads.

It's not a motorway just because it goes on a bridge. It's a motorway because it has direct connections to motorways, especially the Willis Avenue Bridge, which connects on both ends. You can go from Harlem River Drive over the bridge to northbound I-87 without leaving a controlled-access, grade-separated road restricted to motor vehicles.

It was mainly a revert of changeset 88757155 by Fluffy89502, who was arbitrarily demoting motorways and trunks around the country and was called out on the talk-us mailing list a few weeks ago. It wasn't an exact revert, though, and I may have gone too far in a few places, namely the streets at the Brooklyn end of the Manhattan and Brooklyn Bridges. The way it is now is more or less how it was before Fluffy's edits.

This is a bridge, and the roads that pass under it are not tunnels. This is apparent from satellite imagery, so please check before you relabel bridges as tunnels.

Why did you add duplicate township/borough lines around Erie when the townships and boroughs were already mapped?

Hi, I noticed you made some edits to the I-77 Express Lanes interchange with Lakeview Road, adjusting the alignment of ways to better match the satellite imagery. This imagery is outdated because the Express Lanes project is finished. Please don't match ways to satellite imagery of construction unless you've verified construction is ongoing.

Additionally, the I-77 general purpose and express lanes were merged into a single way under Lakeview Road because there is an open entrance/exit point here, where there is no physical separation between the express and general purpose lanes.

I've partially reverted this changeset, retaining the main substance of this edit: the adjustments to the neighborhood boundaries. Mapping of I-77 and its express lanes was done based on the construction plans for the Express Lanes project.

According to NCDOT construction plans, there is no signal here; instead, there's just a stop sign on the off-ramp. Are you from the area and can verify that there is a signal on this side of the interchange as well?

Apologies for the absurdly large changeset area for what should have been a small scope. The edits took longer than I expected to complete and by the time I finished, some conflicts arose that I couldn't seem to fix without rebuilding the NC 24 route relation. As I work my way up the remainder of the I-77 Express Lanes, I'll minimize the lengths of the segments I edit per changeset.

Please let me know if I have caused any other issues and I will resolve them as soon as possible!

Please don't add exit destinations to the motorway_junction name tag. OSM convention is to keep destinations in the destination tags, while the name on the motorway_junction node is reserved for proper interchange names, such as those on the PA Turnpike.

Please don't tag roads as motorways unless they are controlled-access roads with no at-grade intersections or driveways.

I've removed the destination tags from the way you pointed out. I wasn't the one who put the tags there, since they existed for several prior changesets according to the way's history. The only change I had made to the way was removing an unnecessary toll=no tag, and I suppose I didn't notice the destination tags on it at the time. Thanks for pointing it out!