As mapcat has said, we should not depend on TTS changes for local differences in naming.
I would however encourage the use of “SR-xxx” in ramp naming as the best method to both maintain consistency with most of the country and to shorten the displayed text, as ramps names can get long.
Yes I know that TTS will say “State Route” instead of “State Road”. I’m sure most people will not have an issue with that. While states like Michgian can use a single letter and number such as “M-52” in a ramp name (and elsewhere) and it will be pronounced as the letter with the numbers 52, this can not be done with Indiana as mapcat mentioned, as the two letters “IN” will be pronounced as the word “in”.
We are still working on getting Waze to pronounce every capitalized two letter state abbreviation as their state. When or IF this will ever happen is unknown. Therefore we should be wary of making any mass changes that may never be supported.
I have been working on a TTS project for a couple of years now, and only a couple of our suggested changes from that project have been implemented. At our Waze Meet-up in Israel, I was “assigned” to another Waze staff member who was to take over the TTS issue. The issues I submitted immediately after the meet-up were accepted, however there has not been any feedback since.
I do agree with others that “Co Rd” or “CR” not be used in the county road names. As Bruce mentioned, “Co Rd” will be pronounced, but not as “County Rd”. It will pronounce “Co” as a the word “co” and will not expand it to the word “County”.
If a consensus for Indiana does wants “County Road” in the country road names, then “CR” should be used as TTS will indeed say, “County Road”. However this will likely require a massive renaming of road in Indiana, which I do not feel is a good choice.