Skip to content

Spatial Data Types

Backendless database supports the following spatial data types:

  • POINT - represents a single point/location in coordinate space. For the points representing locations on a map, the coordinates are longitude and latitude.
  • LINESTRING - represents a geometry consisting of a collection of points with linear interpolation between them. For example, a linestring can represent a delivery route.
  • POLYGON - a closed geometrical shape consisting of a single exterior boundary and zero or more interior boundaries, also referred to as holes.

Additionally, Backendless supports a "parent" data type called GEOMETRY. This is the base type which can accommodate any of the data types listed above.

database-geo-types.zoom50

Spatial data in Backendless can be represented either in the WKT (Well-Known Text) or the GeoJSON formats. Backendless console supports both of these formats for entering new data or updating existing spatial values. Additionally, Backendless SDKs provide built-in classes which make it easier to work with the spatial data for all database operations, including creating, retrieving, updating and deleting spatial data.

POINT

The POINT type is used to represent a single point identified by two coordinates in a coordinates space. The coordinates are named X and Y, however, Backendless also handles these coordinates as longitude (X) and latitude (Y) to represent locations on a map. The WKT representation of this type is:

POINT (longitude latitude)

or

POINT (x y)

for example, the POINT below points to Dallas, TX

POINT (-96.7553535 32.8656106)

The GeoJSON format for the POINT values is:

{  
  "type": "Point",  
  "coordinates": [  
    longitude or X,  
    latitude or Y  
  ]  
}

Consider the following example. The objects shown below contain two geometry columns/properties of the POINT type: pickupLocation and dropoffLocation.

sample-data-geo

The following request retrieves the first object from the table. Notice the structure of the response, specifically the values of the pickupLocation and the dropoffLocation properties:

cURL  Request:

curl -X GET 'https://api.backendless.com/APP-ID/REST-API-KEY/data/Order/first'

Response body:

{  
  "created": 1575913699597,  
  "updated": 1575915440119,  
  "objectId": "37C8A348-9B7B-80C0-FF24-5A86D905A300",  
  "orderName": "Salads ToGo",  
  "ownerId": null,  
  "___class": "Order",  
  "dropoffLocation": {  
    "type": "Point",  
    "coordinates": [  
       -81.23534874,  
       40.76793927  
    ],  
    "srsId": 4326,  
    "___class": "com.backendless.persistence.Point"  
  },  
  "pickupLocation": {  
    "type": "Point",  
    "coordinates": [  
      -112.04832225,  
      39.6943831  
    ],  
    "srsId": 4326,  
    "___class": "com.backendless.persistence.Point"  
  }  
}

LINESTRING

The LINESTRING type is used to represent geometries composed of multiple POINT values with linear interpolation between each two consecutive points. The WKT representation of this type is:

LINESTRING (lon1 lat1, lon2 lat2, lon3 lat3, lon4 lat4)

or

LINESTRING (x1 y1, x2 y2, x3 y3, x4 y4)

for example, the LINESTRING below identifies the main stops of the historic Route 66:

LINESTRING (-87.52683788 41.85716752, -90.13875858 38.68967135, -95.93953983 36.2131248, -97.49959842 35.53656483, -101.8282117 35.26791494, -105.87118045 35.72083154, -106.61825076 35.14794417, -111.63900272 35.20182535, -118.24178592 34.07195769)

The GeoJSON format for the LINESTRING values is:

{  
  "type": "LineString",  
  "coordinates": [  
    [  
      lon1 or x1,  
      lat1 or y1  
    ],  
    [  
      lon2 or x2,  
      lat2 or x2  
    ],  
    [  
      lon3 or x3,  
      lat3 or y3  
    ],  
    [  
      lon4 or x4,  
      lat4 or y4  
    ]  
  ]  
}

Consider the following example. The Travel table has an object identifying a travel route. The route column is of the LINESTRING type, its value is visualized in the map in the screenshot below:

linestring-example.zoom85

The following request retrieves the object from the Travel table. Notice the structure of the response, specifically the value of the route property:

cURL  Request:

curl -X GET 'https://api.backendless.com/APP-ID/REST-API-KEY/data/Travel/first'

Response body:

{  
  "created": 1574828569764,  
  "name": "Route 66",  
  "updated": 1574828575008,  
  "objectId": "BC0EC35B-0E01-F2A7-FF77-D3A630CD3100",  
  "ownerId": null,  
  "___class": "Travel",  
  "route": {  
    "type": "LineString",  
    "coordinates": [  
      [ -90.13875858, 38.68967135 ],  
      [ -95.93953983, 36.2131248 ],  
      [ -97.49959842, 35.53656483 ],  
      [ -101.8282117, 35.26791494 ],  
      [ -105.87118045, 35.72083154 ],  
      [ -106.61825076, 35.14794417 ],  
      [ -111.63900272, 35.20182535 ],  
      [ -118.24178592, 34.07195769 ]   
    ],  
    "srsId": 4326,  
    "___class": "com.backendless.persistence.LineString"  
  }  
}

POLYGON

Value of the POLYGON type is a figure that is described by a number of LINESTRING values connected to form a single continuous exterior boundary. Additionally, a Polygon may  contain zero or more interior boundaries, where each interior boundary defines a hole in the Polygon. The WKT representation of this type is:

POLYGON ((lon1 lat1, lon2 lat2, lon3 lat3),  
         (hole-lon1 hole-lat1, hole-lon2 hole-lat2, hole-lon3 hole-lat3),  
         (...),(...))

or

POLYGON ((x1 y1, x2 y2, x3 y3),  
         (hole-x1 hole-y1, hole-x2 hole-y2, hole-x3 hole-y3),  
         (...),(...))

where the first group of coordinates defines the exterior boundary and all subsequent groups defines the holes. The first group is mandatory.

for example, the POLYGON below identifies the outline of The Pentagon - the US Department of Defense headquarters. It also includes a hole - which is the inner plaza.

POLYGON ((-77.05781934 38.87248788,   
          -77.05474017 38.87287211,   
          -77.0533025 38.8706001,   
          -77.05556629 38.86883758,   
          -77.05848453 38.87002374,   
          -77.05781934 38.87248788),   
         (-77.05669282 38.87156906,   
          -77.05551265 38.87170271,   
          -77.05494402 38.8708507,   
          -77.05577014 38.87030775,   
          -77.05688594 38.87074211,   
          -77.05669282 38.87156906))

The GeoJSON format for the POLYGON values is:

{  
  "type": "Polygon",  
  "coordinates": [  
    [  
      [  
        lon1,  
        lat1  
      ],  
      [  
        lon2,  
        lat2  
      ],  
      [  
        lon3,  
        lat3  
      ]  
    ],  
    [  
      [  
        hole-lon1,  
        hole-lat1  
      ],  
      [  
        hole-lon2,  
        hole-lat2  
      ],  
      [  
        hole-lon3,  
        hole-lat3  
      ]  
    ]  
  ]  
}

Consider the following example. The Building table has an object identifying a shape of a building. The shape column is of the POLYGOON type, its value is visualized in the map in the screenshot below:

pentagon-example.zoom80

The following request retrieves the object from the Building table. Notice the structure of the response, specifically the value of the shape property:

cURL  Request:

curl -X GET 'https://api.backendless.com/APP-ID/REST-API-KEY/data/Travel/first'

Response body:

{  
"created": 1578647319762,  
"name": "Pentagon",  
"updated": 1578647324081,  
"objectId": "2BC67B66-D6E7-04FE-FFAC-1C0B6ADEDF00",  
"ownerId": null,  
"___class": "Building",  
"shape": {  
"type": "Polygon",  
"coordinates": [  
[  
[  
-77.05781934,  
38.87248788  
],  
[  
-77.05474017,  
38.87287211  
],  
[  
-77.0533025,  
38.8706001  
],  
[  
-77.05556629,  
38.86883758  
],  
[  
-77.05848453,  
38.87002374  
],  
[  
-77.05781934,  
38.87248788  
]  
],  
[  
[  
-77.05669282,  
38.87156906  
],  
[  
-77.05551265,  
38.87170271  
],  
[  
-77.05494402,  
38.8708507  
],  
[  
-77.05577014,  
38.87030775  
],  
[  
-77.05688594,  
38.87074211  
],  
[  
-77.05669282,  
38.87156906  
]  
]  
],  
"srsId": 4326,  
"___class": "com.backendless.persistence.Polygon"  
}  
}