Alternate street names for TTS, zip codes, abbreviations etc
UPDATE3. Summary:
Hi!
Discussing with Dekis my previous suggestion Client-side Abbreviations, together we came up with the following idea.
We propose to use "Alternate street names" feature as Attribute-Value pairs to specify advanced properties of road segments. For instance, we could use Alt City as an attribute name (starting with hash #) and Alt Street as a value.
Here are some possible usage scenarios:
I hope you grasp the idea.
UPDATE1: WME might show and accept those properties from editors with 5 cones up only.
UPDATE1: All we need at the moment is to discuss and agree the syntax with Waze devs. Alt City/Street fields are already there in WME so we could begin to add those properties while Waze would be implementing them.
What do you think?
- To adjust some of non-common segment properties, we suggest to implement Key-Value pairs in WME. We have no intention to use these properties for the vast majority or the roads.
- These Key-Values available for 3+ or 5+ cones editors only.
- Waze devs can implement it in a way they like:
- as a separate Key-Value system similarly to Alternate names;
- adding a Key to existing Alternate Names, so they would become "Key, Alt City (Value 1), Alt Street (Value 2)";
- using existing Alt City as a Key and Alt Street as a Value or vice-versa;
- as fields on a separate tab (next to General) in WME, available for 3+ or 5+ cones editors only;
- or any other way (it is not really important).
- How could we benefit from these properties? Here are the most reasonable applications at the moment IMHO:
- To correct TTS pronunciation, using, for instance, Nuance phoneme set (Nuance Grammar Developer's Guide (PDF), page 85). So, if the property is attached to a road segment, Waze App use it to pronounce the street name.
- To put shields on the map (Waze is about to implement this, so details are subject to further discussion).
- To handle planned road closures (i.e., closed-until) and time-restricted turns (Waze is about to implement this, so details are subject to further discussion).
- Alt streets will be available for search, so we don't need a "short name" property.
- Waze (or someone else) to suggest better idea to localize map data.
- Waze to implement zip codes/administrative divisions in (some) countries as separate fields in address block.
Hi!
Discussing with Dekis my previous suggestion Client-side Abbreviations, together we came up with the following idea.
We propose to use "Alternate street names" feature as Attribute-Value pairs to specify advanced properties of road segments. For instance, we could use Alt City as an attribute name (starting with hash #) and Alt Street as a value.
Here are some possible usage scenarios:
- To improve TTS pronunciation:
Street: full street name Waze uses by default
Alt City: #tts Alt Street: if present, a spoken form of the street name for TTS
Example:
Street: CeBIT Street <- a name for search and to display
Alt City: #tts Alt Street: C. bit Street <- Waze uses this to correctly pronounce the street name - To abbreviate long street names:
Street: full street name Waze uses by default
Alt City: #short Alt Street: if present, a short street name to display and to pronounce (if #tts is not there)
For instance:
Street: Estakada imienia generała brygady piłotów Mateusza Iżyckiego <- full name for search
Alt City: #short Alt Street: Estakada Iżyckiego <- short street name to display/pronounce - To complement/disambiguate an address:
Street: full street name Waze uses by default
Alt City: #zip Alt Street: if present, a zip code Waze uses for search
Alt City: #province Alt Street: if present, a province name/code Waze uses for search
Alt City: #district Alt Street: if present, a district name Waze uses for search
etc - UPDATE2: probably a bad idea (thanks to Kuhlkatz) To localize some of above (or below):
Street: full street name Waze uses by default
Alt City: #<attribute>:<LOCALE> Alt Street: if :<LOCALE >suffix is present, Waze use the <attribute> just for specific <LOCALE>
For instance:
Street: вулиця Маршала Малиновського <- default street name in Cyrillic
Alt City: #short Alt Street: Малиновського <- short street name in Cyrillic
Alt City: #short:en_EN Alt Street: Malynovs'koho <- short & transliterated street name
- UPDATE1: To handle road closures:
Alt City: #closed Alt Street: if present, Waze temporarily does not use this road for navigation
Alt City: #closed-until Alt Street: dd.mm.YYYY -- Waze does not use this road until date specified
etc - UPDATE1: Complicated house numbers:
Alt City: #house Alt Street: number (i.e. 23B/2) -- if present, Waze uses this field to search complicated house numbers (small invisible segments should be placed accordingly) - UPDATE1: Time-restricted segments or turns:
Alt City: #restricted-time Alt Street: date/time range -- if present, Waze does not use the segment for navigation if date/time range match ETA
Alt City: #restricted-AB-time Alt Street: date/time range -- if present, Waze restrict traffic one way (A->B)
etc
For instance:
Alt City: #restricted-time Alt Street: Wk0705-1000,Sa,Su <- restrict traffic weekdays from 9:05 AM to 10:00 AM, Sturday and Sunday - UPDATE1: Shields:
Alt City: #shield Alt Street: <color><shape>:<text> -- if present, Waze display <text> on a shield shaped/coloured as <color><shape>
For instance:
Alt City: #shield Alt Street: GR:E40 <- green rectangular shield with E40 text - UPDATE1: Cardinal directions:
Alt City: #dir Alt Street: N, S, E or W -- if present, Waze uses this info to display or for TTS - UPDATE1: City center:
Alt City: #city-center Alt Street: name -- if present, Waze uses this segment as a center of the corresponding city - UPDATE1: Alternate names (yes!):
Alt City: name Alt Street: name -- if present, Waze uses this alt names for search (note Alt City name does not start with hash #)
I hope you grasp the idea.
UPDATE1: WME might show and accept those properties from editors with 5 cones up only.
UPDATE1: All we need at the moment is to discuss and agree the syntax with Waze devs. Alt City/Street fields are already there in WME so we could begin to add those properties while Waze would be implementing them.
What do you think?
Re: Alternate street names for TTS, zip codes, abbreviations