Hello, please try to save your changes in one general vicinity before editing in another to avoid creating such a large changeset box and having your edits queue up in OSMCha for places that you didn't make any edits in. Thanks.

Hello, please try to save your changes in one general vicinity before editing in another to avoid creating such a large changeset box and having your edits queue up in OSMCha for places that you didn't make any edits in. Thanks.

The legal status of a populated places should not matter when it comes to linking them to the trunk network. Arlington, for example, is a census-designated place, however it is tagged as a city and is linked to the trunk network with highways like US 1 and US 50. It's mainly all about population, and collectively, the Bon Air-Tuckahoe-Short Pump area has somewhere about ~100k residents.

For the US, the popular idea that trunk classification should only be applied to limited-access highways isn't really relevant anymore as it's been shifted to major highways and roads that connect significant populated areas and major transport hubs like airports and seaports. This has been documented in various OSM Wiki pages for most states, including Virginia, which was created by me with feedback from other people during the creation process:

osm.wiki/Virginia/Highway_classification

A couple corrections though, VA 37 is all the way up in Winchester, and Parham is unsigned minus the section between US 1 and 95 where it is VA 73. And a lot of the highways that are classified as trunk in Richmond were trunk before I touched them if I recall correctly, such as US 60 between VA 288 and VA 150 and US 360 west of VA 150 as well as northeast from I 64.

This section is a continuation of the partial ring road formed by VA 150/895 and does serve as a link between large towns like Short Pump/Tuckahoe and Hopewell/Petersburg as well as an inner bypass of Richmond. It's also alright for trunk roads to have driveway access, especially since every trunk road in the Richmond area has driveways when you look at them closely.

Why do you believe it should be primary? This is the most direct link between I 64 and Chippenham Parkway and connects to the southern Tuckahoe area and Bon Air.

These should remain motorways, as they have freeway-to-freeway connections with the Interstates and sufficient grade separations.

Thanks for updating me on that, I've updated the construction of the trail now.

Hello, I left a comment on your previous changeset explaining that the expressway=* tag is used to specify whether a road is an expressway or not, and that this section has expressway=yes added to it. This does not yet render on OSM Carto (which is used as the standard layer for OSM) but does for some other highway-centric map styles.

The indication that this is a bypass/alt route of the I 66 tolls is that the trunk route begins at the ramps connecting to I 495 rather than past them. The freeway-like segment of US 50 to the west of these ramps serves the same purpose as what it does up to I 66 by Fairfax.

Please do not add made-up names to objects on OSM.

I have reverted this changeset and all other changesets you made to NV 160 after this one. One speed limit sign does not indicate the speed limit of an entire road, and it should be assumed that a road with so many traffic signals and driveways does not have such a high speed limit.

You're also citing Google Maps as a source, which is illegal to do as it is copyrighted data.

Expressway=yes tags are added to this segment to imply it is an expressway, it should be reverted back to primary. Non-motorway highways need to be classified based on their status as a route rather than their physical construction, and there is an ongoing project to eliminate roads classified solely on this basis throughout the US.

I should also note that there are many other instances of primary roads in the area with freeway-like interchanges, such as along Franconia-Springfield Parkway, Franconia Road, Duke Street, Leesburg Pike, as well as some in DC and MD along Military Road, Suitland Parkway, and the three Capitol Streets.

They're functionally residential collector roads, often indicated by the double-yellow centerlines, which handle heavier amounts of through traffic to nearby subdivisions. There are other roads similar to these in Dale City and Lake Ridge as well as throughout suburban Fairfax and Arlington Counties, and tertiary has been established to identify these roads as such.

Though the community might not like it, it's clear by the heavier amount of traffic and more-visible tread marks on the roads that these do form an alternative route from US 29 to Glenkirk Road, bypassing Linton Hall Road. Despite having traffic-calming obstacles like low speeds, speed bumps, and stop signs, these particular roads and the aforementioned examples I gave are still heavily trafficked as through streets and are designed in a way to handle the handful of traffic that uses it as such.

I've removed these nonexistent features and incorrect building tags. I am guessing that these edits might either be some fantasy micronation mapping by someone who lives at this property or deliberately incorrect mapping to improve their experience in a crypto-based property management game that uses OSM data.

Whoops, thanks for pointing that out. I must have quickly copied some of the trees and pasted them with the tags of the trees I copied them from. I've fixed it now.

I think OKC Boulevard should be tagged as a motorway at the western section, and primary for the rest of the route with expressway=yes at the non-surface street sections.

An expressway would be any non-motorway road (or section of road) that has motorway characteristics, such as;

a dual-carriageway, high-speed highway with a mix of grade separations and signalized intersections, driveways, etc. (like US 75 from Tulsa to Bartlesville);

a freeway that is undivided and/or low-speed (like the Duncan Bypass);

a two-lane highway designed to have a limited amount of intersections and a lack of driveway access (such as Gilcrease Expressway from its western terminus to where it becomes a motorway).

The access control, speed limits, and median all play a part in whether or not a road should be tagged as an expressway. It's a confusing, but useful tag.

I, and I'm sure everyone else, am not trying to be as hostile and I apologize if it's coming off that way. It can simply get tedious to have to explain over-and-over what has been happening for the past 2 or so years regarding the OSM trunk network in the US just to be ignored or have the explanations dodged. All states need to be agreeing to and consistent with this major project and its guidelines if we want it to be completed. Hopefully you understand where I'm coming from.

Hello, trunk roads that are stubs and lack a connection to another motorway or trunk route at its terminus or those that are bypassed by highways that are better for long-distance traveling (such as I 40) are better fit with highway=primary and expressway=yes. The segment of OKC Boulevard between I 40 and Klein Avenue could be tagged as a motorway as it is a freeway spur, but the rest of the route is more of a business loop with some expressway sections and should not be tagged as trunk.

I wouldn't call it a stupid move, I think it's just looking from a perspective different from what's agreed upon. I've just now reverted this changeset.

Having it follow Goldsboro Road to River Road is definitely a good idea, considering that's the route most traffic would take to get between the Beltway and Downtown Bethesda.