I guess it's so that left turning cars don't clog up Grand Central between the two signals since they're so close to each other. It definitely made more sense for this jughandle to exist back in the day before Project NEON when there was a ramp from Grand Central to I 15 N that utitlized Iron Horse Ct.

It's a jughandle—traffic coming off I 15 making a left onto Grand Central Pkwy has to use this road to get to it and cannot directly make a left from the ramp.

The Fredericksburg Battlefield is just one component of the Fredericksburg and Spotsylvania National Military Park located in the city. The park itself also includes the Chancellorsville Battlefield and other nearby historic sites like the Old Salem Church. The official name for the park 'Fredericksburg and Spotsylvania National Military Park' is also present on the signs for all sites included in the complex.

I will respond, because not everything you don't like is "bait".

This antagonistic behavior, lack of willingness to communicate like a mature adult, and carelessness in preserving old objects that were mapped years ago that you've shown poses a higher risk of getting blocked from editing than you reporting me for reverting your deletion of many multiple year-old place nodes or for me simply editing in Fredericksburg because I don't live there despite it being down the road from me. The fact you used open GIS data as a source and mapped out places that technically don't exist as neighborhoods shows me it doesn't really require someone who lives here to edit here.

Reminder, you live in Fredericksburg, not inside of the software you are voluntarily contributing to. It's a community project that anyone can contribute to regardless of where they're from. If we had to map in only the places we lived in, the map would be disastrously incomplete.

I'm giving you the chance to get yourself together and even gave you a thorough explanation of what you did wrong and what needed to be done instead. If you want to keep acting like this towards other contributors and report me to the same people that I already regularly communicate with regarding disruptive editors, I cannot stop you.

If you believe this is rude, that's a misunderstanding on your part. I'll admit that I should have given a heads up first, but when incorrect edits are made, regardless of their effort, they should be fixed. In the edits you made, you deleted a bunch of neighborhood nodes and replaced them with areas instead, which removes their labels from the map, and then mapped out subdivision boundaries as neighborhoods, creating duplicate areas for places that aren't colloquially known, such as Brent's Mill. Subdivisions are landuse planning areas, not places that locals and visitors would know by name. Neighborhoods, which generally overlap subdivisions, should be nodes if they have unofficial boundaries, unless they can be officially defined with boundaries in which case they can instead be their own boundary relations.

I should also mention the current primary section of Valley View south of Sahara makes sense since there is a higher AADT and larger lane capacity, since this section picks up where Rancho left off as the main north-south arterial nearest to I 15 before the AADT drops again when Las Vegas Blvd takes over as the main north-south arterial in the area.

Valley View doesn't serve the massive amounts of traffic nor greater connectivity through the valley like Jones and Rancho do. Secondary seems ideal in this scenario, since a secondary road is still a major road, just not as important as THE most important intra-urban roads that the primaries normally are. Primary classification also isn't necessarily a requirement for a road that intersects an Interstate or major freeway. College Dr, Auto Show, and Galleria all have interchanges with I 11 as secondary roads.

Prior to 2021, highway=trunk was used extensively for classifying major urban boulevard-like arterials and expressways such as a Lake Mead Parkway. Years ago, Las Vegas Blvd and Paradise Road were also incorrectly tagged as trunk roads.

Spurs not particularly being an issue doesn't imply that Lake Mead Parkway should be a trunk road. Remember that trunk road classification is based on importance, not physical construction. Lake Mead Parkway only connects the Henderson suburbs to the Interstates rather than linking a major standalone community or providing a logistically important through route between other major highways.

I think this should just remain a motorway rather than be tagged as a primary road with motorway=yes, which is not a widely used tag and is redundant when highway=motorway essentially means the same thing.

I don't believe a name showing up in an assessor map necessarily means that's the name of the road—just the name of the right-of-way for a potential future road that does not yet exist. These track roads lack signage, have no properties addressed to them, and are informal and are typically formed as a consequence of maintenance vehicles/OHVs/traffic seeking out shortcuts so I'm not really inclined to have them named as the roads they exist within the right-of-way of.

I wouldn't really worry about it or overthink it since it's kind of arbitrary, and the road technically doesn't exist yet because it's under-construction. As long as the primary route isn't being extended past this intersection/onto other roads there's nothing that needs to be done necessarily.

Hello, why were motorways mapped over the roads here?

The major difference is that they aren't bounded by toll booths like the Lake Mead NRA roads. 160 is a major route that links Pahrump to Las Vegas, and 159 links 160 to Summerlin. They serve larger amounts of traffic that aren't solely visiting Red Rock Canyon.

Theoretically, yes, it does link Moapa and Henderson, but unless enough people were willing to spend $25 to take a worse road with no services for it to act as a major commuter route, it doesn't really serve a valuable role in general travel. In a scenario where Northshore Road does not require a park entrance fee to use, primary would make sense.

Ignoring these factors and simply focusing on creating a route that renders more consistently, i.e. attempting to link two primary spurs, can create a hazard for anyone using an OSM-based router that either ignores tolls or they have tolls enabled, being unexpectedly led down a route with a costly toll and hardly any services like gas stations simply because it was tagged at the same level as a highway like US 95 or Route 160.

If you're focusing on tagging roads from a navigation-based perspective, it's best to imagine essentially every road that requires a pass or specific status to use as a giant, unroutable void (like park roads only accessible through toll booths or roads on military bases closed off by checkpoints) to get the best results, since these roads are no useful for general travel and cannot be accessed like a normal public road or even a toll road that is specifically built for regular traffic.

I have noted before that this isn't a through route at all. It wouldn't be worthy of primary and barely makes it to secondary since it is essentially only accessible to traffic visiting the Lake Mead NRA. All through traffic going from anywhere north of Vegas along I 15 or Moapa (and vice versa) towards Henderson will be taking the Interstates, which aren't just free but also faster.

Highway links are generally tagged to match the road of the greatest classification that they are connected to. Likewise, way/145047535 retains its trunk link tags despite it leading to a secondary road. See here: highway=trunk_link

This huge box was a complete accident. I meant to save this as two different changesets. Didn't realize this happened until just now. My apologies!

Beale Street should remain trunk until the interchange is open. Tagging it as primary effectively creates a gap in the trunk route. It should probably also remain a trunk road until all movements between the Route 93 alignment and I 40 are open.

Not every highway with a ramp or interchange is a motorway. What would make this short segment more of a motorway than Route 78 bypassing Westerly or Route 1 in Narragansett. You seem to use what the state officially designates a highway as when classifying roads, so I think it's relevant for me to bring up that RIDOT does not recognize this stretch of road as a "freeway or expressway": https://www.dot.ri.gov/documents/maps/Functionalmap.pdf

Furthermore, "you're not from here" is a very poor, territorial excuse that is pointless when road classification relies more on the general knowledge of the US highway system more than being a local to the area. Your assumption that I have not been on these roads is also false. My mother is from the Boston area and grew up in East Greenwich, so I have visited this area frequently and specifically have been to Aquidneck and along these roads on a previous vacation to New England I had with my family.

Regardless of whether or not I have even stepped in the state of Rhode Island, OpenStreetMap is intended to be a collaborative project, not one where every user controls an area. The "I'm from here, you're not" argument seems to be a quick cop-out anyway judging by your lack in willingness to have constructive discussions even with locals of the areas you edit, as I linked in a previous comment.

I should also not that I made this edit since this stretch of highway is not part of Route 24, which is tagged as a motorway, but rather a part of Route 114 which is a trunk/primary road. It should not be tagged as a motorway because of a single interchange or because of another motorway branching off of it. From an on-ground perspective, traffic going south on the primary segment on Route 114 is not going to enter a freeway for barely a quarter of a mile before continuing on the trunk section, it's going to simply continue along the same non-freeway road that passes through one partial interchange with a different highway.