Moderator: USA Champs
kentsmith9 wrote:A Style Guide can still easily exist as a collection of subpages. In true Wiki format, pages should really be less than 5 screens of data and some people say 2 or less.
dbraughlr wrote:Is there any chance that Waze would give us a "connector" road type that is the street equivalent of a highway ramp?
Service road could be converted for this use.
CBenson wrote:qwaletee wrote:There's already code to treat unnamed ramps as if they were named with the same name as the next named segment on the route.
This isn't a ramp property. This is true of any segment, isn't it?
daknife wrote:Ahh, I took it as otherwise, I think I interpreted it s saying, "well here it is a MH, that is the difference." In retrospect, I guess I was expecting to be put in my place and was looking (at least subconciously) for an argument, rather than agreement. Anyway, no biggie, I see what you meant now and good point on road type variations (at least within the Hwy types) should not disrupt routing if the name/number is consistent. But with 89 it does tend to lose continuity at each town, as it briefly takes on a local name (Main, or State street in nearly every town in Utah it runs through, sometimes only for a few blocks, but also through the length of the major population area of the State, where it is State St through Salt Lake county and city).
Tonight I made 89T all MH, the scenic alt should in my opinion remain a minor as do US BUS alternates.
Tapatalking via my Galaxy S4
banished wrote:Implications for this discussion...?
https://www.waze.com/forum/viewtopic.ph ... 49#p746349