04 – Cartography configurations with custom fields

An important feature of our Map Viewer is the ability to configure the way buildings & POIs are shown. This is achieved by using special custom-fields for each of them.

Please note! In addition to the configurations explained here, you may internationalize buildings, floors, POIs and POI categories as explained here.

Building custom fields #

You may configure building custom fields as explained here. The following table summarizes the most important you may use.

KeyValueExampleDescription
geojson_map_urlURL where the GeoJSON map is hosted. Value is empty by default (no GeoJSON shown).geojson_map_url = https://dashboard.situm.com/floorplan.geojsonThe Map Viewer downloads and displays the GeoJSON map from the URL
has_tilestrue, falsehas_tiles=trueIndicates whether the venue floorplans are available as high-resolution tiles. This is needed so that the MapViewer shows them. If not present, the value is assumed to be false and tiles are not shown.
poiCategoryOrdertext
poiCategoryOrder=code1, code2, code3
If this custom-field is not present, the order of the POI categories in the POI category filter menu will be alphabetical. Otherwise, it will be ordered based on the specific order of the POI category codes inputed.

POI custom fields #

You may configure POI custom fields as explained here. The following table summarizes the most important you may use.

KeyValueExampleDescription
priorityPriority level from 1 (max priority) to 10 (min priority). Value is 10 by default (lowest priority)priority = 3The POI priority is used for two different purposes:

1. Clustering view : If the POI is too close to other POIs, the Map Viewer shows only some of them to avoid cluttering the view. Those with the highest priority will have a higher chance to be shown.

2. Semantic indications: If in navigation mode the route crosses the coverage area of a POI, the corresponding instruction will include information about that POI. (only for priority = 1) link
top_leveltrue or false. Value is false by default (any value other than true will be false)top_level = trueIf the POI is too close to other POIs, the Map Viewer shows only some of them to avoid cluttering the view. Those with this custom-field set to true will never be hidden.
surnameString“Gentleman” might be a surname to show for a POI on the Gentleman side of a fashion storeAllows to show a specific subtitle or surname for each POI. This is the default language fallback.
surname_lngStringCaballero (spanish translation of “Gentleman”)Allows to shown a specific subtitle for each POI, on a specific language (lng), following this convention. E.g. surname_es will be the subtitle for spanish.
max_zoomDecimal number between 1 (lowest zoom) and 23 (highest zoom)18.2Experimental feature

POI will disappear after a certain zoom level. E.g. in the example if you zoom higher than 18.2 the POI will dissapear
min_zoomDecimal number between 1 (lowest zoom) and 23 (highest zoom)18.2Experimental feature

POI will never appear before a certain zoom level. After that zoom level, POI will appear as long as clustering algorithm allows it. E.g. in the example if you zoom higher than 18.2 the POI will appear at some point, provided that there are no higher priority POIs too close.
hideCombination of the following values in a list: on_map, on_search, on_map_icon, on_map_texthide = on_map, on_searchThis configuration allows precise control over a Point of Interest (POI)’s visibility on a map and in search results. Key settings include:

on_map: Hides the POI on the map.
– on_search: Hides the POI in search results.
– on_map_icon: Hides the POI’s map icon.
– on_map_text: Hides the POI’s label (name) on the map.

You can also combine values, e.g., “hide=on_map, on_search” hides POIs on the map and in search results.

Exception: If set to “on_map” or a combo of “on_map_icon” and “on_map_text,” the POI will still appear on the map when selected, serving as a route endpoint, or as a fixed point of interest.
indication_typeString (floor)
indication_type = floorSpecify how the user should make transitions between floors.

To add extra information in the floor transition indications, it’s necessary to include the following custom field in the POIs that indicate a transition between floors, such as an elevator or escalator. link


(Example of Indication: if we have a POI scalator the indication can be as following: “Change floor 1 using scalator“).
indication_radiusDecimal value (distance in meters)indication_raidius = 5.5Distance from the POI to the route to add the POI information in indications.

The added information in the indications varies depending on the proximity of the POI to the route using the value previously defined. link

(Example of Indication: if we have a POI information the indication can be as following: “Turn left and go ahead for 17 m to Information“).

NOTE: There is the possibility of configuring a global distance for all POIs.

POI categories custom fields #

You may also configure POI categories custom fields. The following table summarizes the most important you may use.

KeyValueExampleDescription
hideCombination of the following values in a list: on_map, on_search, on_map_icon, on_map_texthide = on_map, on_searchControls specific POI category visibility on the map and in search results. Visibility settings are independent for each category, such that they don’t propagate from parent to subcategories. Key settings include:

– on_map: Hides all POIs within the specified category on the map.
– on_search: Hides all POIs within the specified category in search results.
– on_map_icon: Hides icons associated with all POIs within the specified category on the map.
– on_map_text: Hides labels (names) of all POIs within the specified category on the map.

You can also combine values, e.g., “hide=on_map, on_search” hides POIs on the map and in search results.

Exception: If set to “on_map” or a combination of “on_map_icon” and “on_map_text,” POIs in the designated category will still appear on the map when selected, serving as a route endpoint, or as a fixed point of interest.

Subscribe to our newsletter

BASIC INFORMATION ON DATA PROTECTION

Data controller: SITUM TECHNOLOGIES, S.L.
Contact: Data controller: situm@situm.es
Responsible for protection: dpo@situm.es
Purpose and legal basis: To manage the sending of SITUM newsletters only with consent.
Legitimation: Express consent of the interested party.
Recipients: The data will not be passed on to third parties with the exception of legal obligations.
Retention period: As long as the interested party remains subscribed to the newsletter (a link to unsubscribe will be available in each newsletter sent by Situm).
Rights: The interested party may at any time revoke their consent, as well as exercise their rights of opposition, access, conservation, rectification, limitation, deletion of data and not be subject to a decision based only on automated data processing, by writing to SITUM at the addresses indicated.
Additional Information: You can consult additional and detailed information on Data Protection in our privacy policy.

Please, download your copy here

Thank you for downloading our whitepaper. Please do not hesitate to contact us if you would like to know more about how our solutions can help your business. Download whitepaper


Close window