Hello,

I think highway=primary for Route 100/Pottstown Pike through Eagle might be too high of a classification, since traffic passing through will most likely take the bypass while Route 100 here serves a business route and only connects to tertiary roads. Given its relatively high traffic but low relevance to long-distance traffic, secondary would be the best classification for this segment.

For the US, trunk classification used to be applied only to expressways, boulevards, and other high speed or high-capacity roadways, but now we have access_control=partial and/or expressway=yes to be used on any classification of road (excl. motorway), and highway=trunk is used primarily for major intercity highways or significant commuter routes of any physical characteristics.

I was the one who restored the city tag, not Nguyen.

Ironic that you want people to discuss before changing place classifications considering you were the one who went and changed them all first.

Road numbers do not dictate a road's classification. I have discussed this with you at least once or twice with you before. Perhaps if you stopped creating new accounts to circumvent discussion, you would notice it when people talk to you.

Hello, I was the one who created this very short motorway some years ago but then also recently retagged it down to primary. I don't think motorway is the proper classification here due to its very short length and that it only has two and a half interchanges. Best classification here would probably be primary with expressway=yes tagging.

Hello, the West Chester Bypass should not be classified as trunk since it only terminates at a primary route, so the best classification for it would also be primary. Trunk routes cannot abruptly terminate at lower roads in the hierarchy, except for some rare cases, like at ferries or at the end of an island, peninsula, or valley.

Church Street I downgraded from tertiary to residential since it serves as a minor street in the grid rather than as a through street or collector road. As for its residential classification as opposed to unclassified, these two tags are nearly interchangeable and their usages vary by the user. Some my apply unclassified to a road that might possibly slot between a residential street and a collector road in the hierarchy, but some might also use it to slot below residential as a very minor service road-like street. It doesn't really matter too much which you use, though, because they both render the exact same as each other. I personally use unclassified for access streets on campuses, hospital grounds, airports, industrial areas, commercial areas, etc. or more-rural roads in agricultural areas, typically unpaved ones. All in all, it doesn't really matter which one you use.

As for driveways vs. parking aisles, these two also render the exact same here, but there might actually be some third party renderers that use that data more different than residential vs. unclassified. I tagged the access road to Wendy's as a driveway since it's not just a parking aisle, but also provides access to the drive through and the whole business itself. If this parcel of land right here was only a parking lot, I think parking aisle tags would make a lot more sense. Or, if there was a larger parking lot with separate aisles spurring off the driveway here, I would tag those as parking aisles.

I retagged it to secondary instead of secondary link since it technically serves as the other carriageway of the road for that short distance rather than as a slipway as it's the only way for traffic to get from Industrial Park Road and onto Research Center Drive. I'm definitely more inclined to keep typical slipways like those at Prices Fork and Toms Creek/Stanger or Southgate and Duckpond as highway links instead of mainline roads since they only assist vehicles making turns and aren't part of the road itself.

Hello! Thank you for adding these roads here. Just a tip for the future, remember to use expanded street name suffixes instead of abbreviated ones, like 'Place', 'Street', and 'Drive' instead of 'Pl', 'St', and 'Dr'. This is the standard format for OpenStreetMap.

Please do not change US 20 through the I 15 interchange back to motorway. It passes through signalized intersections and has a sidewalk plus a 35 mph speed limit, therefore not meeting the requirements for motorway tagging.

No worries! I'm going to restore some of the original highway classifications so that they conform with the US highway classification standards—at least for the time being. Thank your for cooperation and communication.

Functional classification doesn't exactly match 1-to-1 with OpenStreetMap's definitions of highways, and shouldn't be the source of classifying highways. It is difficult to generalize since it's a case-by-case basis, but, instead, we base road classification on how a highway serves from a connectivity standpoint and how it compares to other nearby highways, with secondary criteria like traffic data and physical characteristics sometimes playing a role in this process. When using this criteria is applied, it also avoids confusing dead-end primary routes like PA 113 in Phoenixville.

Around the East Coast, places tagged as towns like Leola and New Holland are typically linked to the road network with primary roads or higher (trunk/motorway). It may also be of reason to tag PA 29 from Phoenixville to Malvern as primary for this same reason, also considering its connections to motorways (the PA Turnpike and US Route 202).

The OSM Wiki has better explanations than I do for how highways are being classified, talking about specific classifications and why to avoid functional classification: osm.wiki/United_States/2021_Highway_Classification_Guidance

What are the reasons for the highway reclassifications you're making? Particularly why Route 23 was downgraded to secondary and the reasons for these new primary gaps and stubs around Phoenixville and Norristown.

Let me get this straight:

Coincidentally, multiple new OSM users suddenly have a fixation on reclassifying populated place nodes and highways around New England, which boasts an ever-expanding roster of edops, miela404, cm81447, and edemes, who all, for whatever reasons, have the same intentions and mannerisms. Is that correct?

Or, you are edops and are on your 4th alternate account because you want to avoid any confrontation from other contributors because you want to keep changing things everyone has vowed not to change or discuss beforehand.

If the second answer is true, then please, like we have been begging you to do at this point, just communicate, because edit warring is pointless when things can be undone at the click of a button and a block evasion is worthless when you insist on making the same edits and using the same comments when making them.

Road numbers very rarely reflect a road's place in the highway network of the US. In the age of digital maps and GPS, road numbers on minor collector roads like these are a relic and mostly reflect how a road is maintained (in this case, by the state) rather than how important it is. Route 96 only links to some small rural neighborhoods around East Boothbay, without any connection to other secondary or tertiary roads. Ignoring the designation, that is enough to conclude that secondary is overkill for a no-outlet rural highway, and small-scale edits like these don't necessarily need to be discussed.

Hello! Do you know the exact issue were you having with bike lanes not being properly displayed with Route 140 being tagged as a trunk road? Bike lanes added as tags to a road won't render in the standard OSM map regardless of a road's classification, rather only when it is a separate way tagged as a cycleway, which is used for things like standalone bike trails or protected bike lanes. Perhaps you're using another renderer than the OSM standard map layer?

Meant to say west instead of east. But a trunk road terminating like that with a primary route with no connection to any other trunk highways or motorways means it is a trunk stub, by definition of OSM.

A trunk route that does not connect to another trunk road or motorway is a trunk stub/spur. The trunk section of Soldiers Field Road that you reinstated and extended only terminates at a primary route when trunk roads are intended to link to other trunk roads and motorways to form a fully-connective network.

In an urban scenario like this, trunk roads would be the major commuter routes for getting across town and should not abruptly end at roads of a lower classification. SFR continuing east from the Eliot Bridge is much more important as a through route, connecting Fresh Pond Parkway to the MA Turnpike before becoming Storrow Drive and heading towards Downtown, while the section east of that junction simply terminates at Beacon Street without a connection to any other major highways.

Can you clarify why my edit is "wrong"? This is by OSM definition a trunk stub.

I have reverted Storrow Drive from motorway back to its original trunk classification. It has characteristics you would find on a controlled-access highway, but it isn't a freeway. Its speed limit is only 40 and has some sections with sidewalks and at-grade street/driveway access.

changeset/154868242