Road Types (USA) – comprehensive overhaul of drivable roads

[nzahn1]

Is there a forum discussion on the implementation that's already going? There haven't been any posts here for a while. Thanks.

We are a little more piecemeal in the mid-atlantic: Here's the Maryland discussion.

[nzahn1]

I don't advocate putting any type of crossover on Interstate highways since it's never legal for any passenger vehicle to route on them, and they are bound to cause problems.

I would have agreed with you up until this post was made:

Can anyone speak to what policy exists for crossovers which are legal and useful?

I don't see an example of that being a legal or useful crossover. The Interstate Highway Act prohibits such crossovers, so I don't think the Yield sign makes it legal for the general public to use. That's a major hazard coming to a near stop in the left lane of an interstate to make a U-turn.

To me, this looks like a dirt road(s) making a connection with the interstate. You can see the Stop Sign for the dirt road facing the interstate from the desert on the North side. How legal this "interchange" is I have no idea.

[nzahn1]

i have my method, which was pulled straight from the wiki. It works fine.. but alas it dissapeared.

Not disappeared, just buried. And it still references 10-15° rather than the more appropriate 20-30°
Its in the Junction Style Guide Interchange Page

[PesachZ]

I would like to clear up some conusing statements in the Parking Lot Road and Private Road sections without changing the meaning at all.

https://wiki.waze.com/wiki/Road_types/U ... g_Lot_Road

* The proper use of parking lot roads can also help to avoid automated traffic jam reports as well as Map Problems related to Wazers driving in unmapped parking lots. Draw in the drivable portions of the parking lot that are near streets and other roadways. This will prevent the Waze routing server from assuming you must be on the main road when in fact you are stopped in the parking lot.

to

* Parking Lot Roads can be used to prevent Waze from assuming drivers driving slowly or parked in the parking lot are in a traffic jam in the main road -- draw in the drivable portions fo the parking lot that are near outside roadways.
* Waze will not highlight slow speeds (automatically detected traffic jams) on parking lot roads

And then, in the private road section:

As with Parking-Lot Roads, a route over a Private Road will incur a transition penalty upon leaving it for another road type. This transition penalty keeps Waze from routing Wazers through a private area as a shortcut. Unlike Parking-Lot Roads, however, Private Roads do not suppress automated traffic-jam detection.
As of August 2014 the Waze client displays Private Roads identically to public roads. Since this may change in future releases, never use the Private Road type for unrestricted public roads. Do not use the Private Road type as a workaround to force Waze to avoid slow public roads, for example those with rough patches or construction. In special cases, however, the Private Road type may be used for a public street that is legally and enforceably signed for local traffic only.

to

* Never use the Private Road type for unrestricted public roads
* Do not use the Private Road type to try to force waze to route around slow (damaged or under construction) public roads. Talk to a routing expert to find out if there are any good solutions.
* Private road may be used for a public street that has a legally enforceable sign for local traffic only.
* Waze handles private roads similarly to how it handles parking lot roads, but not exactly the same.
** Similarity: Waze routing adds a penalty to a route that goes from a private road segment to a segment of a different type.
** Difference: Waze will highlight traffic slowdowns on private roads.

The proposed PLR section omits mention of preventing missing road MP

Sent using Tapatalk for Android

[PesachZ]

True. there are 3 things mashed into that paragraph, not just 2.

How about

* Parking Lot Roads can be used to avoid "missing road" automated Map Problem reports.
* Parking Lot Roads can be used to prevent Waze from assuming drivers driving slowly or parked in the parking lot are in a traffic jam on the main road -- draw in the drivable portions of the parking lot that are near outside roadways.
* Waze will not highlight slow speeds (automatically detected traffic jams) on parking lot roads

Minor typos, but I support this

Sent using Tapatalk for Android

[PesachZ]

…

As with Parking Lot Roads , a route over a Private Road will incur a transition penalty upon leaving it for another road type.

…
We should also note that going from a parking lot road to another parking lot road or private road to private does not incur a penalty.

Isn't that already mentioned (emphasized above)?

Also that private road to parking lot road and vice versa may not incur a penalty as expected.

Why not?





Sent from Android using Tapatalk

[PesachZ]

…
[quote]As with Parking Lot Roads , a route over a Private Road will incur a transition penalty upon leaving it for another road type.

…
We should also note that going from a parking lot road to another parking lot road or private road to private does not incur a penalty.

Isn't that already mentioned (emphasized above)?[/u][/b]

to a new editor. no. its not emphasized above. I have had conversations with the entire SE group for hours about this topic.[/quote]
Can you please suggest a replacement text that would be clearer to a new editor.

Sent from Android using Tapatalk

[PesachZ]

[ img ]

Consider that as you travel across individual segments of the same type waze does not apply penalties.
In the example above the "correct" crossovers incur a penalty when crossing the divided road,
while the "incorrect" crossovers do not incur a penalty. The incorrect versions actually encourage the routing engine to route across the divided road into the other parking lot instead of immediately turning onto the divided road. Please keep this in mind when mapping these types of roadways to prevent bad routing.

A picture is worth 1000 words. Maybe visual examples would be best applied here.

i'm not sure we want to get too far into best mapping practices though.

This does not explain what you said earlier that private to plr or vice versa might not incur a penalty. The reason there is no penalty in these example is because the route doesn't exit to a different type

Sent from Android using Tapatalk

[PesachZ]

Consider that as you travel across individual segments of the same type waze does not apply penalties.
In the example above the "correct" crossovers incur a penalty when crossing the divided road,
while the "incorrect" crossovers do not incur a penalty. The incorrect versions actually encourage the routing engine to route across the divided road into the other parking lot instead of immediately turning onto the divided road. Please keep this in mind when mapping these types of roadways to prevent bad routing.

A picture is worth 1000 words. Maybe visual examples would be best applied here.

i'm not sure we want to get too far into best mapping practices though.

It doesn't even have to be a split road.

Agreed, I just thought the examples illustrate the issue clearly. PLR To PLR across a non penalized street type doesn't incur a penalty so it can and will cause major issues.

Perhaps you could also draw some companion correct and incorrect sample crossing a single two way segment (not-divided) road as well.

Sent from Android using Tapatalk

[PesachZ]

In the State Template thread we discussed preventing a circular reference between the template and the Dirt Road section. I think we can prevent the circular reference by changing the Dirt Road section to (changes in red):

In some areas of the country, improved unpaved roads (gravel, macadam, etc.) are set to this type. In other areas, improved unpaved roads, and possibly certain dirt roads, will be set to other types, as if they were paved. Check your state page for details on whether your state follows unique guidelines for dirt roads or contact your regional coordinator for further guidance.

Sounds good

Sent from Android using Tapatalk