Names
Named entities in Overture share a common schema.
primary
If a feature has a name, expect names
to have at least one property: primary
. This will always be populated with the localized name of a feature.
id: 08b2aa845a18afff02009f7c732067c5
names:
primary: The White House
common
Common name variations are translations of a name.
id: 08b2aa845a18afff02009f7c732067c5
names:
common:
de: Weißes Haus
hi: व्हाइट हाउस
fi: Valkoinen talo
ru: Белый дом
pt: Casa Branca
lt: Baltieji Rūmai
hr: Bijela kuća
fr: Maison Blanche
hu: Fehér Ház
br: Ti Gwenn
si: ධවල මන්දිරය
uk: Білий дім
sk: Biely dom
sv: Vita huset
ko: 백악관
en: White House
ku: Qesra Spî
it: Casa Bianca
es: Casa Blanca
zh: 白宫
cs: Bílý dům
ja: ホワイトハウス
fa: کاخ سفید
ro: Casa Albă
nl: Witte Huis
tr: Beyaz Saray
rules
Additional names variations such as official, alternate, or short exist as rules
.
Rules can also have side
and geometric
range scoping. Read more about scoping rules here.
id: 08b2aa845a18afff02009f7c732067c5
names:
rules:
- variant: alternate
language: hr
value: Bila kuća
between: null
side: null
Languages
Languages in the Overture Maps schema are identified by IETF BCP-47 language tags; the same tag scheme is used for common
map entries and language
values in rules.
This pattern recognizes BCP-47 language tags at the lexical or syntactic level. It verifies that candidate tags follow the grammar described in the RFC, but not that they are validly registered tag in IANA's language subtag registry.
In the regular expression, '(:?'
indicates a non-capturing group, and all the top-level or non-nested groups represent top-level components of langtag
referenced in the syntax section of https://www.rfc-editor.org/rfc/bcp/bcp47.txt. In particular, the top-level groups in left-to-right order represent:
1. language
2. ["-" script]
3. ["-" region]
4. *("-" variant)
5. *("-" extension)