Air surveillanceImplementation status: BidirectionalInput supportedOutput supported

ASTERIX Category 062: system tracks, translated without being re-fused

Category 062 is the output of a surveillance data processing system: a system track built by correlating radar plots, Mode S interrogations, multilateration, ADS-B and ADS-C into one product. It is the only format in the open integration layer whose input is already the result of somebody else's fusion, and that single fact decides how the adapter behaves.

About the standard

What CAT062 is

A Category 062 record is a system track message. Beyond position and velocity it carries a large volume of metadata about the correlation that produced it: per-technology update ages, per-parameter ages, amalgamation and coasting flags, the tracker's own estimated standard deviations, contributing sensor lists, and a set of last measured values standing beside the calculated ones.

The category defines one message type. Unlike Category 034 there is no per-type expectation table, so the encoding rules live in the individual data items.

Position in this category is already geodetic, which removes the projection problem that Category 048 has to solve with an externally supplied sensor position.

Operational relevance

Why this matters to a commander

In most national and many coalition environments, the recognised air picture that reaches a command post has already passed through a data processing system. Category 062 is the format in which that picture is distributed.

For decision support the important property is provenance. A system track is an assertion made by a named upstream system, and treating it as ground truth erases the difference between what a sensor measured and what a tracker concluded.

Ingesting Category 062 alongside Category 048 and Category 021 lets a fused picture retain both the processed track and the reports it was built from, which is what makes a disagreement visible instead of averaged away.

What is implemented

The exact behaviour, not a capability claim

One record becomes one Entity and one Event. No canonical Track is emitted and no records are combined, because combining them would be a second fusion performed inside a translator.

The tracker's statements about its own processing are collected under a fusion provenance attribute so that a consumer can see whose opinion each one is.

The adapter does not arbitrate between the altitude items, does not resolve measured values against calculated ones, does not turn contributing sensor lists into joins, and does not convert the stated ages into instants. The tracker's own formula for doing so is recorded rather than applied, because an instant computed here would be indistinguishable in the output from one the source stated.

Identity is taken from the 24-bit Mode S address, filed under the same namespace the ADS-B, Category 021, Category 048 and STANAG 4676 adapters use, so the same airframe derives the same identifier without the adapters coordinating. The track number is never used as identity.

Times are counts since the previous midnight, so the date comes from an injected clock. There is no sensor position argument and no reference point argument, and one item that would require a projection is declined rather than resolved against an assumed one.

Egress re-emits from the parsed integers, so objects that came from Category 062 produce a byte exact block.

  • 01
    Direction in
    Category 062 data block, or its parsed dictionary equivalent, to one Entity and one Event per record in block order.
  • 02
    Direction out
    Objects that came from Category 062 to one byte exact data block.
  • 03
    Fusion metadata
    Carried as the upstream system's statement, under a named provenance attribute. Never applied, never re-decided.
  • 04
    Identity
    24-bit Mode S address, in the namespace shared with the other cooperative surveillance adapters. Track numbers are not identity.
  • 05
    Integrity gate
    Structural. No checksum exists in the category, so length, record tiling, defined field reference numbers, valid compound subfields, bounded extensions and non-zero repeat counts are the whole gate.
Direction of exchange

Which way the data actually moves

Into the canonical model

  1. CAT062 data block
    System track messages from a data processing system.
  2. Entity and Event
    One pair per record, with the tracker's provenance attached.

Out of the canonical model

  1. Canonical objects from CAT062
    Only objects this adapter produced.
  2. CAT062 data block
    Byte exact reconstruction.
Workflows

Where this data is used

Ingesting a national recognised air picture

System tracks arrive as canonical objects with their originating system named, so a coalition picture can distinguish a partner's processed track from a raw sensor report.

Preserving disagreement

Where the same airframe appears in a Category 062 track and a Category 048 report, both survive translation with their own provenance, and the fusion layer resolves them on the record rather than silently upstream.

Assurance replay

Because nothing is computed from the ages and nothing is combined, replaying an archived block reproduces the same canonical objects exactly.

Implementation evidence

Every claim above has a file behind it

These paths are in the public repository, published under Apache 2.0. The adapter module for this page is asterix_cat062.

Source and fixtures

  • Adapter source
    packages/cdm/synapse_cdm/adapters/asterix_cat062.py

    Both directions, with each declined inference argued at the site of the decision.

  • Wire codec
    packages/cdm/synapse_cdm/adapters/cat062_codec.py

    Item level decode and encode.

  • Fixtures
    packages/cdm/synapse_cdm/fixtures/cat062/

    Raw blocks, parsed twins and golden canonical output, including contributing sensor lists, composed track numbers and disagreeing altitudes.

  • Field by field coverage
    packages/cdm/synapse_cdm/FORMAT_COVERAGE.md

    The Category 062 row set.

Test evidence

  • Harness test
    tests/test_cdm_asterix_cat062_adapter.py

    Replayed by the validation harness shipped in the same package, which runs six checks per fixture including a never-drop lossless check.

  • Lossless check
    tests/test_cdm_lossless.py

    Ensures the tracker's parked statements are measured rather than exempted.

Manifest-backed assurance

Maturity is declared in each generated adapter manifest and checked against suite eligibility. VERIFIED is a separate claim-status axis. Neither means external certification or integration with a named system.

  • asterix_cat062
    Maturity L4Claim VERIFIED
What these maturity levels mean

L3 means required provenance survives translation. L4 adds applicable roundtrip evidence. L5 would require every applicable public conformance gate to pass. L6 requires an independent real implementation or system and cannot be awarded from this repository's synthetic fixtures.

Status and limits

What is claimed, and what is not

Implementation status: Bidirectional

The published adapter implements both translation directions: the format into the canonical data model, and the canonical data model back out to the format. Both directions are replayed by the validation harness against shipped fixtures.

Last reviewed against the published implementation on 2026-09-06.

Limitations

  • No canonical Track is produced from a Category 062 stream. One record is one observation.
  • None of the callsign shaped strings in the category are read as identity.
  • One item requiring an unstated projection is declined rather than resolved against an assumption.
  • This is one ASTERIX category and implies nothing about any other.

Security boundary

  • The published layer translates payloads and holds nothing. No track data, network configuration or system topology appears in the repository.
  • The adapter never reads the system wall clock, so archived payloads replay identically.

Public sources

Statements about what SynapseCommand® implements are drawn from the published repository rather than from these external sources.

Questions

Frequently asked

Does the adapter build tracks from Category 062?
No. Each record becomes one Entity and one Event. Category 062 is already a fused product, and combining its records would be a second, unaudited fusion performed inside a translator.
What happens to the tracker's update ages?
They are carried as stated, under a fusion provenance attribute. The specification gives a formula for turning them into instants, and the formula is recorded rather than applied, because a computed instant would be indistinguishable from one the source asserted.
Is the track number used as an identifier?
Never. Identity comes from the 24-bit Mode S address where the record carries one, in the same namespace the other cooperative surveillance adapters use.
Related

Where to go next

Related C2 environments

Command environments in the compatibility catalogue whose published characteristics reference this standard. Each page states the current SynapseCommand integration status for that system.