User:Nhanway/TXFrontageRds View history

Revision as of 00:30, 14 December 2022 by Nhanway (talk | contribs) (Add Tables, Need to change photos eventually)

Work in progress DO NOT FOLLOW AS THIS IS BEING TESTED

Texas Specific Frontage Rd Guidance

Naming

Important to remember that those using CarPlay or AndroidAuto segment name is very important as TIO and TTS does not work yet.

Primary:

Primary name should match street signs or freeway name if present. Add “Frontage Rd” on endː

  • Lyndon B Johnson Fwy Frontage Rd
  • N Highway 175 Frontage Rd
  • IH-10 Frontage Rd

If Frontage Rd is a highway itself different then freeway it parallels should be named same as national guidelines “XX-XX”. Wiki Link https://wazeopedia.waze.com/wiki/USA/Road_names#United_States_Numbered_Highways

  • US-290
  • 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.

  • 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 https://wazeopedia.waze.com/wiki/USA/Road_names#Concurrent_names

DO NOT ADD SHIELD TO FRONTAGE RD

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

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”

https://wazeopedia.waze.com/wiki/USA/Road_names#Local_freeway_names_and_significant_bridges

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 (“ᴛᴏ”, “ᴠɪᴀ”, “ᴊᴄᴛ”).

VIO

Top Box should match naming guidelines above. If matching Fwy name and/or signage take out “Frontage Rd” on top box.

“Fwy Name” Or “Local street Signs” or if neither apply “XX-XX Frontage Rd”

Second box should be “XX-XX Frontage Rd” if that was not used as top box.

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

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 with • and >> symbol

Include same examples pictures as above with TTS WME box.