---
sourceDocument: Australia Field Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/field-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# GeoJSON format requirements for territory geographies

# GeoJSON format requirements for territory geographies {#ariaid-title1}

Release version: Australia  
Updated September 28, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of GeoJSON format requirements for territory geographies

This document outlines the specific GeoJSON format standards that territory geographies must adhere to within the ServiceNow platform.
These requirements ensure that geographic data is correctly structured, validated, and processed for territory management.
Show full answer Show less  

## Geography Types and Behavior

* **geojson (GeoJSON):** The default type where you provide the GeoJSON data directly, which must comply with the defined format rules.
* **composite (Composite Geography):** The system automatically generates GeoJSON by merging multiple referenced geographies into a single MultiPolygon. Circles are approximated as 64-point polygons before merging.
* **matchingattributes (Matching Attributes):** Uses ZIP code, city, state, or country attributes for matching instead of GeoJSON. GeoJSON validation is skipped for this type.

## Required Top-Level GeoJSON Structure

GeoJSON must be wrapped in a **FeatureCollection** with the following structure:

* The `type` must be **FeatureCollection** (case-sensitive).
* Include at least one **Feature** object in the `features` array.
* Each **Feature** must have:
  * `type`: "Feature"
  * A `geometry` object
  * A `properties` object

## Supported Geometry Types

Only the following GeoJSON geometry types are supported for territory geographies:

* **Polygon:** A single closed polygon defined by coordinate rings.
* **MultiPolygon:** Multiple separate polygon regions grouped together.
* **Point (circle):** A single point with a radius property (in meters) representing a circle. The radius must be specified in the `properties` object.

Unsupported GeoJSON geometry types include LineString, MultiLineString, MultiPoint, and GeometryCollection.

## Coordinate Rules

* Coordinates must be expressed as `[longitude, latitude]` pairs with exactly two numeric values.
* Longitude values range from -180 to 180.
* Latitude values range from -90 to 90.
* Each linear ring in Polygon or MultiPolygon geometries must contain at least four coordinate pairs.
* Rings must be closed by having the first and last coordinates identical.

## Multi-feature Constraints

* A `FeatureCollection` can contain multiple Polygon and MultiPolygon features.
* It can contain only one Point (circle) feature.
* A feature collection cannot mix circle and polygon features together.  
GeoJSON format requirements define the structure, geometry types, and coordinate rules that territory geographies must follow.

## Geography types {#geojson-format-requirements__section_geography_types}

The Geography Type field on the Territory Geography \[sn_tp_territory_geography\] table determines how the system uses GeoJSON.  
{#geojson-format-requirements__table_geography_types__entry__3}

| Value | Label | Behavior |
|-|-|-|
| `geojson` | GeoJSON | You provide the GeoJSON directly. This is the default geography type. |
| `composite` | Composite Geography | The system generates the GeoJSON automatically by merging multiple referenced geographies into a single MultiPolygon. Before merging, the system approximates each circle as a 64-point polygon. |
| `matching_attributes` | Matching Attributes | The territory uses ZIP code, city, state, or country attributes for matching instead of GeoJSON. The system skips GeoJSON validation for this geography type. |
[Table 1. Geography types]

{#geojson-format-requirements__table_geography_types}

When you select GeoJSON in the Geography Type field, make sure that the content of the GeoJSON field meets the requirements. This applies whether you import a
GeoJSON file or paste the GeoJSON directly.

## Required top-level structure {#geojson-format-requirements__section_required_top_level_structure}

GeoJSON must be wrapped in a FeatureCollection at the top level.

    {
      "type": "FeatureCollection",
      "features": [
        {
          "type": "Feature",
          "geometry": { ... },
          "properties": { }
        }
      ]
    }

* Set `type` to `FeatureCollection`. This value is case-sensitive.
* Include at least one Feature object in the `features` array.
* Give each Feature a `type` of `Feature`, a `geometry` object, and a `properties` object.
{#geojson-format-requirements__ul_required_top_level_structure}

## Supported geometry types {#geojson-format-requirements__section_supported_geometry_types}

Territory geographies support the Polygon, MultiPolygon, and Point (circle) geometry types.  
{#geojson-format-requirements__table_supported_geometry_types__entry__3}

| Geometry type | Description | Structure |
|-|-|-|
| Polygon | A single closed polygon shape. | { "type": "Polygon", "coordinates": [ [ [lng, lat], [lng, lat], [lng, lat], [lng, lat] ] ] } |
| MultiPolygon | Multiple separate polygon regions. | { "type": "MultiPolygon", "coordinates": [ [ [ [lng, lat], [lng, lat], [lng, lat], [lng, lat] ] ], [ [ [lng, lat], [lng, lat], [lng, lat], [lng, lat] ] ] ] } |
| Point (circle) | A center point with a radius in meters, which represents a circle. Add the `radius` property to the `properties` object. The radius must be a number in meters. | { "type": "Feature", "geometry": { "type": "Point", "coordinates": [lng, lat] }, "properties": { "radius": 5000 } } |
[Table 2. Supported geometry types]

{#geojson-format-requirements__table_supported_geometry_types}

## Unsupported GeoJSON types {#geojson-format-requirements__section_unsupported_geojson_types}

Territory geographies accept only the Polygon, MultiPolygon, and Point (circle) geometry types. The following standard GeoJSON geometry types aren't recognized:

* LineString
* MultiLineString
* MultiPoint
* GeometryCollection
{#geojson-format-requirements__ul_unsupported_geojson_types}

## Coordinate rules {#geojson-format-requirements__section_coordinate_rules}

* Enter each coordinate as `[longitude, latitude]`, with exactly two numeric values.
* Use a longitude value from -180 through 180.
* Use a latitude value from -90 through 90.
* Include at least four coordinate pairs in each linear ring of a Polygon or MultiPolygon.
* Close each ring by making the first and last coordinates identical.
{#geojson-format-requirements__ul_coordinate_rules}

## Multi-feature constraints {#geojson-format-requirements__section_multi_feature_constraints}

* A FeatureCollection can contain multiple Polygon and MultiPolygon features.
* A FeatureCollection can contain only one Point (circle) feature.
* A FeatureCollection can contain either a circle or polygons, not both.
{#geojson-format-requirements__ul_multi_feature_constraints}