View source for User:DBsooner/SCR/Roads in SCR View history

== Roads in the South Central Region ==

=== Interstates in the region ===
Arkansas / Louisiana / Mississippi / Oklahoma / [[Texas#Interstates in Texas|Texas]]
<br />
=== Road naming ===
Use the following designations when creating or editing numbered roads in the South Central Region.
{| class="wikitable"
!
!AR
!LA
!MS
!OK
!TX
|-
|Interstates
|I-XX
|I-XX
|I-XX
|I-XX
|I-XX
|-
|US Highway
|US-XX
|US-XX
|US-XX
|US-XX
|US-XX
|-
|State Highway
|AR-XX
|LA-XX
|MS-XXX
|SH-XX
|SH-XX
|-
|State Loop
|AR-XX LOOP
|
|
|SH-XX LOOP
|Loop XX
|-
|State Spur
|AR-XX SPUR
|LA-XX SPUR
|
|SH-XX SPUR
|Spur XX
|-
|State Park Road
|
|
|
|
|Park Rd XX
|-
|State Rec Road
|
|
|
|
|Recreational Rd XX
|-
|County Road
|CR-XXX
|Parish Rd XX
|CR-XXX
|[[Oklahoma/Counties|Varies by Cnty]]
|CR-XX
|-
|Farm/Ranch to Market
|
|
|
|
|FM XX/RM XX
|-
|Private Road
|
|
|
|
|Private Rd XX
|}

'''Business Roads'''
All business roads should be suffixed with BUS:
* Business Interstate = I-XX BUS
* Business US Highway = US-XX BUS
<br />

=== Other road names ===
The South Central Region conforms to the USA Standards for TTS abbreviations for prefixes and suffixes. Please see the [[Abbreviations and acronyms|Road Naming Abbreviations & Suffixes]] page for more details.
<br /><br />
=== Non-drivable roads ===

Generally, if a road can't be driven on (e.g. Walking Trail, Pedestrian Boardwalk, Stairway, Ranch road in the middle of nowhere), then it should not be mapped in the South Central Region. We have chosen to implement this guideline because due to the way the routing engine works, Waze '''WILL''' route users to drive on these "Non-Drivable" road types.

'''[[Railroads|Railroads]]''' mapped in the South Central Region should follow the current standard of editing. All crossings should be connected to drivable segments accordingly.  If no crossing exists, elevate the segment accordingly.

'''ONLY enter a name for the railroad segment if the tracks are historical in nature, a major landmark, or a routine destination for Wazers. In the SCR, very few segments should be named and most 'routine destinations' will be covered by a Place point/area for the train station.'''

The Waze app now renders railroad tracks as such so naming serves little purpose any longer.
<br /><br />
=== Special roads ===

*[[Best map editing practice#When to Split a Two-Way Road (and when not to)|When not to divide a two-way road]]
*[[Best map editing practice|Divided Roads]]
*[[Carpool, HOV, Transit lanes|Carpool, HOV, Transit lanes]]
*[[Creating and Editing a roundabout|Roundabouts and Traffic Circles]]
*[[Creating_and_Editing_street_segments#Fix_the_end-node_on_culs-de-sac_and_dead-ends|Cul-de-sacs]]
*[[Road types#Dirt|Dirt Roads]]. In the South Central Region '''ALL''' roads that are unpaved or gravel are considered dirt roads as this is how GPS Nav users (any brand) expect the "Avoid Dirt Roads" feature to behave.  These roads should be deleted when going through farm land, ranch land, or mountainous areas throughout the state, as they are most likely base import roads and not real roads. For roads which are labeled with names and are actually dirt on SATIMG, please keep these and make them dirt roads. To do so, select the {{Street|Local Street}} or {{Private Road}} type (as appropriate), then check the Unpaved box.
*[[Road types#Parking Lot Road|Parking Lot Roads]].  Map parking lot roads (PLRs) that will allow proper navigation in to and out of a parking lot. A primary routing purpose for PLRs is to connect a parking lot that has entrances along two or more different named roads, to enable shorter / faster routing to a destination. The SCR standard for PLRs is to enable U-turns at the ends of each PLR segment. In the Waze app, U-turn-enabled PLR segments will support drivers that need to double-back on a segment.  This will allow Waze to quickly route drivers who need to exit any parking lot the same way that they came in.  This SCR guidance is true for gas stations, strip malls, shopping areas, and other PLAs where a PLR is appropriate. Remember that a parking lot area (PLA) does not substitute roads needed for actual navigation. While it is important to map appropriate PLRs, please follow guidance and do not add PLRs which are not necessary.   
*[[Best map editing practice#Toll roads|Toll Roads]]. Only segments that actually contain a toll gantry should be marked as Toll.
*[http://en.wikipedia.org/wiki/Frontage_road Frontage roads]. Name as "Frontage Rd" unless the corresponding highway has an alternate name. I-635 Frontage roads are labeled as "Lyndon B Johnson Freeway" as that is the local name for I-635. 
*Alleys and driveways are generally '''not mapped''' unless they are required for navigation. See [[Driveways]] for more information.
*Any road which is a main road for a state park can be a {{Primary Street}}. Other roads can be {{Street|Local Street}}.
<br /><br />

=== Turnarounds and Median U-Turn Segments (MUTIs) ===
'''Turnarounds '''Turnarounds (those labeled as Turnaround, not crossovers), should be classed as {{Street|Local Street}}.

'''Median U turn segments (Louisiana) '''Dedicated median U-turn segments in the New Orleans metropolitan area (at least) should be unnamed.

A turn instruction override should be used such that a "U-turn" instruction is given when entering the U-turn segment.

For curved segments, the geometry of the segment should be set such that no instruction is given when ''leaving'' the U-turn onto the road. For straight segments, a turn instruction override may be used as well, set to "None".
<br /><br />

=== Segment and turn restrictions ===
Information about setting [[Partial restrictions|partial restrictions on time or vehicle type on roads]].

Information about [[soft and hard turns|soft and hard turns, turn restrictions, and time-based turn restrictions]].
<br /><br />
=== Functional Classification of Roads ===

The South Central Region participates in functional classification across all states. We promote a hybrid FC to ensure for the best routing possible for all Wazers.  The hybrid FC basically means a state highway would never be typed less than Minor Highway (mH). See [[Road types]] and [[Road names]] to learn more about various road types and how functional classification applies.

'''Frontage roads'''

All frontage roads running along freeways and major highways should be set to {{Minor Highway}}. 

In cases where a Wazer would go from {{Freeway|Fwy}}  > {{Ramp}} > Frontage Rd > {{Major Highway|Major}}, the Frontage Rd would be set as {{Minor Highway|Minor}} with the Routing Type changed to <code>One type higher</code> or <code>Preferred</code>.  This moves that section of road up in classification within the routing server but for appearance purposes, it keeps it as a {{Minor Highway|Minor}}. Frontage road that dead ends should be set as {{Street|Local Street}}.  Small sections of Frontage Rd which just run parallel to a freeway and provide no entrance/exit to/from the freeway will match FC or be no higher than {{Primary Street|PS}}.
Only those rank 4 or higher can set the Preferred/One type higher routing flag. Once this flag is set, certain edits on the segment will be limited to those R4 and higher.

'''Turnarounds'''

Turnarounds (those labeled as Turnaround, not crossovers), should be classed as {{Street|Local Street}}.
<br /><br />
==== Functional Classification by State ====
Use the appropriate link below to access the correct Waze Functional Cross Reference chart and state DOT Functional Classification map for the state you are working in. Once you have reviewed the map, refer to the FC cross reference chart below to determine what road type and lock level should be assigned to the roads in the area. For roads that need to be locked at a higher level than you are able, change the street to the correct type, then request a lock from a higher-level editor.

{| class="wikitable"
|-
! State
!WAZE FC X- Reference
! State DOT FC Map
! Notes
|-
| {{anchor|Arkansas}}Arkansas
|
| [http://gis.arkansas.gov/arcgis/rest/services/FEATURESERVICES/Transportation/MapServer/8 AHTD FC Overlay for ArcGIS]
| The AR FC map is an overlay added to the base [http://www.arcgis.com/home/webmap/viewer.html?webmap=5709338946c54415ae30c63bfab923b4 ArcGIS] map. To use the overlay, click on the "Modify Map" in the upper right corner of ArcGIS. On the left side an "Add+" tab will pop up. Click on it and select "Add Layer from Web" and paste in the URL for the overlay provided by the link to the left. If you have never used ArcGIS before, you may be asked to create a Public Account.
|-
| {{anchor|Louisiana}}Louisiana
|
| [http://www.arcgis.com/home/webmap/viewer.html?webmap=8a893b672da94be793b83b4581ca877d&extent=-95.3652,28.8529,-88.6196,33.4989 LaDOTD Interactive Online Map]
| [http://wwwsp.dotd.la.gov/Inside_LaDOTD/Divisions/Multimodal/Data_Collection/Mapping/Pages/Statewide_Highway_Functional_Classification_Maps.aspx Static FC maps] are also available if desired.
|-
| {{anchor|Mississippi}}Mississippi
|
| [http://mdot.ms.gov/portal/planning.aspx?open=Maps MDOT]
| Click on Functional Class Maps to find the various FC maps available.
|-
| {{anchor|Oklahoma}}Oklahoma
|
| [http://okdot.maps.arcgis.com/apps/Viewer/index.html?appid=00907358f2934cf28c2121457df23d10 ODOT ArcGIS Map]
| Static maps available here: [http://www.okladot.state.ok.us/maps ODOT] Look in the middle of the page to find links for [http://www.okladot.state.ok.us/maps/rfc/index.htm Rural Functional Class maps] and [http://www.okladot.state.ok.us/maps/ufc/index.htm Urban Functional Class maps].
|-
| {{anchor|Texas}}Texas
|[[Texas#FC Cross Reference|TX FC Chart]]
| [http://www.txdot.gov/apps/statewide_mapping/StatewidePlanningMap.html TxDOT Statewide Planning Map]
|  Select Functional Classification & Urban Areas in the left menu to turn the FC overlap on.
|}
<br />

====FC issues on State Maps====
If you find any issues where FC changes unexpectedly such as in the image (the small section of green in between 2 red sections), please let the Regional Coordinator (RC) know exactly where this is located, so the appropriate DOT can be notified.
[[File:FC_issue.png|thumbnail|center]]
<br />
==== Road Lock Standards ====
In the South Central Region, we have a set minimum standard for locking roads based on segment type. Any road of a certain segment type must be locked at least to the rank (level) in the chart below. Roads may be locked higher for protection and special situations (areas with construction, tricky design, frequent mistakes, imaging inaccuracies, and the like), but should not be locked lower. If you find a road locked to a higher level than its minimum, please leave it locked no lower than that level when you have finished editing.

<center>

{| class="wikitable"
|-
! Segment Type
! Lock Level
|-  align="center"
| {{Freeway}}
| 5
|-  align="center"
| {{Ramp}}
| 4
|-  align="center"
| {{Major Highway}}
| 4
|-  align="center"
| {{Minor Highway}}
| 3
|-  align="center"
| {{Primary Street}}
| 2
|-  align="center"
| {{Street|Local Street}}
| Automatic (1)
|-  align="center"
| {{Railroad}}
| 2
|-  align="center"
| {{Ferry}}
| 5
|-  align="center"
| {{Private Road}}
| 2
|}
</center>
<br />

=== Speed Limits ===
Please familiarize yourself with the information on the [[Speed limits|Speed Limits Wazeopedia Page]].
<br />
==== {{@|Where speed limits change}} ====

Speed limits should change where they legally go in effect for your state, that may be at the sign, a specified distance before the sign, or the nearest intersection. When a speed limit changes in the middle of a segment, {{u|a new junction should be added to support the SL change}}.
* However '''a new junction should never be added for a SL if it will be within 200 feet of an existing junction''', or potential junction.
* A new junction should always be added if it will be more than 1,000 feet from the nearest existing or potential junction.
<br />
==== {{@|Creating a new junction for a speed limit change}} ====

When creating a new junction solely for the sake of showing a speed limit change, you can attempt to get more value from the junction. Survey the area around the speed limit change, determine if there is a PLR or other segment which should be connected to the road and would result in a junction. You may find that there's a parking lot which could benefit from being added to the map within the allowable distance of 200 feet (or more depending on your area) to where the SL changes. In such a case connect that segment and use that junction. Otherwise you should create a new junction to show where the SL changes.

On roads where traffic for one turn direction typically backs up waiting to make the turn further than 200 feet, and traffic going straight or turning the other direction does not have to wait as long to pass through, turn delays can be affected even with the new junction 200 feet away. In these cases you may choose to extend the buffer zone to beyond the point where traffic backs up, and instead make the change at an existing junction node. These situations are governed by editor discretion and local guidance.

{{expand|nt=yes|
It is very important that we do not create new junctions too close to existing intersections, yet marking the speed limit change too far can have a negative impact on the user experience.

The minimum distance of 200 feet was chosen because a distance less than that is negligible, and unnoticeable in the client experience. It is not much different than the delay we expect with GPS lag and error anyway. For example think of where you hear the turn prompts announced, they can sometimes precede a junction by up to 200 feet.

We have confirmed directly with the routing developers that adding a junction node connecting only 2 segments does not have an associated [[routing penalty]]. We have also confirmed that creating and adding new junction nodes where necessary using these above guidelines will not have a negative effect on route calculation.

However there is a legitimate concern when adding new junctions too close to existing intersections / interchanges, that they may interfere with and pollute the ability for Waze calculate accurate [[turn delays]].

The reason to use a minimum of 200 feet from the nearest junction as a buffer is to account for turn delay calculations.
If we create junction nodes very close to intersections we will effectively eliminate Waze's ability to differentiate the time it takes to go straight, vs the time to turn left or right. {{u|A distance of less than 200 feet between junctions poses a significant risk to the ETA calculations (turn delays).}} Over 200 feet it is up to local practice , and the editor's discretion to determine if a junction node there will negatively impact turn delay calculations. We must stipulate a minimum buffer zone, but it doesn't need to be exact. The area between 200-1,000 feet is open to interpretation, editor discretion, and local guidance.

If an exit or turn lane does back up over 1,000 feet, it is unlikely that traffic beyond the 1,000 mark will be drastically affected by the new junction placed that far away. ''However specific exceptions with the consultation of Regional Coordinators, or State Managers will always be allowed.''

: The turn delay issue could potentially be mitigated by adding [[User:CBenson/Junction_Box|Junction Boxes]] to each of these situations to correct them. However doing so would result in a lot more work for editors, and a lot more strain on the servers. It would make it harder to manage these intersections since all the included segments, and turns get locked from editing. It will have an effect on route calculation timing as well. We therefore had to come up with a compromise that is still visibly accurate, without anything being noticeably different to the client user, yet maintaining the ability for Waze to calculate proper ETA timing through intersections.
| the rationale behind these rules.}}
[[File:Mbox construction yellow.png|120px|right]][[File:Work zone SL.png|120px|right|Work Zone Speed Limit sign]]
==== {{@|Work zones}} ====
Speed limits in work zones are often lowered to protect workers and prevent collisions. If these speed limits appear on regulatory black and white signs, they '''MAY''' be added to the associated WME road segments. '''Speed limits should only be changed in work zones when the change will be in effect for at least 30 days.''' 
Add the construction zone speed limit to the affected segments and place a [CONSTRUCTION] note on the map listing the official speed limit so when construction is complete, an editor can easily reset the speed limit.
<br /><br /><br /><br /><br /><br /><br /><br /><br /><br />
=== True Elevation ===
The South Central Region practices the concept of True Elevation (TE) to better represent segments in relation to surroundings / ground level. In general, most segments should have an elevation of ''Ground'' unless they pass over another segment, waterway, or natural feature. '''Drivable and non-drivable segments are handled the same way with respect to elevation.'''

<font color="red">'''''NOTE: At this time, this is not a seek-and-destroy mission. Only fix true elevation as you encounter it.'''''</font>

True Elevation can help the user identify an elevated segment by shading the edges of the segment. Currently, not all elevated segments are configured to display this. At this time, true elevation only affects the look of the map in the LiveMap. However, it is anticipated this look will be incorporated into the app and other aspects of Waze. 

==== {{@|Definitions}} ====

* '''Bridge:''' A ''bridge'' is defined as a segment which is elevated ''above ground level'' by means of a man-made structure, typically to pass over another segment, waterway/body of water, or a ground-level natural feature. This does ''not'' include segments which are elevated above surrounding ground level solely by earthen construction.
* '''Tunnel:''' A ''tunnel'' is defined as a segment which passes below ground level (i.e., underground) by means of a man-made structure. This includes segments which pass under ground level segments via the use of a culvert or similar structure. This does ''not'' include segments which are below surrounding ground level but above ground (e.g., depressed freeways).

==== {{@|Examples}} ====

* [https://www.waze.com/en-US/editor/?env=usa&lon=-95.73154&lat=36.16328&zoom=5 Simple Interchange]
* [https://www.waze.com/en-US/editor/?env=usa&lon=-81.52165&lat=30.28692&zoom=7 More Complex Interchange (requiring junctioning of ramp segments to maintain ground elevation)] -- '''NEED REPLACED WITH SCR EXAMPLE'''
* [https://www.waze.com/en-US/editor/?env=usa&lon=-81.51658&lat=30.25273&zoom=5 Major Circular Interchange] -- '''NEED REPLACED WITH SCR EXAMPLE'''
* [https://www.waze.com/en-US/editor/?env=usa&lon=-80.32092&lat=25.78047&zoom=5 Complex Interchange] -- '''NEED REPLACED WITH SCR EXAMPLE'''
* [https://www.waze.com/en-US/editor/?env=usa&lon=-81.52201&lat=30.27881&zoom=5&segments=508539771,508539767,508539764,508539772 Raised Freeway (over preserve area)] -- '''NEED REPLACED WITH SCR EXAMPLE''' Louisiana Bayou??

==== {{@|Visuals}} ====
Below are two images showing the difference in Live Map rendering when True Elevation is not applied and when True Elevation is applied. Take note of the shading along the edge of the segment is missing when True Elevation is not used.

'''* * * * * * NOTE * * * * * These will be changed to SCR examples once I can actually upload to the wiki again. Further, I am waiting on a tile update for the example I have. :)
'''
{| class="wikitable"
![[File:SER_NoTE_Ex.png|400px|thumb]]
![[File:SER_TE_Ex.png|400px|thumb]]
|-
!'''Segment over water without True Elevation'''
!'''Segment over water with True Elevation'''
|}  

==== {{@|Implementation}} ====
* Elevation of overlapping segments should be set relative to each other, with the lowest segment as ''Ground'' except when the lowest segment is a tunnel.
* Only elevate / lower the actual bridge / tunnel section of the road.
* Bridges should be cut at the start / end of the bridge where the land falls away. You can typically see guardrail at the start / end of the bridge section, an expansion gap in the pavement where the bridge starts / ends, and/or a pavement change (asphalt to concrete, for example).
** '''Do not''' cut segments for elevation purposes if the bridge starts / stops within 60m / 200ft of an existing junction.
** Maintain some uniformity for display purposes when determining where to make the cuts.
** No need to elevate segments over every small creek or box culvert. A '''minimum''' bridge length of '''100ft''' is the rule in the SCR (unless the segment passes over another segment, then length does not matter).
* Only set elevation as low / high as necessary. For example, no segment should be elevation +2, unless it passes over another segment with elevation +1.
* Tunneled segments shall have lower elevation, relative to ground, and ''Tunnel'' should be checked.
* Only segments which are actually '''underground''' should have negative elevation.
* Tunnels should be cut at least 15m / 50ft before and after the tunnel, to allow time for the GPS to regain signal.
* '''The use of common sense is paramount in implementing True Elevation.'''

Note: If you have any questions, please speak with leadership for your area. Also, if you use the ''Bridge tool'' to join segments, be aware this will raise the elevation of the joined segment and you must lower the joined segment as appropriate.