State Specific Routes
Recently, some states have been naming their state routes in various ways. For example, I believe Pennsylvania is "PA-XX", etc.
This idea should probably be built upon. For example, from what I read, I believe Maryland editors want their State Routes to be called "Route XX". However, Tennesseans normally refer to roads as "Highway XX".
Instead of the map editors inventing hacks and disagreements to get standards like these to work, I'm thinking we should ask Waze formally to set something up. Basically, I'm asking what you guys think of introducing (over the long-term), a standard of naming state routes "[State Abbreviation] - [Route Number]".
Then, each State could come to an agreement on how for Waze to display and pronounce these roads. Waze, if all works well, would parse similar to this:
(WME Name) "TN-153" -> (Display) "Hwy 153" / (TTS) "Highway 153"
This system would also allow the State's to eventually receive State-specific shielding with little headache.
If you guys think this is a decent enough of an idea, maybe we should acquire a list of the State's and how they would want it to be displayed on the client and sent to the TTS engine. Then we could see if Waze would comply with that list.
Here is the link:
https://skydrive.live.com/redir.aspx?ci ... vuxcisLStQ
This idea should probably be built upon. For example, from what I read, I believe Maryland editors want their State Routes to be called "Route XX". However, Tennesseans normally refer to roads as "Highway XX".
Instead of the map editors inventing hacks and disagreements to get standards like these to work, I'm thinking we should ask Waze formally to set something up. Basically, I'm asking what you guys think of introducing (over the long-term), a standard of naming state routes "[State Abbreviation] - [Route Number]".
Then, each State could come to an agreement on how for Waze to display and pronounce these roads. Waze, if all works well, would parse similar to this:
(WME Name) "TN-153" -> (Display) "Hwy 153" / (TTS) "Highway 153"
This system would also allow the State's to eventually receive State-specific shielding with little headache.
If you guys think this is a decent enough of an idea, maybe we should acquire a list of the State's and how they would want it to be displayed on the client and sent to the TTS engine. Then we could see if Waze would comply with that list.
Here is the link:
https://skydrive.live.com/redir.aspx?ci ... vuxcisLStQ
State Specific Routes