ISRImplementation status: BidirectionalInput supportedOutput supported

STANAG 4607: ground moving target indication, translated both ways

STANAG 4607, published as AEDP-4607, is the NATO format for ground moving target indicator data. SynapseCommand publishes a bidirectional adapter implemented field by field against Edition A Version 1, including everything its seven amendments overturned.

About the standard

What STANAG 4607 is

A GMTI packet carries dwell segments, each holding target reports produced by a moving platform's radar as it looks at the ground. It describes movement detected in a patch of terrain during a dwell, together with the platform's own position and the mission that produced the data.

The format explicitly places error detection, encryption and physical transmission outside itself, and its implementation guide places sequence numbering, loss detection and channelisation in a multiplexing layer that is also outside the format. There are no start or end of message characters.

That boundary is the reason the adapter takes exactly one packet. There is no socket, no reassembly buffer, no sequence number window and no cache of previous packets, because the standard instructs a reader that those belong elsewhere.

Operational relevance

Why this matters to a commander

GMTI answers a question no static picture can: what is moving, where, and in which direction, across an area far larger than an imaging sensor can cover at once.

For indications and warning, patterns of vehicular movement are often the earliest observable signal of intent, and they arrive long before identification is possible.

For a decision-support layer the honesty of the mapping matters more than its breadth. A GMTI report is a detection, and treating a sequence of detections as a track is a claim about association that the data itself does not make.

What is implemented

The exact behaviour, not a capability claim

The adapter implements 212 fields, held in machine readable form alongside the written row set, and a test asserts that the two agree in both directions. A field that nobody has made a decision about fails the build rather than being quietly absent.

No target track is ever emitted. The format carries no identifier for a real target anywhere in its core segments: the report index is defined as a count within a dwell and is conditional besides, the dwell index may be reused across segments by the standard's own guide, and it wraps. Associating reports across dwells is what a GMTI tracker does, and the guide sends the reader to the sensor vendor for the rule, so a translator may not invent one.

Each target report therefore becomes one Entity and one detection Event, with a key that ends in positional ordinals whose fragility is stated on the object rather than hidden.

The platform is the one real identity in the format, because each nation is made responsible for its own platforms being uniquely identified. The platform gets the only Track, and each of its samples records which segment it came from and what kind of instant that segment's time actually is, since one is the temporal centre of a dwell and the other is the moment a report was prepared.

The exercise indicator never sets the deployment level synthetic flag, in either direction, agreement included. A simulated indicator against a real declaration is a refusal, a real indicator against a synthetic declaration is a refusal, and the mixed value contradicts neither and is parked visibly.

Egress re-emits packets from the parsed values.

  • 01
    Edition
    AEDP-4607 Edition A Version 1, including the changes made by its seven amendments.
  • 02
    Direction in
    One GMTI packet, as bytes or as the parsed dictionary twin, to canonical objects.
  • 03
    Direction out
    Canonical objects back to a GMTI packet.
  • 04
    Objects produced
    One Entity and one detection Event per target report; one Track for the platform only.
  • 05
    Fields covered
    212, cross-checked between the written row set and the machine readable layout by a test.
Direction of exchange

Which way the data actually moves

Into the canonical model

  1. GMTI packet
    Mission, dwell and job segments with target reports.
  2. Entities, detection Events, platform Track
    No target track is produced, by design.

Out of the canonical model

  1. Canonical objects
    Objects for re-emission.
  2. GMTI packet
    Encoded from the parsed values.
Workflows

Where this data is used

Movement indications

Detections enter the canonical model and are correlated by the ISR Fusion Agent, where association is a recorded decision rather than a side effect of parsing.

Wide area monitoring

Dwell coverage and platform position together describe what was looked at and when, so a gap in reporting can be attributed to coverage rather than to absence of movement.

Exercise and live separation

A payload that declares itself simulated inside a feed declared real is refused rather than absorbed, which keeps exercise data out of a live decision record.

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 gmtif.

Source and fixtures

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

    212 fields, the no-target-track rule and the exercise indicator rules, documented at their sites.

  • Codec
    packages/cdm/synapse_cdm/adapters/gmtif_codec.py

    Packet and segment level decode and encode.

  • Fixtures
    packages/cdm/synapse_cdm/fixtures/gmti/

    Raw packets, parsed twins and golden canonical output.

Test evidence

  • Harness test
    tests/test_cdm_gmtif_adapter.py

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

  • Codec test
    tests/test_cdm_gmtif_codec.py

    Field layout agreement between the written row set and the machine readable layout.

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.

  • gmtif
    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 target tracks. Only the platform receives a Track, because only the platform has a genuine identifier in the format.
  • One packet at a time. Stream splitting, sequencing and loss detection are outside the format and outside this layer.
  • One tag related identifier that could have become a source identity is deferred rather than minted, because the field's meaning has moved across editions.
  • Declared gaps are recorded in the coverage document rather than resolved by assumption.

Security boundary

  • The adapter is a translator. It stores nothing, forwards nothing and holds no state between payloads.
  • No classification handling, no key material and no deployment configuration appear in the published layer.

Public sources

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

Questions

Frequently asked

Why does the adapter not produce tracks from GMTI reports?
Because the format carries no durable identifier for a target. The report index counts within a dwell, the dwell index may be repeated and wraps, and the standard's own implementation guide sends the reader to the sensor vendor for the association rule. Inventing one inside a translator would manufacture identity that the data does not contain.
Which edition is implemented?
AEDP-4607 Edition A Version 1, including the changes introduced by its seven amendments. Where the pinned document leaves a question open, the gap is recorded rather than closed.
Can SynapseCommand receive a live GMTI feed?
The published layer translates one packet at a time. Transport, sequencing and loss detection sit outside the format by the standard's own instruction, and therefore outside this contract. How a feed reaches the boundary is a deployment question.
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.