I’m jumping in here a little late, but the use of preferred routing for Texas frontage roads verbiage should be included somewhere in either the SCR, Texas, or frontage road Wiki. I included the frontage road Wiki because Texas isn’t the only state that uses frontage roads.
I think they should be locked at 4, as they can’t be touched by editors R3 and below regardless. In some areas of the country, this might be the only thing locked at R4
I’m not sure I have heard the term “connecting road” in this context. Are you talking about a situation when two different route numbers meet and share a common roadway for some distance and then split apart again? If true, I assume you are defining the combination of road type and preferred or unpreferred routing to use under the different combinations.
My understanding is that Freeway and MH are classed the same relative to pruning. So this would be for all other combinations when sharing the same segments.
I think we want to word this in a way that relates to visual examples. I’m not directly familiar with this portion of pruning and routing and I’m not sure I follow the above instructions enough to reword it myself. But if someone supplied pictures I could reword it.
However, because of pruning of Mountain Blvd (as our destination is that far up the mountain), Waze would not route through Keller, despite the exit being signed for Keller. So, our connecting road here is Mountain Blvd, connecting an exit signed to Keller, and Keller Ave itself. Our old practice was to increase the road type of Mountain Blvd there to mH, the lower type of F and mH. Now, we can simply set Mountain Blvd to preferred.
Scenario 1b:
Using the same area, we’re going to now head to Oakland after going to the mountain. The logical ramp would be to go down Keller, and take the corresponding on-ramp. Again it is signed from Keller that going down 1 segment on Mountain Blvd will lead you to the on-ramp. This segment of Mountain will need to be set as preferred, to connect Keller with the on-ramp.
If Mountain Blvd is a street, then the two connecting segments need to have their road type increased, as well as set with a Preferred routing. i.e., in the client, it is the most visually minimal way to get the route to work
My recollection is that there is a little bit of difference at the extreme lengths of routing. However, the more important question is if setting to “Preferred” on MH will trigger “Avoid freeways” option.
If someone could just double check a detail I haven’t seen yet: Does the R4 “virtual lock” come in to play when a routing type is LOWERED, as well? I’d imagine it does, but just haven’t seen confirmation.
I can confirm that the “virtual lock” comes in to play when LOWERED also. I just tried this and got the saving error when attempting to split a segment that had its routing type lowered.
The other day, I ran across an old school upgrade of PS to MH for a connecting road from a MH to a FW. It was over a mile long. I think there needs to be some standardization on how far people are allowed to do this w/o going and getting the SMs/RCs involved.
Not sure if it is appropriate for the Wazeopedia page (or for me to be doing it) but I typically set the routing to “unchanged” when unlocking frontage roads for lower level editors. When I lock it back up, I set it back to +1.(or -1)
Just to add my two cents also, I tested this a while back and found that with routing type +1 or -1, any lower level editor can still edit the segment (geometry, name, SL, etc) they just can’t change the road type or do anything that would cause the segment ID to change (split the segment).
