---
sourceDocument: Australia Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/service-management-for-the-enterprise

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Service Management

ft:clusterId :

    - sm4e

bundleId :

    - sm4e

workflow :

    - Technology


---

# Level geometry file

# Level geometry file {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
The level geometry file contains all the geometry for a given level. Each file is one
map that can be rendered in the ServiceNow platform.
The file naming standard is:

* Name with the `id` of the level found in the community map file
* Must contain <kbd class="ph userinput">-geojson-geojson-level-geom-</kbd>

{#r_LevelFile__ul_lb2_phv_lv}For example, level 46475 is found in a file named <kbd class="ph userinput">map-23641-mv-1-ev-1-geojson-geojson-level-geom-46475-fv-2.json</kbd>  
The main component of the level file is an array of features, and looks like:

    {
                "geometry": {
                    "coordinates": [
                        [
                            [
                                -117.2057125,
                                32.8818922
                            ],
                            [
                                -117.2057223,
                                32.8819201
                            ],
                            [
                                -117.2057559,
                                32.8819117
                            ],
                            [
                                -117.205746,
                                32.8818838
                            ],
                            [
                                -117.2057125,
                                32.8818922
                            ]
                        ]
                    ],
                    "type": "Polygon"
                },
                "id": 13960404,
                "label_area": [
                    -117.20573465198783,
                    32.88190207162559,
                    2.9198852018440062,
                    2.9198852018440062,
                    1.2818771600723267
                ],
                "location": {
                    "coordinates": [
                        -117.2057347,
                        32.8819021
                    ],
                    "type": "Point"
                },
                "obj_type": "Geometry",
                "properties": {
                    "display_name": "Reef Shark",
                    "entities": [
                        1473100
                    ],
                    "facility": "room",
                    "int_address": "Room B1-132"
                },
                "type": "Feature"
            },

* The `geometry` object is the geoJSON representation of points that make up the object. For more information about the GeoJSON standard, see <http://geojson.org>.
* `Geometries` can be turned into fm_space records.
* The `id` is mapped to the external space id on the fm_space record.
* The `display_name` is the name of the space.
* The `type` is the most important property. In the example, the class is a `facility` and the type for that class is a `room`. When parsing, these values determine:
  * If an fm_space record is created for the geometry
  * If the fm_space has a subtype
  * If any default icons are assigned to a space
  * If any default colors are assigned to the map
  {#r_LevelFile__ul_bk1_dhv_lv}
{#r_LevelFile__ul_wzv_hgv_lv}
* **[Valid classes](https://servicenow-prod.fluidtopics.net/FXqYbMVpdI92td2CZ~5GFw)**   
  There are certain classes and class types that are valid for the level geometry file.