Skip to main content
The Geo Object API provides endpoints for managing geographical objects (markers, units, points of interest) on the tactical map.

Create Geo Object

Create a new geographical object and broadcast it to all clients.

Authentication

This endpoint requires HTTP Basic Authentication.

Request Body

string
required
Type of geographical object. See Geo Object Types for valid values.
string
required
Attitude/affiliation of the object:
  • friendly / friend - Friendly forces
  • hostile - Hostile forces
  • neutral - Neutral entities
  • unknown - Unknown affiliation
float
Latitude coordinate. Required if address is not provided.
float
Longitude coordinate. Required if address is not provided.
string
Address to geocode into coordinates. Alternative to providing latitude/longitude.
string
required
How the position was determined. See How Values for valid values.
string
Display name/callsign for the object
integer
required
Time in seconds until the object goes stale (0 for persistent)
string
Additional notes about the object
boolean
Whether to save this object for repeated broadcasting (default: false)
UID of another object to link to
float
Distance in meters to offset from base coordinates
float
Bearing in degrees for distance offset (default: 360)

Response

string
The UID of the created geo object

Response Example

Update Geo Object

Update an existing geographical object by UID.

Authentication

This endpoint requires HTTP Basic Authentication.

Request Body

Same as Create Geo Object, with the addition of:
string
required
The UID of the existing object to update

Response

Get Geo Objects

Query geographical objects within a specified radius.

Authentication

This endpoint requires HTTP Basic Authentication.

Query Parameters

float
required
Center latitude for search
float
required
Center longitude for search
integer
Search radius in meters (default: 100)
string
Filter by attitude: friendly, hostile, neutral, unknown, or * for all (default: *)

Response

Returns an array of geo objects within the specified radius.
array

Response Example

Get Repeated Messages

Retrieve all geo objects marked for repeated broadcasting.

Authentication

This endpoint requires HTTP Basic Authentication.

Response

object
Dictionary mapping UIDs to CoT XML messages

Response Example

Delete Repeated Messages

Remove geo objects from repeated broadcasting.

Authentication

This endpoint requires HTTP Basic Authentication.

Query Parameters

string
required
Comma-separated list of message UIDs to delete

Response

Geo Object Types

Common geo object types include:

Squad/Infantry Types

  • Sniper - a-.-G-U-C-I-d
  • Medic - a-.-G-U-i-m-etf
  • Recon - a-.-G-U-C-R
  • LMG - a-.-G-E-W-R
  • Grenadier - a-.-G-E-W-Z
  • anti Tank - a-.-G-U-C-A-A
  • AA - a-.-G-U-C-D
  • Engineer - a-.-G-U-C-E
  • Mortar - a-.-G-E-W-O

Emergency Services

  • Vehicle - a-.-G-E-V-C
  • Ambulance - a-.-G-E-V-m
  • Hospital - a-.-G-I-X-H
  • Police Station - a-.-G-I-i-l
  • Emergency Station - a-.-G-I-i-e
  • SAR - a-.-A-M-F-Q-H
  • Medevac - a-.-G-U-C-V-R-E

Incidents

  • Incident - a-.-X-i-o
  • fire - a-.-X-i-f
  • earthquake - a-.-X-i-g-e
  • avalanche - a-.-X-i-g-a
  • vehicle accident - a-.-X-i-t-v-a

Generic

  • Ground - a-.-G

How Values

Valid values for the how parameter:
  • gps - GPS derived
  • human / retyped - Human entered
  • machine - Machine generated
  • mensurated - Measured from imagery
  • estimated - Estimated position
  • nonCoT / gigo - Non-CoT source

Error Responses

Or for retrieval: