Hey, thanks for reaching out! So thinking about it, I think it comes down to two things:
A. Old habits die hard and this is one of them and
B. I've personally always found it easier to recreate geometry because it helps me visualize all of the attributes. Examples from this edit are turn restrictions, refs, destination:refs and when I'm feeling ambitious, lanes, surfaces, names, alt_names, prefixes, etc.

I know that recreating the geometry erases the object history which is important in some cases and to some people. I'm not big on object histories unless its in regards to objects that I have never visually surveyed. I am trying to make a more concerted effort to be cogniscent of other editors and what is important to them as well as provide meaninful updates here in the valley.

I hope this gives you some insight into my editing style and how I approach editing. Let me know if you have any other questions. Happy to answer!

Hello,

I want to preface this with the fact that I believe you mean well when you perform edits in Northern Nevada.

I checked the history on this way and it looks like this is your second attempt to "upgrade" the road classification east of the US 50 - US 50 ALT convergence point to trunk. User btwhite92, who is a prominent editor in Northern Nevada as well as a longtime area resident addressed another user who had previously upgraded this route to trunk with the following changeset comment "US 50 east of US 50 Alt junction is not built to expressway standards - undivided, increasingly lower speeds, direct access to countless properties, [the] highway west of this intersection meets requirements for 'trunk'." I agree with btwhite92, having traveled this stretch of road hundreds of times in my life. While a highway may possess a certain lane capacity or even have a similar speed limit, that doesn't mean that it warrants a "trunk" classification. You will notice that the route west of where you edited has physical concrete barriers dividing travel directions. Additionally, there are clear barriers that divide links from through traffic that have pre-determined routes which you must use to exit and/or enter the highway. This route you changed, leaving Fallon until it reaches US 50 ALT, does not have concrete barriers, nor does it have divided links. Yes, it has 4 travel lanes with a center turn lane. It is, however, that center turn lane that gives the motorist the ability to exit the highway wherever they choose which is not an attribute of a properly classified "trunk" road.

I appreciate your enthusiam to edit in Northern Nevada. That said, one of the best things you can do is study the OSM Carto Map to get a feel for how each state is mapped. Each community interprets and implements the overall OSM guidelines differently. Local editors who have lived, worked, gone to school, driven the roads, and been to these cities and small towns are going to know a lot and be an invaluable resource in helping you understand how we, the Nothern Nevada OSM community, edit and in this case, classify our roads.

Another good tip is to stick to areas you are personally familiar with. I edit almost exclusively in my hometown and in my home county because I am intimatley familiar with everything about it. I map other places that I have visited and/or lived for a short while because I actively try to become familiar with them which in turn allows me to make accurate and correct edits within OpenStreetMap.

I think this bug might be the cause. I read the big report and I’ve noticed some of what was in the report lately.

You’re absolutely correct. That changeset comment was actually intended for another changeset and I got thrown off when I submitted the changeset. This particular changeset was only some realignment work. Thanks again!

Thanks for reaching out. Lamoille Hwy does not meet expressway standards (i.e. Trunk or higher). US tagging guidelines specify primary for roads linking urban clusters of > 10,000 population (Elko: 20,467; Spring Creek: 12,361). This is the main reason for tagging the highway as primary. I would be more inclined to tag this road as trunk if it was divided with a cement barrier or berm in the middle. The highway itself is 5 lanes (2 each direction, 1 center turn lane) with a max speed of 55mph which does not classify it as an expressway.

In Nevada, we don’t have a lot of corridors that would classify as “trunk” outside of the major urban areas of Reno-Sparks and Las Vegas. However, a great example of a trunk road in Nevada is US 50 connecting Dayton to Silver Springs. That corridor embodies all of the traits of an appropriately tagged trunk highway as it is divided, has limited access, and a max speed of 65 mph.

I hope this helps.

The imagery is great! I'm happy to finally see a long-er stretch of motorway along Bangerter. It's been a long time in the making. Hopefully funding will be indentified for MVC sooner rather than later.

Hey, good to know. Thanks for making that correction. I'll come back in when they finish that up this summer and make the change to motorway.

Lamoille Hwy does not meet expressway standards (i.e. Trunk or higher). US tagging guidelines specify primary for roads linking urban clusters of > 10,000 population (Elko: 20,467; Spring Creek: 12,361). Please consult the OSM wiki to learn more about road classifications and how they differ between states and editing communities.
Additionally, as someone who has been local to the area. I have it on very good authority exactly how this highway is constructed, its speed, median width, and the amount of daily traffic it sees. Please consult all available data sources (including local editors and statewide tagging guidelines before making major changes).
Thanks.
---

Published using OSMCha: https://osmcha.org/changesets/101153019

Hello,
My apologies. When I did this, I was still very new to OSM and editing in ID with no concept of boundary relations.
I don't remember seeing an error message during the upload. I imagine there probably was one but I most likely didn't know what it was.

Fixed.

Hey,
I really appreciate the rapid response and your candid thoughts. I see where your coming from. I'm familiar with the points you've presented and have on occasion used those same positions in other discussions. In my mind, it does make a little more sense as a primary with classification considerations I account for each day in my professional line of work but I may leave it for now and think about it for a few days. Thanks for your thoughts! Much appreciation!

Hi,
I was reviewing some edits in the Provo-Orem area and came across this classification change on University Ave (US 189) and 800 N (UT 52) from primary to trunk. I wanted some context behind your change and your reasoning for making the change. I am local to the area and drive this road multiple times daily.
I work in OSM professionally and reviewed the wiki on highway=primary and highway=trunk. In the wiki entry for highway=trunk, it states "Use highway=trunk for high performance or high importance roads that don't meet the requirement for motorway." This stretch of road from its interchange with Interstate 15 to the mouth of Provo Canyon is not a high performance road and has no fewer than 25 signal controlled intersections. It is, in reality, a very slow moving road due to high traffic volumes and the amount of signal controlled intersections. According to UDOT, it is classified as a major arterial and generally, these types of highways do not take on a classification higher than primary.
The same is true of 800 North in Orem. All of the above is true with the exception of it having less signal controlled intersections between the mouth of the canyon and Interstate 15.
Like I said before, I'd just like to get your take on things before I go making any changes.
- TheConductor

Good morning,

As I was reviewing edits in my home county, I came across this change. First, thank you for your contributions to the area. I, like you, take great pride in my home and want to make sure that it is modeled as accurately as possible. I took the opportunity to read your bio and you mentioned that you hand model everything. I find that to be an admirable quality in the OSM community. Most, if not all streams and rivers that you encountered in this area were hand modeled by myself over countless hours ensuring painstaking accuracy.

I did this not only for my personal satisfaction but for the benefit of multiple organizations that rely on this data which brings me to my next point. After conferring with contacts from the Nevada Department of Conservation and Natural Resources, the BLM's Winnemucca Field Office, and the Nevada Department of Wildlife, the unanimous conclusion is that the classification of the "Little Humboldt River" is indeed a river. Admittedly, it does not always carry water but when it does, it maintains stream gauge levels appropriate with surrounding rivers. Many of these individuals have been observing and recording this data for much of their careers. As such, I will changing the classification back to "river" but with an "intermittent" tag on it as well.

Thank you for your time. Best regards.

Thanks for reaching out. If you’d like to rip into this and fix it all up, please do. I worked this section of road before I really knew what I was doing in OSM. Now that I have a full-time job with OSM, I haven’t been able to go back and fix previous mistakes as I spend most of my time editing in my work account. Let me know if you have any questions. I’d be happy to provide insight.

I agree that we're more or less on the same page. I think you have made a valid point referring to the difference between name that is used by locals (US-95 - Veterans Memorial Highway - a working address used by many local businesses) and a designation such as I-80 as Dwight D. Eisenhower Highway. I am very familiar with the "whats on the ground" rule within OSM. I work full-time in editing in OSM using ground footage from Mapillary and as such, it is important that we verify on the ground before we input into the system. I also recognize that this may have been a hasty error on my part to act before looking at all the angles. I appreciate you bringing this to my attention. I will, however, scrutinize more closely the signage along Interstate 80 the next time I am traveling to California or Utah just to 100% sure that no such signage exists. For now, I think creating a relation to keep the name will be the best course of action moving forward.

I appreciate your candidness and willingness to be thorough. I look forward to working alongside you in the future.

Warm regards :)

You make a great point and no, I have never referred anybody to take the "Dwight D. Eisenhower Highway" west to California. Having driven the entire breadth of Interstate 80 from border to border many times, I am not aware of a sign that specifically states the fact we are debating. There is a rest stop between Fernley and Sparks that has a commemorative sign that speaks to the links I provided above. I have been to the rest stop and can confirm the signs existence. I will provide a link below to an image of the sign that somebody else took.

What I am aware of is that locals are more or less aware of the designations given to highways both federal and state throughout Nevada. Recently, the state passed legislation designating the stretch of I-11 as a Purple Heart Highway and US 95 is known as Veterans Memorial Highway. Additionally, there is a Martin Luther King Jr. designation for US 395 through Reno, it is signed yet no one that I know of refers to it as the Martin Luther King Jr. highway, just US 395 or 395. I understand these are token designations and are not necessarily the name we refer to them by but they are part of the naming convention of the highway nonetheless.

Another good indicator for myself is that if the state (in this case Nevada) feels it is important enough and appropriate enough to put these names onto an official state map, they must carry some weight in terms of designation or name for that particular stretch of highway. The name Dwight D. Eisenhower freeway might not be as widely used as something like the Capital Beltway. The only perceptible difference being a much larger population that needs to have designations between the multitude of highways that criss-cross the DC metro area thus why the name probably stuck. Here in rural Nevada, we have one interstate and no need to use its name to define it when I 80 will suffice.

However, if you feel that the name would be better placed in a relation as opposed to directly on the way, I will defer to that preference. I hope I have explained myself appropriately.

Warm regards :)

https://www.flickr.com/photos/kenlund/17462364323
osm.wiki/United_States_roads_tagging

Hello chachafish,

The removal of the name Dwight D. Eisenhower Highway is incorrect. In 1973, Congress passed legislation that designated a cross-country stretch of interstate highway as the Dwight D. Eisenhower Highway. The following stretches of highway have received that designation: I-270 between the Capital Beltway and I-70 in Frederick, Maryland, I-70 to I-25 in Denver, I-25 to I-80 at Cheyenne, Wyoming, and I-80 to San Francisco. Here are the following links for your information.
https://www.fhwa.dot.gov/infrastructure/ddehwy.cfm
https://www.govinfo.gov/content/pkg/STATUTE-87/pdf/STATUTE-87-Pg250.pdf#page=4
https://www.nevadadot.com/home/showdocument?id=6475

Thank you for your time and understanding,

DRM12

When there’s time. It’s a very, very casual hobby. Thank you for the pro tip. @Bytemark