--- metadata: - name: generator content: Diplodoc Platform v5.52.0 alternate: - https://business.yango.com/support/en/branches/branches-xml.md - href: en/branches/branches-xml.md type: text/markdown title: Markdown version - href: ../llms.txt type: text/markdown title: llms.txt --- > **Documentation Index:** Fetch the complete configuration index at https://business.yango.com/support/en/llms.txt # Updating data via XML files If you have more than 30 branches in your chain, we recommend updating chain information in Yango for Business using XML files. Data about your branches will be updated based on the contents of the XML file: - New branches will be added to the database and will appear in Yango services with the specified attributes. - Branch cards whose details weren't added to the XML file will be closed. ## Step 1. Prepare an XML file {#step-1} ### Content requirements {#requirements} {% note alert %} If these requirements aren't met, or if the file data doesn't match the website, the file won't be published. {% endnote %} Moderators verify that the data in the file matches the data on the website: - **Address** Legal addresses don't need to be included. - **Phones** Numbers must be identical. If the website displays proxy numbers that differ from those in the file, specify this when submitting the file. - **Business hours** If any locations have restricted access, specify this when submitting the file. - **Category** The primary category must be the same on the website and in the file. Categories must be semantically compatible. Correct: `Tire fitting, Auto repair shop` Incorrect: `Tire fitting, Confectionery` - Number of branches. - No duplicates — no two organizations may share identical addresses or coordinates. {% note info "Exceptions" %} Categories that may share an address but must have distinct coordinates (differing by more than 30 meters): - **ATMs** - **Parcel lockers** - **Vending machines** - **Payment kiosks** {% endnote %} The following attributes are recommended to match the organization's website: - **Extension number** - **Additional categories** - **Holiday hours** - **Building number and letter designations in addresses** ### Technical requirements {#requirements-tech} 1. The XML file must be UTF-8 encoded. 2. The file must not be empty. 3. The file must not contain empty elements. 4. The standard XML header must start from the first line, from the zero character. For example:
```xml ```
5. The XML must be well-formed. The file can be checked manually on your computer using the [schema (XML Schema Definition)](https://doc-static.yandex.net/src/support/business-priority/en/partner-public-en.xsd). 6. The data can't contain HTML attributes. 7. ASCII control characters in the range `0`–`31` are not permitted in text fields. 6. The data can't contain HTML attributes. 7. ASCII control characters in the range 0–31 are not permitted in text fields. {% note info %} Exceptions: `9` (tab), `10` (line feed), `13` (carriage return). {% endnote %} 8. `&` must be escaped as `&`. 9. To describe branches, use [a set of mandatory and additional attributes](#parameters-description). Each branch property should be wrapped in a separate attribute (see [Sample file](#example)). If a property has multiple values (for example, phone numbers), pass multiple attributes with the same name. 10. Each `company-id` in the XML file must be unique. 11. All data in an XML file must be in the same language. Multilingual attributes are an exception (see [Attribute description](#parameters-description)). A _multilingual attribute_ is an attribute in an XML file with values in several languages. The language is defined by the `lang` attribute. For each new language, create an item with the corresponding `lang` attribute in a separate row. {% cut "Example" %}
```xml
Büyük Postane Cd. No. 7, İstanbul
101a Baker Street, London
```
{% endcut %} You can find the current `lang` values in the [XML schema](https://doc-static.yandex.net/src/support/business-priority/en/partner-public-en.xsd). To add other languages, contact [support](https://business.yango.com/support/en/troubleshooting/main.md). ### Attribute description {#parameters-description} #| ||**Attribute**|**Description**|**Multilingual element**|**Required field**|| ||companies|{% include [popup-companies](../_includes/popup/id-popup/companies.md) %}|Not applicable|Yes|| ||company|{% include [popup-company](../_includes/popup/id-popup/company.md) %}|Not applicable|Yes|| ||company-id|{% include [popup-company-id](../_includes/popup/id-popup/company-id.md) %}|No|Yes|| ||name|{% include [popup-name](../_includes/popup/id-popup/name.md) %}|Yes|Yes|| ||shortname|{% include [popup-shortname](../_includes/popup/id-popup/shortname.md) %}|Yes|No|| ||name-other|{% include [popup-name-other](../_includes/popup/id-popup/name-other.md) %}|Yes|No|| ||address|{% include [popup-address](../_includes/popup/id-popup/address.md) %}|Yes|Yes|| ||country|{% include [popup-country](../_includes/popup/id-popup/country.md) %}|Yes|No|| ||address-add|{% include [popup-address-add](../_includes/popup/id-popup/address-add.md) %}|Yes|No|| ||phone|{% include [popup-phone](../_includes/popup/id-popup/phone.md) %}|No|Yes|| ||**Elements nested in phone**|>|>|>|| ||number|{% include [popup-number](../_includes/popup/id-popup/number.md) %}| |Yes|| ||ext|{% include [popup-ext](../_includes/popup/id-popup/ext.md) %}| | || ||info|{% include [popup-info](../_includes/popup/id-popup/info.md) %}| | || ||type|{% include [popup-type](../_includes/popup/id-popup/type.md) %}| |Yes|| || |>|>|>|| ||email|{% include [popup-email](../_includes/popup/id-popup/email.md) %}|No|No|| ||url|{% include [popup-url](../_includes/popup/id-popup/url.md) %}|No|Yes|| ||add-url|{% include [popup-add-url](../_includes/popup/id-popup/add-url.md) %}|No|No|| ||info-page|{% include [popup-info-page](../_includes/popup/id-popup/info-page.md) %}|No|No|| ||working-time|{% include [popup-working-time](../_includes/popup/id-popup/working-time.md) %}|Yes|Yes|| ||scheduled-working-time|{% include [popup-scheduled-working-time](../_includes/popup/id-popup/scheduled-working-time.md) %}| |No|| ||rubric-id|{% include [popup-rubric-id](../_includes/popup/id-popup/rubric-id.md) %}|No|Yes|| ||actualization-date|{% include [popup-actualization-date](../_includes/popup/id-popup/actualization-date.md) %}|No|Yes|| ||coordinates|{% include [popup-coordinates](../_includes/popup/id-popup/coordinates.md) %}|No|Yes (if the address is inaccurate)|| ||**Elements nested in coordinates**|>|>|>|| ||lon|{% include [popup-lon](../_includes/popup/id-popup/lon.md) %}| |Yes (if the address is incomplete)|| ||lat|{% include [popup-lat](../_includes/popup/id-popup/lat.md) %}| |Yes (if the address is incomplete)|| || |>|>|>|| ||photos|{% include [popup-photos](../_includes/popup/id-popup/photos.md) %}|No|No|| ||**Elements nested in photos**|>|>|>|| ||tag|{% include [popup-tag](../_includes/popup/id-popup/tag.md) %}| | || || |>|>|>|| ||feature-boolean|{% include [popup-feature-boolean](../_includes/popup/id-popup/feature-boolean.md) %}|No|No|| ||feature-enum-single|{% include [popup-feature-enum-single](../_includes/popup/id-popup/feature-enum-single.md) %}|No|No|| ||feature-enum-multiple|{% include [popup-feature-enum-multiple](../_includes/popup/id-popup/feature-enum-multiple.md) %}|No|No|| ||feature-numeric-single|{% include [popup-feature-numeric-single](../_includes/popup/id-popup/feature-numeric-single.md) %}|No|No|| ||feature-numeric-multiple|{% include [popup-feature-numeric-multiple](../_includes/popup/id-popup/feature-numeric-multiple.md) %}|No|No|| ||feature-in-units-single|{% include [popup-feature-in-units-single](../_includes/popup/id-popup/feature-in-units-single.md) %}|No|No|| ||feature-in-units-multiple|{% include [popup-feature-in-units-multiple](../_includes/popup/id-popup/feature-in-units-multiple.md) %}|No|No|| ||feature-range-single|{% include [popup-feature-range-single](../_includes/popup/id-popup/feature-range-single.md) %}|No|No|| ||feature-range-in-units-single|{% include [popup-feature-range-in-units-single](../_includes/popup/id-popup/feature-range-in-units-single.md) %}|No|No|| ||feature-range-in-units-multiple|{% include [popup-feature-range-in-units-multiple](../_includes/popup/id-popup/feature-range-in-units-multiple.md) %}|No|No|| ||feature-text-single|{% include [popup-feature-text-single](../_includes/popup/id-popup/feature-text-single.md) %}|No|No|| |# ### Additional attributes {#parameters-additional} You can pass additional parameters for your chain or branch in an XML file. For example, you can show if there is parking available near your shopping center or which currency can be withdrawn from your ATM. To get an XML file with a list of possible attributes for your business category: 1. On the chain page, go to **Branches**. 1. Under **Branch management**, choose **File**. 1. Click **Export data** → **Download features**. {% note info %} Errors in attribute values will not block publication of the XML file, but the affected attributes will not be published. {% endnote %} ### Sample file {#example} {% note info %} To view an attribute description, click the name of any underlined attribute in the sample file. {% endnote %}
```xml <[companies](*companies)> <[company](*company)> <[company-id](*company-id)>770704034 <[name](*name) lang="en">Anchor <[shortname](*shortname) lang="en">Anchor <[address](*address) lang="en">101 Baker Street, London <[country](*country) lang="en">United Kingdom UK <[address-add](*address-add) lang="en">Rose Mall, Floor 2, Suite 203 <[phone](*phone)> <[number](*number)>020 1234 5678 <[ext](*ext)>555 <[info](*info)>Secretary <[type](*type)>phone phone 034 2202 3303 <[email](*email)>info@anchor.com <[url](*url)>http://www.anchor.com <[add-url](*add-url)>http://www.anchor.com <[info-page](*info-page)>http://www.test.com/anchor <[working-time](*working-time) lang="en">every day, 10:00-21:00 <[rubric-id](*rubric-id)>184106414 184106394 <[actualization-date](*actualization-date)>1511724300 <[photos](*photos) gallery-url="http://test.com/anchor/gallery"> <[tag](*tag)>EXTERIOR <[tag](*tag)>FOOD <[feature-boolean](*feature-boolean) name="internet" value="1"/> <[feature-enum-single](*feature-enum-single) name="star" value="five"/> <[feature-numeric-single](*feature-numeric-single) name="room_number" value="15"/> <[feature-enum-multiple](*feature-enum-multiple) name="hotel_type" value="art_hotel"/> <[feature-numeric-multiple](*feature-numeric-multiple) name="license_number" value="004555"/> <[feature-in-units-single](*feature-in-units-single) name="minimum_order" unit="money" unit-value="gbp" value="30"/> <[feature-in-units-multiple](*feature-in-units-multiple) name="ats_by_type" unit="apartment_type" unit-value="single" value="200"/> <[feature-range-single](*feature-range-single) name="number_seats_banquet_hall" from="15" to="20"/> <[feature-range-in-units-single](*feature-range-in-units-single) name="tickets" unit="money" unit-value="gbp" from="10" to="15"/> <[feature-range-in-units-single](*feature-range-in-units-single) name="price_1_min" unit="money" unit-value="gbp" from="7" to="10"/> <[feature-range-in-units-multiple](*feature-range-in-units-multiple) name="tea" unit="money" unit-value="gbp" from="100" to="300"/> <[feature-text-single](*feature-text-single) value="Anchor_free_wi-fi" name="ssid"/> 7707040070 Anchor Bank Anchor Bank <[name-other](*name-other) lang="en">Branch 2
6 Mathew Street, Liverpool, United Kingdom
phone 040 9988 7444 http://www.anchorbank.com/ weekdays 8:30–18:00, Sat 9:00–14:30 184106974 23.09.2019 <[coordinates](*coordinates)> <[lon](*lon)>48.295532 <[lat](*lat)>55.616051 ```
## Step 2. Upload the file to your website {#step-2} Upload the file to your website using an updatable link. The data should be accessible via HTTP or HTTPS. ## Step 3. Add a link to the file in Yango for Business {#step-3} 1. On the chain page, go to **Branches**. 1. Under **Branch management**, choose **File**. 1. Add a link to the file, select the **XML** type, and click **Check**. Checking the file may take several hours. 1. If the file is verified successfully, click **Post**. In the window that opens, check the changes in the branches. The map can show up to 50 branches with changes. 1. Click **Yes, start the upload**. The file data will be moderated and uploaded to the Yango for Business database. If the file is large, the data upload may take several days. If errors are found when checking the file, you'll see an error message. Fix the errors and re-submit the file for review. To view the branch changes uploaded to the Yango for Business database from the file, click **Upload history**. The button will be available 24 hours after the first upload. Yango Maps will show new branches and other changes in a few days. Write to support [*status]: - Status. - Name. - Phone numbers. - Websites. - Business category. - Services. - Email. - Business hours. - Business hours for. [*for-xml]: - Data about your branches will always be up-to-date in all Yango services and mobile applications. Your potential customers will be able to easily find the nearest branch using [Yango Maps](https://maps.yango.com). - You can fully automate the transfer of data about branches by configuring exports from 1C, ERP (SAP, Axapta), or other systems. - You can provide all the information about branches, including photos and additional parameters, in XML files. [*name-other]: Alternative name of the branch (if there are multiple names, each one is listed in a separate element). Specified without quotation marks, case-sensitive. [*companies]: Root attribute. [*company]: Branch description Nested in the root attribute. There can be any number of `company` attributes. [*company-id]: Permanent unique ID of the branch (assigned by the chain owner). Can contain any set of numbers and Latin letters. [*name]: Name of the branch. Specified without quotation marks, case-sensitive. [*shortname]: Short name of the branch to be displayed next to placemarks on Yango Maps, up to 25 characters. Specified without quotation marks, case-sensitive. [*address]: The branch address (on one line). Multilingual element. If the element contains only the street name and house number, use the `locality‑name` element specifying the locality. [*country]: Country. Specified in full, without abbreviations. [*address-add]: Additional address information that doesn't apply to other elements (shopping center/shopping and entertainment complex/shopping and entertainment center, floor, office, premises, boutique, entrance). For example, Romashka shopping center, floor 2, office 203. Doesn't include a detailed description of the route to the address (100 meters from the metro station to the north, the blue building to the right of Pushkinsky Public Garden). Don't use brackets or quotation marks. [*phone]: Compound element. Phone number (if there are several phone numbers, specify each one in a separate element). [*number]: The landline or mobile phone number. The format is `[country code]` (`[city code]`) `[phone number]`. [*ext]: Extension, without comments, words, or delimiters. [*info]: Information about the phone number, such as "director" or "reception". This element shouldn't contain information about the phone type. [*type]: Phone type. Acceptable values: - `phone`: Phone number. - `fax`: Fax number. - `phone‑fax`: Phone/fax number. [*email]: Email address (if there are multiple addresses, specify each one in a separate element). [*url]: The chain's main website. Specified in lowercase, in full, including http:// or https://. [*add-url]: Additional website of the chain (such as links to social media pages). The URL of the page with branch information on the chain website is specified in the `info‑page` element. [*info-page]: URL of the page with branch information on the chain website. The address must contain the domain name of the chain website. Specified in lowercase, in full, including http:// or https://. [*working-time]: Opening hours. Days off and non-working days aren't specified. [*rubric-id]: [The ID of the business category](https://doc-static.yandex.net/src/support/business-priority/en/rubrics_en.xlsx) this branch belongs to. Branches can have up to three business categories, but at least one of them should match the chain category. If a branch has multiple business categories, specify each one in a separate element. [*actualization-date]: Date updated. Corresponds to the time of the last update. Used to avoid downloading information received during the previous check. The content can be specified in the following format: - `DD.MM.YYYY`; - [UNIX-time](https://ru.wikipedia.org/wiki/Unix-время): specified in milliseconds from `00:00:00.000 01.01.1970`. [*photos]: A link to the gallery or a page on the chain site with all photos. If there are multiple photos, each one is in a separate photo element. It can contain the following attributes: - `alt`: Text description of the photo in free form. - `type`: Photo type. Can take a single value: `interior`. [*tag]: Photo tag. Set inside the photos element. Acceptable values: - `INTERIOR`: Interior. - `EXTERIOR`: Exterior. - `ENTER`: Entrance. - `LOGO`: Logo. - `FOOD`: Food, drinks. - `GOODS`: Goods. - `MENU`: Cafe or restaurant menu. - `ACCESSIBILITY`: Ramps, lifts for people with disabilities, and more. - `DEVICES`: Electronic devices. - `SERVICES`: Services. [*feature-boolean]: Branch property. If there are multiple properties, each one is specified in a separate element. Acceptable values: - `0: No`; - `1: Yes`. [*feature-enum-single]: Branch property. [*feature-numeric-single]: A branch property with a numeric value. [*feature-enum-multiple]: Branch property. If there are multiple properties, each one is specified in a separate element. [*feature-numeric-multiple]: A branch property whose value is defined in units. If there are multiple properties, each one is specified in a separate element. [*feature-in-units-single]: A branch property whose value is defined in units. [*feature-in-units-multiple]: A branch property whose value is defined in units. If there are multiple properties, each one is specified in a separate element. [*feature-range-single]: A branch property that has a range value. [*feature-range-in-units-single]: A branch property that has a range value in units. [*feature-range-in-units-multiple]: A branch property that has a range value in units. If there are multiple properties, each one is specified in a separate element. [*feature-text-single]: A branch property in text format. [*coordinates]: Compound element. Coordinates (latitude and longitude). [*lon]: Longitude. Use the dot as the decimal separator. [*lat]: Latitude. Use the dot as the decimal separator. {% included (../_includes/popup/id-popup/companies.md) %} Root attribute. {% endincluded %} {% included (../_includes/popup/id-popup/company.md) %} Branch description. Nested in the root attribute. There can be any number of `company` attributes. {% endincluded %} {% included (../_includes/popup/id-popup/company-id.md) %} Permanent unique ID of the branch (assigned by the chain owner). Can contain any set of numbers and Latin letters. {% endincluded %} {% included (../_includes/popup/id-popup/name.md) %} The name of this specific branch. Written in standard capitalization, with no quotation marks, all-caps formatting, or special characters. Must match the chain name exactly as it appears on the website, with no branch-specific additions. Branch-specific additions belong in the `name-other` element only. Correct: _Chamomile_ Incorrect: _Chamomile on Lenin Street_ {% endincluded %} {% included (../_includes/popup/id-popup/shortname.md) %} Short name of the branch to be displayed next to placemarks on Yango Maps, up to 25 characters. Specified without quotation marks, case-sensitive. {% endincluded %} {% included (../_includes/popup/id-popup/name-other.md) %} A descriptive label that distinguishes the branch from others (for example, "Additional office 1"), or an alternative name for the branch. Use a separate element for each name. Specified without quotation marks, case-sensitive. The language attribute is required: ``. {% endincluded %} {% included (../_includes/popup/id-popup/address.md) %} The full address of the branch — region, city, street, and building number (exceptions: villages, gas stations, highway-side businesses, and buildings not found in Yango Maps). If the branch doesn't have a complete address, you may provide a partial address, but it must not conflict with the coordinates specified in the file. Entered on a single line. Correct: `London, Baker Street, 72B` Incorrect: `London, Baker Street` If the element contains only the street name and house number, use the `locality‑name` element specifying the locality. The address must not include extraneous information such as floor numbers, office numbers, or landmarks. {% endincluded %} {% included (../_includes/popup/id-popup/country.md) %} Country. Specified in full, without abbreviations. {% endincluded %} {% included (../_includes/popup/id-popup/address-add.md) %} Additional address information that doesn't apply to other elements (shopping center/shopping and entertainment complex/shopping and entertainment center, floor, office, premises, boutique, entrance). For example, `Roze shopping center, floor 2, office 203`. Landmark descriptions and turn-by-turn directions are not permitted (for example, "100 meters north of the subway station," "blue building to the right of Trafalgar Square"). Don't use brackets or quotation marks. {% endincluded %} {% included (../_includes/popup/id-popup/phone.md) %} The organization's phone number. (if there are multiple numbers, specify each in a separate element). Compound element. Contains required elements. ```xml 0800 123-45-67 phone ``` {% endincluded %} {% included (../_includes/popup/id-popup/number.md) %} The landline or mobile phone number. The format is `[country code]` (`[city code]`) `[phone number]`. {% endincluded %} {% included (../_includes/popup/id-popup/ext.md) %} Extension, without comments, words, or delimiters. {% endincluded %} {% included (../_includes/popup/id-popup/info.md) %} Information about the phone number, such as "director" or "reception". This element shouldn't contain information about the phone type. {% endincluded %} {% included (../_includes/popup/id-popup/type.md) %} Phone type. Acceptable values: - `phone`: Phone number. - `fax`: Fax number. - `phone‑fax`: Phone/fax number. {% endincluded %} {% included (../_includes/popup/id-popup/email.md) %} Email address (if there are multiple addresses, specify each one in a separate element). {% endincluded %} {% included (../_includes/popup/id-popup/url.md) %} The chain's main website URL (without social media pages). Specified in lowercase, in full, including `http://` or `https://`. To add social media links, use the `add-url` attribute. Individual branches may specify their own regional website. URLs must not contain UTM parameters. {% endincluded %} {% included (../_includes/popup/id-popup/add-url.md) %} Additional website of the chain (such as links to social media pages). The URL of the page with branch information on the chain website is specified in the `info‑page` element. {% endincluded %} {% included (../_includes/popup/id-popup/info-page.md) %} URL of the page with branch information on the chain website. The address must contain the domain name of the chain website. Specified in lowercase, in full, including http:// or https://. {% endincluded %} {% included (../_includes/popup/id-popup/working-time.md) %} Opening hours. Days off and non-working days aren't specified. General business hours (without separate hours for individual departments). {% cut "Example" %} ```xml daily 11:30-21:30 break 14:00-14:30, break 16:30-17:00 ``` {% endcut %} If the business observes holidays, a separate `scheduled-working-time` element with exact dates is required. {% endincluded %} {% included (../_includes/popup/id-popup/scheduled-working-time.md) %} Holiday hours. {% endincluded %} {% included (../_includes/popup/id-popup/rubric-id.md) %} [The ID of the business category](https://doc-static.yandex.net/src/support/business-priority/en/rubrics_en.xlsx) to which this branch belongs. Each branch requires between one and three categories, at least one of which must match the chain's category. When a branch belongs to more than one category, list each in a separate element. {% endincluded %} {% included (../_includes/popup/id-popup/actualization-date.md) %} Date updated. Corresponds to the time of the last update. Used to avoid downloading information received during the previous check. The content can be specified in the following format: - `DD.MM.YYYY`; - [UNIX-time](https://en.wikipedia.org/wiki/Unix_time) — specified in milliseconds from `00:00:00.000 01.01.1970`. {% endincluded %} {% included (../_includes/popup/id-popup/coordinates.md) %} Country. Specified in full, without abbreviations. Each file may contain only one country. For additional countries, create separate chains and update them with separate files. {% endincluded %} {% included (../_includes/popup/id-popup/lon.md) %} Longitude. Use the dot as the decimal separator. Coordinates must not conflict with the address. A mismatch between the address and coordinates is only permitted when address data is unavailable in Yango Maps. Coordinates must be placed on the building in Yango Maps. If the building isn't on Yango Maps, coordinates that don't fall on it are permitted. {% endincluded %} {% included (../_includes/popup/id-popup/lat.md) %} Latitude. Use the dot as the decimal separator. Coordinates must not conflict with the address. A mismatch between the address and coordinates is only permitted when address data is unavailable in Yango Maps. Coordinates must be placed on the building in Yango Maps. If the building isn't on Yango Maps, coordinates that don't fall on it are permitted. {% endincluded %} {% included (../_includes/popup/id-popup/photos.md) %} A link to the gallery or a page on the chain site with all photos. If there are multiple photos, each one is in a separate `photo` element. It can contain the following attributes: - `alt`: Text description of the photo in free form. - `type`: Photo type. Can take a single value: `interior`. {% endincluded %} {% included (../_includes/popup/id-popup/tag.md) %} Photo tag. Set inside the `photos` element. Acceptable values: - `INTERIOR`: Interior. - `EXTERIOR`: Exterior. - `ENTER`: Entrance. - `LOGO`: Logo. - `FOOD`: Food, drinks. - `GOODS`: Goods. - `MENU`: Cafe or restaurant menu. - `ACCESSIBILITY`: Ramps, lifts for people with disabilities, and more. - `DEVICES`: Electronic devices. - `SERVICES`: Services. {% endincluded %} {% included (../_includes/popup/id-popup/feature-boolean.md) %} Branch property. If there are multiple properties, each one is specified in a separate element. Acceptable values: - `0: No.` - `1: Yes.` {% endincluded %} {% included (../_includes/popup/id-popup/feature-enum-single.md) %} Branch property. {% endincluded %} {% included (../_includes/popup/id-popup/feature-enum-multiple.md) %} Branch property. If there are multiple properties, each one is specified in a separate element. {% endincluded %} {% included (../_includes/popup/id-popup/feature-numeric-single.md) %} A branch property with a numeric value. {% endincluded %} {% included (../_includes/popup/id-popup/feature-numeric-multiple.md) %} A branch property with a numeric value. If there are multiple properties, each one is specified in a separate element. {% endincluded %} {% included (../_includes/popup/id-popup/feature-in-units-single.md) %} A branch property whose value is defined in units. {% endincluded %} {% included (../_includes/popup/id-popup/feature-in-units-multiple.md) %} A branch property whose value is defined in units. If there are multiple properties, each one is specified in a separate element. {% endincluded %} {% included (../_includes/popup/id-popup/feature-range-single.md) %} A branch property that has a range value. {% endincluded %} {% included (../_includes/popup/id-popup/feature-range-in-units-single.md) %} A branch property that has a range value in units. {% endincluded %} {% included (../_includes/popup/id-popup/feature-range-in-units-multiple.md) %} A branch property that has a range value in units. If there are multiple properties, each one is specified in a separate element. {% endincluded %} {% included (../_includes/popup/id-popup/feature-text-single.md) %} A branch property in text format. {% endincluded %}