User:Sub5/HNs on Service Roads View history

Latest revision as of 21:43, 10 May 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.

Please make sure that the Service Roads/Frontage Roads are set to the correct Functional Classification (FC) level. There are several items to consider:

General USA guidance is found at Functional Classification
Functional Classification map(s) from the local authorities (Department of Transportation, State Highway Administration, etc.) are preferred. [Often found on State wazeopedia pages.]
Regional or State guidance, if applicable, will be listed on their respective Wazeopedia page.
If the Service Road/Frontage Road is not listed in the FC map and there is no Regional/State guidance, then follow the guidance for Frontage Roads for Freeways/Expressways found at Frontage Road.
If above items do not provide the appropriate guidance, then set the Road Type to be a Street.

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 rd. The address may not be reachable from the main rd, especially if there is a barrier between the roads. Additionally stopping may be dangerous or prohibited on the main rd.
The address is not found in search since it is listed on the service road, but it should use the main street'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 rd, and then being unable to make a recommended turn further down since they are on the main rd instead of the service rd. 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 rd at all points by at least one segment.

b. The service road does not have the main rd 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

Procedure to put house numbers on service/frontage roads

Starting with HNs on the [Main St]

Temporarily name the service road with the [Main St] as the primary road name. (No Service Rd in the primary name)
Save the road name change
Edit HNs by moving each applicable HN from the real Main St to the Service Road

Moving 4723 2nd from top right

Save the HNs
Change the Service Road's primary name to "[Main St] Service Rd"
Add an alternate name of "[Main St]" to the Service Rd
Save the road name change

@@ Line 1: / Line 1: @@
-== Service Roads or Frontage Roads ==
+== Service roads or frontage roads ==
-Service and Frontage Roads often cause routing problems.  Some of the more frequent ones are:
+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.
-#  Routing off the main road to the service road and then back onto the main road.
+Please make sure that the Service Roads/Frontage Roads are set to the correct Functional Classification (FC) level.   There are several items to consider:
-#  Unable to get to the address since it is on the service road and there is a barrier from the main road.
+# General USA guidance is found at [[National resources/Functional classification|Functional Classification]]
-#  The address is not found in search since it is listed on the service road, but it should use the main street's address.
+# Functional Classification map(s) from the local authorities (Department of Transportation, State Highway Administration, etc.) are preferred. [Often found on State wazeopedia pages.]
-#  [https://www.waze.com/editor/?env=usa&lon=-77.13444&lat=38.86644&zoom=6&mode=0&Filter=0&segments=504886632,52714725,52709947,52709794&b=0 Arlington Blvd Route]Turn not allowed, unable to make the turn from Arlington Blvd to N Montague St.  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 (Arlington Blvd in this case) 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.]
+# Regional or State guidance, if applicable, will be listed on their respective Wazeopedia page.
+# If the Service Road/Frontage Road is not listed in the FC map '''and''' there is no Regional/State guidance, then follow the guidance for Frontage Roads for Freeways/Expressways found at [[Road types#Primary_Street|Frontage Road]].
+# If above items do not provide the appropriate guidance, then set the Road Type to be a Street.
+== 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 rd.  The address may not be reachable from the main rd, especially if there is a barrier between the roads.  Additionally stopping may be dangerous or prohibited on the main rd.
+# The address is not found in search since it is listed on the service road, but it should use the main street'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 rd, and then being unable to make a recommended turn further down since they are on the main rd instead of the service rd. This results in Turn Not Allowed, Incorrect Junction, or Wrong Driving Directions URs.
+Here is an example at [https://www.waze.com/editor/?env=usa&lon=-77.13444&lat=38.86644&zoom=6&mode=0&Filter=0&segments=504886632,52714725,52709947,52709794&b=0 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.]
+[[File:Did Not Take Service Rd.PNG|thumb|center]]
 == Solutions ==
-===Naming Service/Frontage Roads===
+===Naming service/frontage roads===
-'''Details on how to do the names and HNs'''
-# To prevent routing errors from Big Detour Prevention make sure that you have at least one segment that does not have the "Main Road" name as either primary or alternate name.  This can be done by having an unnamed segment or the name of an intersection road.
+# To prevent routing detours and to ensure we trigger [[Detour_Prevention_Mechanisms|Big Detour Prevention]],
-# Check for any Bowties, or forks where the main road connects directly to service road, or a feeder road connects directly to both the main and service roads, and eliminate any Best Continuation issues.
+#:a. Keep the service road separated from the main rd at all points by at least one segment.
-# Check and adjust if necessary any slip roads (entrance or exit), in most cases these are best left as no-name segments.
+#:b.  The service road does not have the main rd 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 [[Junction_Style_Guide/Intersections#Bow_tie |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 | 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
-===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:
-# It confirms them given them routing priority over 3rd party sources
-# It snaps the HN stop point to the service road.
-# Check for any Bowties, or forks where the main road connects directly to service road, or a feeder road connects directly to both the main and service roads, and eliminate any Best Continuation issues.
-# Check and adjust if necessary any slip roads, in most cases these are best left as no-name segments.
-# Test the routing after the tiles are built.
-"Procedure to Move House Numbers from Main Road to Service Road"
+'''Procedure to put house numbers on service/frontage roads'''
 * Starting with HNs on the [Main St]  [[File:HNs_on_Main_Street_vice_Service_Rd2.PNG|thumb|center]]
@@ Line 32: / Line 47: @@
 * Save the road name change
 * Edit HNs by moving each applicable HN from the real Main St to the Service Road
-[[File:Select_HN_from_Main_St.PNG|thumb|left]]  Moving 4723 2nd from top right [[File:Move_HN_to_the_Service_Rd_(that_has_Main_St_name_temporarily).PNG|thumb|right]]
+[[File:Select_HN_from_Main_St2.PNG|thumb|left]]  Moving 4723 2nd from top right [[File:Move_HN_to_the_Service_Rd2_(that_has_Main_St_name_temporarily).PNG|thumb|center]]

Search