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 forceshostile- Hostile forcesneutral- Neutral entitiesunknown- 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)
string
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-dMedic-a-.-G-U-i-m-etfRecon-a-.-G-U-C-RLMG-a-.-G-E-W-RGrenadier-a-.-G-E-W-Zanti Tank-a-.-G-U-C-A-AAA-a-.-G-U-C-DEngineer-a-.-G-U-C-EMortar-a-.-G-E-W-O
Emergency Services
Vehicle-a-.-G-E-V-CAmbulance-a-.-G-E-V-mHospital-a-.-G-I-X-HPolice Station-a-.-G-I-i-lEmergency Station-a-.-G-I-i-eSAR-a-.-A-M-F-Q-HMedevac-a-.-G-U-C-V-R-E
Incidents
Incident-a-.-X-i-ofire-a-.-X-i-fearthquake-a-.-X-i-g-eavalanche-a-.-X-i-g-avehicle accident-a-.-X-i-t-v-a
Generic
Ground-a-.-G
How Values
Valid values for thehow parameter:
gps- GPS derivedhuman/retyped- Human enteredmachine- Machine generatedmensurated- Measured from imageryestimated- Estimated positionnonCoT/gigo- Non-CoT source