mNo edit summary |
mNo edit summary |
||
| Line 15: | Line 15: | ||
[http://wisconsindot.gov/rdwy/fdm/fd-11-25.pdf|(a)][http://wisconsindot.gov/rdwy/fdm/fd-11-25-att.pdf#fd11-25a5.3|(b)] | [http://wisconsindot.gov/rdwy/fdm/fd-11-25.pdf|(a)][http://wisconsindot.gov/rdwy/fdm/fd-11-25-att.pdf#fd11-25a5.3|(b)] | ||
[http://wisconsindot.gov/rdwy/fdm/fd-11-25.pdf 1][http://wisconsindot.gov/rdwy/fdm/fd-11-25-att.pdf#fd11-25a5.3 2] | |||
Revision as of 20:34, 13 June 2018
Function Classification Continuity
There are instances when the Waze road typ may need to be upgraded to preserve functional classification continuity. This happens
You're doing the routing engine a favor by interpreting what the intended flow of traffic is, as in "this PS is clearly designed to be the primary route between the limited access road and the mH/MH," this meaning you can justify the upgrade the PS to match the mH/MH