TAK and Maven Integration

How It Works

The Urban Sky SDK supplies live balloon telemetry. A small server-side adapter subscribes to SDK events, maps each update into the destination system's data model, and publishes it through the customer's approved TAK or Maven gateway.

Urban Sky → Urban Sky SDK → Customer adapter → TAK or Maven
                balloon:update       map + publish

The SDK connection and telemetry format stay the same for either destination. Only the final adapter changes.

Data Mapping

The balloon:update event includes the identifiers, position, altitude, and timestamp needed to represent a balloon track.

SDK field	TAK mapping	Maven mapping
balloonId + deviceId	Cursor-on-Target UID	Source or entity ID
lat + lng	CoT point	Observation geometry
altitude	CoT hae after datum validation	Elevation
timestamp	Event time and stale time	Observation time
missionId	Mission detail	Mission context
deviceType	Source detail	Platform or sensor metadata

The exact Maven schema and TAK transport are selected for the customer's environment. Urban Sky can provide that adapter as part of the integration.

Prepare SDK Events

The SDK provides the source event. The example below converts each device update into a neutral record that an approved TAK or Maven connector can use.

const response = await fetch('https://sdk.atmosys.com/runtime/js/current/loader.js')
eval(await response.text())

const sdk = await UrbanSkySDK.init({
  apiToken: process.env.URBAN_SKY_API_TOKEN,
})

sdk.on('balloon:update', update => {
  const tracks = update.devices.map(device => {
    return {
      balloonId: update.balloonId,
      missionId: update.missionId,
      deviceId: device.deviceId,
      deviceType: device.deviceType,
      latitude: device.lat,
      longitude: device.lng,
      altitudeMeters: device.altitude,
      observedAt: device.timestamp,
    }
  })

  // Pass `tracks` to the approved connector for this deployment.
})

For TAK, the connector can translate these records into Cursor-on-Target. For Maven, the connector maps them to the customer's approved ingestion contract. The connector and its credentials are configured separately from the Urban Sky SDK.

Deployment Checklist

• Run the adapter on a server; never expose SDK or destination credentials in a browser.
• Confirm the target schema, endpoint, transport, and authentication method.
• Confirm the altitude datum before mapping altitude into the destination format.
• Define update rate, stale-track behavior, retries, and duplicate handling.
• Validate data classification, releasability, and access controls.
• Test with non-operational data before connecting a live mission.

Integration scope

The SDK provides the source telemetry stream. TAK and Maven publishing requires a customer-specific adapter and authorized access to the destination system. Contact Urban Sky support to scope and validate the integration.

Next Steps

• Get an API token
• Review the telemetry format
• Use the JavaScript SDK
• Contact Urban Sky support