Thank you for letting me know. These edits appear to all be incorrect and I have reverted them and left them a comment. This person seems to be a bit reckless with their changes, as they are updating highway construction through StreetComplete seemingly without checking if the roads are open first. In fact, I don't believe there's any actual surveying going on as they site in their source, in person or through online sources, since they're rapidly editing all over the place. Previously, they incorrectly updated a road near where I live that had only started construction this year (and is still going through the grading process) to a completed road. If you at some point come across any more edits of theirs that seem suspicious (especially roads around the Virginia/DMV area), I'll gladly look into them.

Hello, please be more careful when updating under-construction roads. The two under-construction highway ramps you changed to open motorway links no longer exists, and the section of Commerce road which was tagged as under construction is not open yet and was not given proper highway tags when you updated it. Thanks.

Hello, what is your source/reason for tagging Summit School Road as open? Construction on the project only began earlier this year and completion is not slated until mid-2026. https://novagateway.org/Dashboard/Overview/36

Thank you for adding the paragraph regarding these classification gaps and clarifying the reasons for the other roadways' classifications.

In response to the classification of side streets which connect primary roads to motorways—I classified it as primary not with the expectation that it wouldn't be properly navigated by routing systems if tagged lower than primary, but rather from the standpoint that if the section of road is used primarily to get from a primary road to motorway link or vice versa, primary would make sense and would accurately reflect this usage. It would not be a disconnected primary stub as it would meet a road of the same classification (primary) at one end and a road of a higher classification (motorway) at the other.

Regarding two more changes I made that have not yet been discussed in full here yet:

One change I made was downgrading a section of US 7 in Danbury to trunk as it was nearing the terminus of its motorway segment and was undivided at that point. I had seen the state classification guidelines prior to this discussion and how the motorway classification guidelines stated that they must be divided, so I would have assumed that my edits were correct. Another rationale for the change is that the US 7 freeway is at its terminus here, and that traffic entering from Miry Brook Road is technically not entering a 'motorway' if such road is undivided and is 1000 feet long before it becomes a standard undivided highway.

The other change was upgrading a short section of Columbus Avenue in New Haven which was classified as residential to tertiary to bridge a gap between the primary route in the west and short tertiary segment in the east. This is under the assumption that traffic travelling between the primary section of Columbus Avenue and S. Orange Street are not taking Church to Union, back to Columbus, and up Orange and that this specific section of Columbus functions as a local residential street.

I considered reaching out to jnighan at first before hesitating and ultimately deciding against it because I figured it would not be productive to converse with another person over some few hundred feet of roadway on the map. That's not reaching out to any community (just one person who has documented highway classification in the state), but community consensus for minor edits should technically not be required in the first place. I understand that it's not about all edits in Connecticut—just road-focused ones—but I still cannot see how minor edits to the road network could create accumulate so much so that it turns into a mess, even without aggressively monitoring every change that happens in the state.

I myself have documented road classification in my home state of Virginia and am responsible for much of how the major roads are classified. If someone adds or removes a trunk or primary route, I'll scrutinize it and likely revert it—I'd expect the same thing to happen in Connecticut or any other state with documented highway classification. However, I would not expect myself or anyone else to scrutinize a change to a roadway so small as 1000 feet of undivided highway or a median break at a signalized intersection, especially if the edits are not breaking anything or going against any proposed state highway guidelines.

You are correct about it being frustrating to me because I feel that it's counterintuitive to require that anybody have to reach out to a particular contributor for confirmation over relatively insignificant edits. If this is procedural for when responding to the edits of a more-experienced editor like me, then I am concerned with how you would take care of edits from new users who are inevitably out of the loop of any "discussion".

I do not yet know what jnighan's opinions on how minor road edits should be handled are, so I will contact him via Slack. As far as I know, though, it seems to mostly be up to you for what should and should not be reverted, which is anti-community in my opinion.

I apologize if my message sounds heated or disregardful, but as someone who has had countless encounters with territorial editors since day one of me editing OSM, I am concerned about the approach to "community" here.

One more note—please consider using more descriptive changeset comments to explain what you're doing in your edits so that it is clearer from a glance which kind of edits you are making. Thanks!

Hello, GeographRick, per the guidelines for the classification of motorways in the US (osm.wiki/United_States/2021_Highway_Classification_Guidance#Motorway), these small stretches of highway with grade separations which you have upgraded to motorways should not be tagged as such. A disconnected motorway should be at least a couple miles long and have multiple interchanges rather than just one, per the page I linked. Examples of correctly-tagged isolated motorways would be the Kokomo, IN bypass and the Wilmington, OH bypass.

Do innocuous changes like those which you have reverted actually need to be discussed beforehand? I don't see how changing frivolous bits of road (I'm talking less than a quarter mile long each) to fix highway connectivity or indicate that a very short highway segment does not meet OSM's motorway standards requires community consensus. Nothing would get done anywhere else if that were the case. I understand immediately reverting massive undiscussed changes, like if I were to reclassify a trunk route to primary despite it being documented on the OSM Wiki that such a road should be primary, or a particular road which has had its classification discussed before—things like that, but I don't believe that this territorial approach of monitoring each and every minor roadway edit in the state you live in is pro-community. You don't seem to give a true reason for reverting these edits aside from them being "undiscussed", when the vast majority of edits anywhere on OSM are undiscussed by default, or show me which exact venue I'd need to go to (Slack? Forum? Wiki?) in the event I were to discuss any sort of edits with the community.

Thank you for these edits! I was just editing around Stafford County earlier today and noticed how intrusive it was to add other point features (like neighborhood nodes) when addresses were separate from their respective buildings.

woodpeck had commented on a changeset of mine (changeset/160071661) about some edit warring happening here. I am assuming this all sparked from trespassers entering the property, probably from the other other side where there are driveways, to access the supposed trails that were mapped here. Upon looking at various aerial imagery and using Bing Streetside along Jackson Trail East, I am confident that there truly are no longer or have never been any viable routes here other than just trekking across the woods.

I was not aware that these ways were subject to an edit war, but I do know a discussion about them had happened: changeset/159812862

It's apparent to me that these roads do not exist. Without the context of them being subject to an edit war, I zoomed in with various aerial imagery and found no evidence that they still existed or existed at all. I then checked Bing Streetside at what would be the intersection of these roads and Jackson Trail East with nothing there either. I am nearly certain that these were just erroneously traced by TIGER, as usual and I have deleted hundreds of roads like these in the past. Around Virginia especially, it's not hard to find residential, service, and track roads traced over farmland or forest without any sight of them actually existing.

There was only one way that I could confirm existed, which was this driveway: way/1341100200#map=17/38.260891/-77.635896

I've just deleted these ways. It looks like they are former or nonexistent ways which were erroneously created by TIGER. Not sure why they were tagged as footways, though.

Assuming that you are edops a.k.a. miela404 a.k.a. edemes a.k.a. frillwed a.k.a. cm81447, I am in the process of reverting some of your more-recent edits and I am positive that you are aware of why they're being reverted since you keep deleting your previous accounts and creating new ones each time you're blocked or confronted.

Assuming that this a new user suddenly making large undiscussed highway/place node edits just like edops, with the same changeset comments as edops, and editing in the same exact region as edops, I am going to, for the time being at least, revert your edits, and I apologize that you have to be caught in the crossfire due to the edit warrer/sockpuppeteer in the region. If you would like to make mass highway/place edits, it is highly appreciated that these be discussed with other editors first, especially in a contentious area like this and/or if you do not 100% understand what changes you are making.

Hello, please do not reclassify properly-tagged roads on OSM so that they could be routed along in a third party app. Parking aisle and driveway tags were all used accordingly here.

Hello, the expressway spur of US 52/WV 75 should not be classified as trunk as it only links to another primary route at its terminus. Expressway characteristics on non-Motorway roads of any type can be identified with the tag 'expressway=yes'.

Hello. Generally, it is acceptable for 'shunpikes' that parallel toll roads to be tagged as trunk. See US 30 and I 70 around Bedford and Everett, PA, US 13 and DE 1 through Delaware, and US 50 in Fairfax County and Arlington, VA. Often times, these routes will see just as much, if not more traffic than the toll road. This section of Route 168 Business in particular sees ~1000 more daily traffic than mainline 168, according to AADT data.

Hello, Route 606 here should not be trunk as it does not serve as a major interregional route like Fairfax County Parkway or Route 50 do. The best classification here would be primary.

That's the name the road already had (partially). The church on the western end also is addressed to Crossroads Lane in records. The church's website shows that it's addressed to CR 128, so 'Crossroads Lane' could also be an alternative or historic name.

Not sure how I removed them but my guess is that it was accidental. I've readded the tags.