Kinematic wrote:Currently working on one for all Highways. Although it's going to take some time.. a very LONG time.

If you want some help, let us know where in the wiki to find it and the source you are using for the Montana routes inventory.

FYI, I have one for Oregon which is still in progress. Since I'm the RC, I'd like something similar, but if yours is cooler, I may change my mind.

The number one thing besides fielding user reports and place update requests would be updating road types to ensure they're in line with the Functional Classification standards.

https://wiki.waze.com/wiki/Road_types/USA

There's a reference chart available on that page that's absolutely essential to determine whether or not a road might need upgrading.

Those types of changes can have a drastic impact on routes offered across the state.

Unfortunately the errant state names is something to get used to when doing basemap editing. There's numerous cases of this across the country. In areas I edit, Iowa segments pollute Nebraska, Montana in Wyoming and Kansas in Missouri. Add-ons are available to help you flag these instances.

One-way roads are also common in more remote areas where few Wazers have traveled.

On the plus side you'll be racking up experience and points in a hurry cleaning things up!

It's a dirty job, but someone's got to do it.

Right now I am working on Hardin, MT (speed limits, cleaning up streets). I am also cleaning up rural roads between Billings and Huntley.

Looks like you guys did good work in Hardin. I had to fix a few street names, add a few streets, etc. I cannot remember many turn issues.

Another TODO item would be elevation work given the newer "seagull" guidelines. Normalizing all elevation +/- levels for all interchanges, bringing railroads up from -5 to ground or the appropriate +/- if a bridge/tunnel, marking tunnels and bridges appropriately even when there's no other corssing road, etc.

In NE our progress cheatsheet is county-based with completion percentages for FC, elevations, SL. I do like your highway-based tracking since consistency end-to-end is very important. Do you have ideas for handing off the baton for a highway when someone has completed all the segments they have rights to? (that's one thing the NE county-based system handles reasonably well; it corresponds quite closely to editing rights).

Hardin was a mess when I started on it! Barely above basemap, one editor just flipped all the unknown direction roads to 2-way and left it at that. So yeah, it needs more love [WHITE SMILING FACE]️

Sent from my SM-N920V using Tapatalk

bretmcvey wrote:The number one thing besides fielding user reports and place update requests would be updating road types to ensure they're in line with the Functional Classification standards.
https://wiki.waze.com/wiki/Road_types/USA
There's a reference chart available on that page that's absolutely essential to determine whether or not a road might need upgrading.
Those types of changes can have a drastic impact on routes offered across the state.

That's a great idea bretmcvey. That wasn't on my mind at all as I was more focused on Highways because the majority are missing alternate names along with exits or are improperly named. I'll definitely start looking into that. Thanks

AlanofTheBerg wrote:If you want some help, let us know where in the wiki to find it and the source you are using for the Montana routes inventory.

FYI, I have one for Oregon which is still in progress. Since I'm the RC, I'd like something similar, but if yours is cooler, I may change my mind.

So I looked at yours and it's far better than mine. Looks like I'll be using your set up or until I can think of some highly sophisticated method.

PhoenixofMT wrote:I would add fixing direction and state on the more remote roads. It's pretty frustrating to add a road and not realize that the state has defaulted to Idaho because it comes before Montana alphabetically and a bunch of nearby roads were assigned the wrong state with the base map import back in 2009.

The minor inconveniences editing get soo annoying.