Roads should definitely not be classified based on their traffic volumes, or else city streets would be trunk and most major intercity highways would be tertiary and secondary. These two highways are either already bypassed by freeways or don't act as a major connector to other important roads or towns/cities. It's been heavily agreed upon in the US that trunk classification is for roads as important as Interstates, like US 15 or US 50. Please consider joining us on the OSM US Slack (https://app.slack.com/client/T029HV94T/) and things like these can be thoroughly discussed amongst the community.

Please don't upgrade small stubs like this trunk. Trunk classification is for important roads like intercity highways, not roads with high traffic volume or higher-speed design. This stub of MD 26 and that section of US 40 should be primary.

Hello, I had not realized that there was a note and that this section of road is now at motorway-grade. I just updated this section by dividing the carriageways to prevent others from making my mistake.

In all honesty, I don't remember making this edit since it was over a year ago and I'm not entirely sure why I did it, but I think it had something to do with me believing that this section acts more as a ramp connecting to I-15 rather than its own freeway carriageway. You can revert it if this is an official part of I-80.

Admittedly I should have waited for more discussion and consensus as well as provided justifications in my changeset comments. As of right now I have completed the Virginia city proposal and am currently working on Delaware, Maryland, and Nevada as well as adding a section to specify the criteria. Here's the proposal page that's being worked on: osm.wiki/User:Joseph_R_P/City_classification_proposals

Hello, I can't find anything on the OSM Wiki that states a city must have at least 50,000 people to be classified as such. There are also a lot of nearby cities which have smaller populations than 50,000, which were already and still are cities before I upgraded them, such as;

Cumberland, MD (20k)

Hagerstown, MD (40k)

Salisbury, MD (32k)

York, PA (44k)

Fairfax, VA (23k)

Staunton, VA (24k)

Martinsburg, WV (17k)

Morgantown, WV (31k)

There's also an abundancy of cities west of the Mississippi which have less than 10k residents tagged as cities in Wyoming, Nebraska, Montana, Alaska, Arizona, etc., but that might have to do something with density.

I think I should also point out I had also upgraded Ocean City, MD (pop. 7k) to a city. I had also upgraded a lot of cities throughout Virginia such as Manassas, Fredericksburg, Blacksburg, and Williamsburg, which all have a range of 15k to less than 50k residents.

Currently I'm documenting the cities I propose should be upgraded/downgraded as well as the ones that I have already reclassified with their justifications on the OSM Wiki on a sub-userpage of mine.

I think from here, city classification on the east coast needs more discussion before anything else changes.

I didn't really consider city being 'full service' as the sole or primary deciding factor when upgrading Elko to city, but I did consider to be part of the decision making in that edit as well as in me upgrading both Fallon and Mesquite to cities. The main two deciding factors for me are population and prominence, and those are also used by a lot of other users too, especially in New England and other northeastern states where the city and road classification went through a major overhaul.

I don't think I'll upgrade Elko back to city just now, since I'm planning on writing up a user subpage on the OSM Wiki on what I think the cities and towns of Virginia, Maryland, Delaware, and Nevada should be and why I think so to get opinions on proposals as well as document the ones I've already discussed with others.

I've mapped the redesigned intersection by holding my phone up to the computer, which had an image of the planned design pulled up on the screen, and roughly traced the new slipways and added the new stop signs. changeset/123992324

I upgraded Elko to city because it is the largest settlement in a nearly 200 mile radius. A city doesn't have to be as large as Las Vegas, Reno, or Carson City to be considered a city, see Alaska, Nebraska, Wyoming, and Arizona for example. The place=city classification, at least in the United States, is based on local prominence, not its population in an administrative area. If we went solely based on its size ranking in a state, then we'd have a ton of small cities/towns tagged as place=city in small states like Delaware and hardly anything in large states like Nevada.

After all, Elko is technically one of the largest cities in Nevada if you consider the Reno, Carson, and Vegas metros to be one city.

There was also a discussion I started about this on Slack: https://osmus.slack.com/archives/C02QVTSRHV0/p1655955010580079

btwhite92's comment on my thread was part of the decision-making for me upgrading Elko to city. Elko has a college campus, K-12 schools, a hospital, a proper city center, shopping plazas, amenities like museums, community centers, parks, and fairgrounds, and ongoing development. I think it makes most sense for it to be a city.

I meant to also add in my changeset comment that I mapped/adjusted some roads, footpaths, and buildings, which was the main point of my changeset, but I had forgotten to save it, got distracted, then made some other edits.

Hello, when adding numbers to secondary state highways, please use the prefix 'SR' rather than 'VA'. 'VA' indicates that the road is a primary state route, which are numbered 1 through 599, and 'SR' indicates that the road is a secondary state route, which are numbered 600 and above. Thanks.

I didn't pick the arena over the center since I assumed that the arena tags would be for large sports pitches surrounded by seats, but now that I look at it, the horseback riding center tags aren't any better since it appears they're for the entire facility. I've changed the tags.

Hello, mehdi_kalen. I just want to inform you that I have reverted all of your changesets, which have involved you upgrading many service roads to secondary and primary roads. Secondary and primary classifications are for major highways, not the main routes through parking lots.

In my opinion, there are some painted gores that matter, such as the ones between highways and ramps, as well as slip lanes with a painted gore (instead of the usual concrete or grass one) that have different traffic control from the road it comes off of (such as a yield sign whereas the intersection is signalized). I think the rule not to map separate ways "if the two directions are only separated by paint" mainly refers to when it's a two-way road with a painted line, median, or turn lane, so including the painted gores with the physical barrier should be fine.

I include painted gores with the ramp separation with the reasoning being that cars should not drive over them whereas a car can drive over a centerline to make a left turn onto a driveway or cross over a solid white exit lane marker to make a right exit.

It really all comes down to mapping style, because some people will map the ramp all the way down the merge/exit lane and some people will map the lane as its own way regardless of whether there's a slip way ahead or if it's just a standard left/right turn lane.

I'm not sure if there's a documentation or proposal on how turn lanes should be mapped standardly, and if there isn't one yet, for the time being it all comes down to what looks best in your opinion.

Those are some really beautiful ramp curves (not sure if you're using a certain plugin or tool to make them since I don't use JOSM that much, but I admire them nonetheless), but I do recommend keeping the smooth curves up past the painted gore where the ramp becomes a merge/exit lane, like how most are mapped in the US, to prevent the ramps from appearing as sharp turns like this: changeset/122186096#map=18/41.36828/-72.11514

There isn't any official consensus on how ramps should be mapped but it's been quite widely accepted to have ramps merge into/spur off of roads pre your ramp adjustments, however it's not much of a priority.

Alright, thanks for letting me know. I'll consider that next time I'm on my sidewalk/cycle path mapping spree.

Sorry for the late reply, I was not receiving any notifications for changeset comments. The reason I favor Riley, Brookside, and Vint Hill over Rogues is because the former provides direct connection to the population center and important amenities and buildings whereas Rogues Road bypasses it and probably isn't that important to through traffic anyway because traffic travelling between Warrenton and Linton Hall is more likely to avoid the Vint Hill area by following US 29 to VA 215 or SR 619.

The closest pair of roads in the area that I know of to compare these to are Cardinal Drive and Dale Boulevard in Dale City. Cardinal Drive is a newer, faster, and smoother route but Dale Boulevard provides the most connection.

Why did you downgrade this road? I had upgraded it because it is the main thoroughfare through this area and connects two primary roads.

May I ask you to please stop upgrading non-freeway roads to motorway? The US consensus is that motorway tags are for highways or sections of highways that are exclusively controlled-access (have interchanges, ramps, overpasses, etc.). Please also use more descriptive changeset comments that describe what exactly you are doing to the map. 'Added' and 'updated' are vague and could mean anything. Thanks.

Hello, please consider mapping businesses as buildings or points rather than as landuse so they can have proper Wikimedia-connected tags. If you do choose to map the gas station as the area rather than the structure itself, adding landuse tags is redundant.

This is another reminder to please use more descriptive changeset comments explaining what you are doing in the edit rather than where it is, especially considering none of these edits were in the Pennsylvania State University.