User:Nhanway/TXFrontageRds View history

mNo edit summary
mNo edit summary
Line 1: Line 1:


{{mbox|type=notice|text=This new page is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. Content is being prepared by one or more users. Do not make any changes before you send a private message to nhanway. Please use the talk page for thoughts and ideas on setting up this content.}}
{{mbox|type=notice|text=This new page is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. Content is being prepared by one or more users. Do not make any changes before you send a private message to nhanway. Please use the talk page for thoughts and ideas on setting up this content.}}
{{mbox|type=notice|text=Last update 13 Dec 22}}
{{mbox|type=notice|text=Last update Dec 13, 2022}}
==Texas Specific Frontage Rd Guidance==
==Texas Frontage Rds==
DO NOT ADD SHIELD TO FRONTAGE RD


===Naming===
===Naming===
Important to remember that those using CarPlay or AndroidAuto segment name is very important as TIO and TTS does not work yet.
This is guidance for primary and alternate name(s) for [[wikipedia:Frontage_road|Frontage Roads]]. Important to remember that those using Apple CarPlay or AndroidAuto do not get editable [[usa:Turn_instruction#Visual_instructions|visual turn instruction]] therefor, choosing primary segment name is very important. We hope that in the future visual turn instruction will work in Apple CarPlay or AndroidAuto.  


====Primary:====
====Primary Name====
Primary name should match street signs or freeway name if present. Add “Frontage Rd” on endː
Primary name should match street signs and/or freeway name if present. We don't want the primary name of the frontage road to change at every intersection. Primary name should only change if the frontage road changes which road it parallels or the named freeway it parallels is no longer named. The primary name Frontage Road should always have {{nowrapcode|Frontage Rd}} on end. Also do not add Cardinal Directions unless they are 


* Lyndon B Johnson Fwy Frontage Rd
*Lyndon B Johnson Fwy Frontage Rd  
* N Highway 175 Frontage Rd
Parallels I-635 in Dallas County. Street signs for turns onto Lyndon B Johnson Fwy's Frontage road commonly say {{Nowrapcode|I-635 LBJ Fwy}} or {{Nowrapcode|LBJ Fwy}} or {{Nowrapcode|I-635 Lyndon B Johnson Fwy}}. It is common knowledge that {{Nowrapcode|LBJ}}= {{Nowrapcode|Lyndon B Johnson}} and so in Waze we spell in out so TTS will work.
* IH-10 Frontage Rd
* US-175 Frontage Rd
Parallels US-175 in Dallas County. Street signs for turns on to US-175 Frontage road commonly say {{Nowrapcode|N Highway 175}}. It is common in Texas for street signs to spell out US Highways so but we follow national guidelines for naming [[Road names#United%20States%20Numbered%20Highways|US Numbered Highways]].
*IH-10 Frontage Rd
Parallel I-10 in Harris County. <u>ADD GUIDEANCE are we using name "IH-10 Frontage Rd" or "I-10 Frontage Rd" or "Katy Fwy Frontage Rd" Or "I/IH-10 Katy Fwy Frontage Rd"</u>


If Frontage Rd is a highway itself different then freeway it parallels should be named same as national guidelines “XX-XX”. Wiki Link <nowiki>https://wazeopedia.waze.com/wiki/USA/Road_names#United_States_Numbered_Highways</nowiki>
If Frontage Rd is a highway itself different then freeway it parallels should be named same as national guidelines for [[Road names#United%20States%20Numbered%20Highways|US Numbered Highways]]


* US-290
*US-290
* SH-121
Parallels SH-290 Toll in Travis County. As to not mess with [[Detour Prevention Mechanisms|Big Detour Prevention Mechanisms]] we leave these as is. Do not add {{nowrapcode|Frontage Rd}} on the end.
 
*SH-121
Frontage Roads that do not have a name or signage does not exist or signage is “Frontage Rd” should be named “XX-XX Frontage Rd” XX-XX being the hwy it parallels.  
<u>ADD GUIDEANCE</u>
 
* I-14 Frontage Rd
* US-175 Frontage Rd


If Fwy / MH is shared between two shielded roads, use primary XX-XX in primary name same as National Guidence. Wiki link <nowiki>https://wazeopedia.waze.com/wiki/USA/Road_names#Concurrent_names</nowiki>
Frontage Roads that do not have a name or signage does not exist or signage is {{nowrapcode|Frontage Rd}}  should be named “XX-XX Frontage Rd” XX-XX being the shielded road it parallels.  


DO NOT ADD SHIELD TO FRONTAGE RD
*I-14 Frontage Rd
*US-175 Frontage Rd


If Fwy / MH is shared between two shielded roads, use primary XX-XX in primary name same as National Guidance for [[Road names#Concurrent%20names|Concurrent names]]
{| class="wikitable"
{| class="wikitable"
|+
|+
!Guidance
!Guidance
!Example
! Example
|-
|-
|Generally, [[shield]] elements should be placed in the “visual instructions” field (''i.e.'', on line 1).
|Generally, [[shield]] elements should be placed in the “visual instructions” field (''i.e.'', on line 1).
|[[File:Shields-line-1.jpg|thumb]]
|[[File:Shields-line-1.jpg|thumb]]
|-
|-
|Rarely, shield elements may be placed in the “toward” field (''i.e.'', on line 2) '''only''' when the shield is near the bottom of a multi-line sign.
| Rarely, shield elements may be placed in the “toward” field (''i.e.'', on line 2) '''only''' when the shield is near the bottom of a multi-line sign.
|[[File:Shield-in-towards.png|thumb]]
|[[File:Shield-in-towards.png|thumb]]
|-
|-
Line 46: Line 49:
|-
|-
|If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
|If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
|[[File:Share-direction.jpg|thumb]]
|[[File:Share-direction.jpg|thumb]]  
|-
|-
|Do '''not''' include text separators between shields, shield directions, or auxiliary legends (“ᴛᴏ”, “ᴠɪᴀ”, “ᴊᴄᴛ”).
| Do '''not''' include text separators between shields, shield directions, or auxiliary legends (“ᴛᴏ”, “ᴠɪᴀ”, “ᴊᴄᴛ”).
|[[File:No-sep.jpg|thumb]]
|[[File:No-sep.jpg|thumb]]
|}
|}
Line 54: Line 57:
====Alt Names:====
====Alt Names:====


* Address match, check GIS
*Address match, check GIS
** <u>If address is IH-XX or N Interstate XX</u>  
**<u>If address is IH-XX or N Interstate XX</u>  
* Frontage Rd
*Frontage Rd
* If named fwy add XX-XX Frontage Rd
*If named fwy add XX-XX Frontage Rd
*  
*


<br />
<br />


====Ramp Name====
====Ramp Name====
[[Road names#Local freeway names and significant bridges]]
Not sure if this following section is needed as it’s already national guidance  
Not sure if this following section is needed as it’s already national guidance  


Line 72: Line 77:


“I-635 N • Lyndon B Johnson Fwy”
“I-635 N • Lyndon B Johnson Fwy”
<nowiki>https://wazeopedia.waze.com/wiki/USA/Road_names#Local_freeway_names_and_significant_bridges</nowiki>


Example pictures of SV / signage or lack there of:  
Example pictures of SV / signage or lack there of:  
Line 90: Line 93:
|+
|+
!Guidance
!Guidance
!Example
! Example
|-
|-
|Generally, [[shield]] elements should be placed in the “visual instructions” field (''i.e.'', on line 1).
|Generally, [[shield]] elements should be placed in the “visual instructions” field (''i.e.'', on line 1).
|[[File:Shields-line-1.jpg|thumb]]
|[[File:Shields-line-1.jpg|thumb]]
|-
|-
|Rarely, shield elements may be placed in the “toward” field (''i.e.'', on line 2) '''only''' when the shield is near the bottom of a multi-line sign.
| Rarely, shield elements may be placed in the “toward” field (''i.e.'', on line 2) '''only''' when the shield is near the bottom of a multi-line sign.
|[[File:Shield-in-towards.png|thumb]]
|[[File:Shield-in-towards.png|thumb]]
|-
|-
Line 102: Line 105:
|-
|-
|Any shield that is preceded by “ᴛᴏ” on the sign should be preceded by “ᴛᴏ” (using small caps) in free text in Waze as well.
|Any shield that is preceded by “ᴛᴏ” on the sign should be preceded by “ᴛᴏ” (using small caps) in free text in Waze as well.
|[[File:TO-bgs.jpg|thumb]]
| [[File:TO-bgs.jpg|thumb]]
|-
|-
|If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
| If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
|[[File:Share-direction.jpg|thumb]]
|[[File:Share-direction.jpg|thumb]]
|-
|-
Line 111: Line 114:
|}
|}


===VIO===
===Visual Turn Instructon===
Top Box should match naming guidelines above. If matching Fwy name and/or signage take out “Frontage Rd” on top box.  
Should be added added to all public street turns onto frontage road. PLR turns for example not top priority. Cross over roads higher priority than side streets.  


“Fwy Name” Or “Local street Signs” or if neither apply “XX-XX Frontage Rd”
[[Turn instruction#Visual%20instructions|Visual instructions Box]] should match naming guidelines above but add shield at beginning.


Second box should be “XX-XX Frontage Rd” if that was not used as top box.
Visual Instruction Box could be made of up two or three components


Added to all public street turns onto frontage road. PLR turns for example not top priority. Cross over roads higher priority than side streets.  
Check with street view or BOTG to verify what signage actually says
 
{{nowrapcode|Roadway Shield}} Plus {{nowrapcode|Fwy Name}} (if applicable) or {{nowrapcode|Local Street Signs}} Plus {{nowrapcode|Frontage Rd}}
 
<u>Provide Examples W/ Photos</u>
 
[[Turn instruction#Toward|Toward Box]] should be used only if control city is visible in used.  
 
<u>Provide Examples W/ Photos</u> 


Use same Example pictures from above but add VIO WME box
Use same Example pictures from above but add VIO WME box
Line 125: Line 136:
|+
|+
!Guidance
!Guidance
!Example
! Example
|-
|-
|Generally, [[shield]] elements should be placed in the “visual instructions” field (''i.e.'', on line 1).
|Generally, [[shield]] elements should be placed in the “visual instructions” field (''i.e.'', on line 1).
|[[File:Shields-line-1.jpg|thumb]]
|[[File:Shields-line-1.jpg|thumb]]
|-
|-
|Rarely, shield elements may be placed in the “toward” field (''i.e.'', on line 2) '''only''' when the shield is near the bottom of a multi-line sign.
| Rarely, shield elements may be placed in the “toward” field (''i.e.'', on line 2) '''only''' when the shield is near the bottom of a multi-line sign.
|[[File:Shield-in-towards.png|thumb]]
|[[File:Shield-in-towards.png|thumb]]
|-
|-
Line 139: Line 150:
|[[File:TO-bgs.jpg|thumb]]
|[[File:TO-bgs.jpg|thumb]]
|-
|-
|If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
| If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
|[[File:Share-direction.jpg|thumb]]
|[[File:Share-direction.jpg|thumb]]
|-
|-
Line 147: Line 158:


===TTS===
===TTS===
TTS should match VIO with • and >> symbol
TTS should match VIO  
 
Between Numbered highway and Name
 
>> Before control Cities


Include same examples pictures as above with TTS WME box.
Include same examples pictures as above with TTS WME box.

Revision as of 02:07, 14 December 2022

This new page is currently undergoing modifications. The information presented should be considered a draft, not yet ready for use. Content is being prepared by one or more users. Do not make any changes before you send a private message to nhanway. Please use the talk page for thoughts and ideas on setting up this content.
Last update Dec 13, 2022

Texas Frontage Rds

DO NOT ADD SHIELD TO FRONTAGE RD

Naming

This is guidance for primary and alternate name(s) for Frontage Roads. Important to remember that those using Apple CarPlay or AndroidAuto do not get editable visual turn instruction therefor, choosing primary segment name is very important. We hope that in the future visual turn instruction will work in Apple CarPlay or AndroidAuto.

Primary Name

Primary name should match street signs and/or freeway name if present. We don't want the primary name of the frontage road to change at every intersection. Primary name should only change if the frontage road changes which road it parallels or the named freeway it parallels is no longer named. The primary name Frontage Road should always have Frontage Rd on end. Also do not add Cardinal Directions unless they are

  • Lyndon B Johnson Fwy Frontage Rd

Parallels I-635 in Dallas County. Street signs for turns onto Lyndon B Johnson Fwy's Frontage road commonly say I-635 LBJ Fwy or LBJ Fwy or I-635 Lyndon B Johnson Fwy. It is common knowledge that LBJ= Lyndon B Johnson and so in Waze we spell in out so TTS will work.

  • US-175 Frontage Rd

Parallels US-175 in Dallas County. Street signs for turns on to US-175 Frontage road commonly say N Highway 175. It is common in Texas for street signs to spell out US Highways so but we follow national guidelines for naming US Numbered Highways.

  • IH-10 Frontage Rd

Parallel I-10 in Harris County. ADD GUIDEANCE are we using name "IH-10 Frontage Rd" or "I-10 Frontage Rd" or "Katy Fwy Frontage Rd" Or "I/IH-10 Katy Fwy Frontage Rd"

If Frontage Rd is a highway itself different then freeway it parallels should be named same as national guidelines for US Numbered Highways

  • US-290

Parallels SH-290 Toll in Travis County. As to not mess with Big Detour Prevention Mechanisms we leave these as is. Do not add Frontage Rd on the end.

  • SH-121

ADD GUIDEANCE

Frontage Roads that do not have a name or signage does not exist or signage is Frontage Rd should be named “XX-XX Frontage Rd” XX-XX being the shielded road it parallels.

  • I-14 Frontage Rd
  • US-175 Frontage Rd

If Fwy / MH is shared between two shielded roads, use primary XX-XX in primary name same as National Guidance for Concurrent names

Guidance Example
Generally, shield elements should be placed in the “visual instructions” field (i.e., on line 1).
Rarely, shield elements may be placed in the “toward” field (i.e., on line 2) only when the shield is near the bottom of a multi-line sign.
Add shields in the order they appear on the sign assembly.
Any shield that is preceded by “ᴛᴏ” on the sign should be preceded by “ᴛᴏ” (using small caps) in free text in Waze as well.
If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
Do not include text separators between shields, shield directions, or auxiliary legends (“ᴛᴏ”, “ᴠɪᴀ”, “ᴊᴄᴛ”).

Alt Names:

  • Address match, check GIS
    • If address is IH-XX or N Interstate XX
  • Frontage Rd
  • If named fwy add XX-XX Frontage Rd


Ramp Name

Road names#Local freeway names and significant bridges

Not sure if this following section is needed as it’s already national guidance

If named Fwy add • Fwy Name

“to I-635 N • Lyndon B Johnson Fwy”

Fwy Name

“I-635 N • Lyndon B Johnson Fwy”

Example pictures of SV / signage or lack there of:

LBJ “Dallas”

US-175 “N/S Highway 175” “Dallas”

US-290 / SH-290 “Austin”

I-20 “Dallas”

I-14 / US-190 “Killeen”

Guidance Example
Generally, shield elements should be placed in the “visual instructions” field (i.e., on line 1).
Rarely, shield elements may be placed in the “toward” field (i.e., on line 2) only when the shield is near the bottom of a multi-line sign.
Add shields in the order they appear on the sign assembly.
Any shield that is preceded by “ᴛᴏ” on the sign should be preceded by “ᴛᴏ” (using small caps) in free text in Waze as well.
If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
Do not include text separators between shields, shield directions, or auxiliary legends (“ᴛᴏ”, “ᴠɪᴀ”, “ᴊᴄᴛ”).

Visual Turn Instructon

Should be added added to all public street turns onto frontage road. PLR turns for example not top priority. Cross over roads higher priority than side streets.

Visual instructions Box should match naming guidelines above but add shield at beginning.

Visual Instruction Box could be made of up two or three components

Check with street view or BOTG to verify what signage actually says

Roadway Shield Plus Fwy Name (if applicable) or Local Street Signs Plus Frontage Rd

Provide Examples W/ Photos

Toward Box should be used only if control city is visible in used.

Provide Examples W/ Photos

Use same Example pictures from above but add VIO WME box

Guidance Example
Generally, shield elements should be placed in the “visual instructions” field (i.e., on line 1).
Rarely, shield elements may be placed in the “toward” field (i.e., on line 2) only when the shield is near the bottom of a multi-line sign.
Add shields in the order they appear on the sign assembly.
Any shield that is preceded by “ᴛᴏ” on the sign should be preceded by “ᴛᴏ” (using small caps) in free text in Waze as well.
If two or more adjacent shields have the same direction, omit the direction from all but the last such shield (they “share” this direction)—unless there is a compelling reason not to do so.
Do not include text separators between shields, shield directions, or auxiliary legends (“ᴛᴏ”, “ᴠɪᴀ”, “ᴊᴄᴛ”).

TTS

TTS should match VIO

• Between Numbered highway and Name

>> Before control Cities

Include same examples pictures as above with TTS WME box.