Street names can contain a lot of standard abbreviations (for example, St for Street, Rd for Road, W for West, and so on). When generating directions in text form, it is common to include these abbreviations, but when converting these instructions for voice guidance, these abbreviations need to be expanded. The Abbreviations table stores the rules on expanding the abbreviations. You can review all existing abbreviations, modify and remove rules, add custom abbreviations, and maintain abbreviations only for regions where networks are located.
Expanding abbreviations in the directions improves the quality of conversion by making use of the additional details of the street such as: language, knowledge about street name components (prefix, type, suffix), geographic context, and street name or route number.
For example, ObjectID=7 in the image below is interpreted as: For a street whose name is in the English language and is located in the United States, and its name is an ordinary street name; if its Directional component contains the abbreviation SW, this abbreviation is expanded as Southwest.
Schema of Abbreviations table
| Field name | Description |
|---|---|
| Language | The language of the street name, coded in the BCP-47 standard (for example, en, ru, fr). |
| CountryRegionCode | The country (and optionally, region) where this street is located, coded in the ISO 3166-2 standard. See the following examples:
|
| NameClass | The classification of the street name, either as an ordinary street name or as a route number, using the following values:
|
| NameComponent | The component of the street name to which the abbreviation applies:
|
| AbbreviationText | The text of the abbreviation. |
| VoiceText | The text of the expanded form of the abbreviation. |
Note:
If you want to use the Abbreviations Table property, you must create the abbreviations table pertinent to your street data. You can use the above schema to create an abbreviations table.