(Revised order of where to look for FC based on forum discussion.) |
(Added Texas/Detroit Style feeder road FC information) |
||
Line 3: | Line 3: | ||
Service Roads and Frontage Roads are often used interchangeably by Waze Users. Dictionaries even state that the quick definition of one is the other. A more formal definition is along the lines of a road that is parallel or near to a more significant road and that allows people to access local businesses and/or houses. | Service Roads and Frontage Roads are often used interchangeably by Waze Users. Dictionaries even state that the quick definition of one is the other. A more formal definition is along the lines of a road that is parallel or near to a more significant road and that allows people to access local businesses and/or houses. | ||
===Functional classification for service/frontage roads=== | |||
Please make sure that the Service Roads/Frontage Roads are set to the correct Functional Classification (FC) level. General USA guidance is found at [[National resources/USA/Functional classification|Functional Classification]]. There are several items to consider in the following order: | Please make sure that the Service Roads/Frontage Roads are set to the correct Functional Classification (FC) level. General USA guidance is found at [[National resources/USA/Functional classification|Functional Classification]]. There are several items to consider in the following order: | ||
# Regional or State guidance, if applicable, will be listed on their respective Wazeopedia page. | # Regional or State guidance, if applicable, will be listed on their respective Wazeopedia page. | ||
#:a. This includes when the service/frontage road is a "feeder road" and continuity of the road is required. [[Road_types/USA#Exceptions|FC Exceptions]] explains how Texas or Detroit style feeder roads should be handled. | |||
# Functional Classification map(s) from the local authorities (Department of Transportation, State Highway Administration, etc.) are preferred. [Often found on State wazeopedia pages.] Utilize this guidance in conjunction with [[National resources/USA/Functional classification|Functional Classification]] tables. | # Functional Classification map(s) from the local authorities (Department of Transportation, State Highway Administration, etc.) are preferred. [Often found on State wazeopedia pages.] Utilize this guidance in conjunction with [[National resources/USA/Functional classification|Functional Classification]] tables. | ||
# If the Service Road/Frontage Road services a Freeway or Expressway, then follow the guidance for Frontage Roads for Freeways/Expressways found at the Road types/USA/Primary Street that discusses [[Road_types/USA#Primary_Street|Frontage Road]]. | # If the Service Road/Frontage Road services a Freeway or Expressway, then follow the guidance for Frontage Roads for Freeways/Expressways found at the Road types/USA/Primary Street that discusses [[Road_types/USA#Primary_Street|Frontage Road]]. |
Revision as of 21:17, 1 March 2017
Service roads or frontage roads
Service Roads and Frontage Roads are often used interchangeably by Waze Users. Dictionaries even state that the quick definition of one is the other. A more formal definition is along the lines of a road that is parallel or near to a more significant road and that allows people to access local businesses and/or houses.
Functional classification for service/frontage roads
Please make sure that the Service Roads/Frontage Roads are set to the correct Functional Classification (FC) level. General USA guidance is found at Functional Classification. There are several items to consider in the following order:
- Regional or State guidance, if applicable, will be listed on their respective Wazeopedia page.
- a. This includes when the service/frontage road is a "feeder road" and continuity of the road is required. FC Exceptions explains how Texas or Detroit style feeder roads should be handled.
- Functional Classification map(s) from the local authorities (Department of Transportation, State Highway Administration, etc.) are preferred. [Often found on State wazeopedia pages.] Utilize this guidance in conjunction with Functional Classification tables.
- If the Service Road/Frontage Road services a Freeway or Expressway, then follow the guidance for Frontage Roads for Freeways/Expressways found at the Road types/USA/Primary Street that discusses Frontage Road.
- If none of the above items apply, then consult with your State Manager(s) to determine between PS or Street type based on usage density.
Problems
Service and Frontage Roads often cause routing problems. Some of the more frequent routing problems are:
- Routing off the main road to the service road, and then back onto the main road.
- Being navigated to the main road for an address which is on the service road. The address may not be reachable from the main road, especially if there is a barrier between the roads. Additionally stopping may be dangerous or prohibited on the main road.
- The address is not found in search since it is listed on the service road, but it should use the main road's address. This causes the search to use 3rd party results even if there is a confirmed HN in Waze, leading to routing issues.
- Drivers unknowingly taking the main road instead of the recommended service road, and then being unable to make a recommended turn further down since they are on the main road instead of the service road. This results in Turn Not Allowed, Incorrect Junction, or Wrong Driving Directions URs.
Here is an example at Arlington Blvd in Northern Virginia. Reporter was unable to make the turn from Arlington Blvd to N Montague St because they did not follow the recommended route. The recommended route was the PL above. [Note: Editors need to make sure that the service road is labeled service road. Sometimes they are found labeled the same as the main road and Users don't understand to go to the service road. Users who turned on the main road and won't be able to make the subsequent turn.]
Solutions
Naming service/frontage roads
- To prevent routing detours and to ensure we trigger Big Detour Prevention,
- a. Keep the service road separated from the main road at all points by at least one segment.
- b. The segment separating the main road from the service road DOES NOT have the main road name as either the primary or alternate name. This can be achieved by having an unnamed segment or the name of an intersecting road.
- c. Check for any Bowties, or forks, where the main road connects directly to service road, a feeder road connects directly to both the main and service roads, or a slip road (entrance or exit) connecting between the service and main roads and eliminate any Best Continuation issues.
- d. In most cases these are best left as no-name segments.
- When adjusting for BDP also keep an eye out for any unintended Best Continuation issues, which would prevent the user from being given a prompt advising which road to turn on to.
- Test the routing after the tiles are built.
- To allow address matching in search, and proper House Number routing, ensure that the main road name is added to all the service road segments as an alternate name.
House numbers on service/frontage roads
Nudging all the HNs a bit to move the anchor point to the service road vice the main road has 2 benefits:
- Confirm HNs to give them routing priority over 3rd party sources
- Confirm HNs to snap the stop point to the service road.
Don't forget to test the routing after the tiles are built
Discussion
This proposal is under discussion in the forums. To participate in the discussion click here