NATO UNCLASSIFIED

(RELEASABLE FOR INTERNET TRANSMISSION)

STANAG No. 7023
Edition 2
Ratification Draft 3

NORTH ATLANTIC TREATY ORGANISATION

(NATO)

MILITARY AGENCY FOR STANDARDISATION

(MAS)

STANDARDISATION AGREEMENT
(STANAG)

SUBJECT: Air Reconnaissance Primary Imagery Data

Standard

Promulgated on

Chairman, MAS

NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

RECORD OF AMENDMENTS

No. Reference/date of Date Signature

amendment Entered

EXPLANATORY NOTES
AGREEMENT

1. This NATO Standardisation Agreement (STANAG) is promulgated by the

Chairman MAS under the authority vested in him by the NATO Military Committee.

2. No departure may be made from the agreement without consultation with the
Custodian. Nations may propose changes at any time to the Custodian where they
will be processed in the same manner as the original agreement.

3. Ratifying nations have agreed that national orders, manuals and instructions
implementing this STANAG will include a reference to the STANAG number for
purposes of identification.

DEFINITIONS

4. Ratification is “In NATO Standardisation, the fulfilment by which a member

nation formally accepts, with or without reservation, the content of a Standardisation
Agreement” (AAP-6).

5. Implementation is “In NATO Standardisation, the fulfilment by a member nation

of its obligations as specified in a Standardisation Agreement” (AAP-6).

6. Reservation is “In NATO Standardisation, the stated qualification by a member

nation that describes the part of a Standardisation Agreement that it will not
implement or will implement only with limitations” (AAP-6).

RATIFICATION, IMPLEMENTATION, AND RESERVATIONS

7. Page iii gives the details of ratification and implementation of this agreement. If
no details are shown it signifies that the nation has not yet notified the Custodian of its
intentions. Page iv (and subsequent) gives details of reservations and proprietary
rights that have been stated.

RATIFICATION AND IMPLEMENTATION DETAILS

STADE DE RATIFICATION ET DE MISE EN APPLICATION

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

i
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

N IMPLEMENTATION/MISE
NATIONAL NATIONAL
A EN APPLICATION
RATIFICATION IMPLEM-
T REFERENCE DE ENTING FORECAST ACTUAL DATE
I LA DOCUMENT DATE PREVUE DATE REELLE
O RATIFICATION NATIONAL DE N M A T AIR N M A T AIR
N NATIONALE MISE EN A E R E A E R E
APPLICATION V R M R V R M R
Y Y R Y Y R
E E
(1) (2) (3) (3) (3) (3) (3) (3)

BE

CA

DA

FR

GE

GR

IT

LU

NL

NO

PO

SP

TU

UK

US

• See reservations overleaf/Voir reservés au verso(4)

+ See comments overleaf/Voir commentaires au verso (5)
X Service(s) implementing/Armées mettant en application (7)
Releasable to NACC/PfP U Non Releasable U (8)
NATO EFFECTIVE DATE (6)
DATE ∋ ENTREE EN VIGUEUR OTAN

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

ii
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

EXPLANATORY NOTES ON RATIFICATION AND IMPLEMENTATION

DETAILS

(1) a. One ratifying reference is entered for each nation. All dates are to be
shown as follows: “of/du 23.3.81”.

b. If a nation has:

(1) Not signified its intentions regarding ratification of the STANAG or

an amendment thereto, the space is left blank.

(2) Decided not to ratify the STANAG, the words “NOT

RATIFYING/NE RATIFIE PAS’ is entered.

(2) List the national implementing document(s); this may be the STANAG itself or
an AP.

(3) When nations give a forecast date for their implementation, it is entered in the
forecast column (month and year only). Implementation dates are transferred
from the forecast to the actual date column when notified by a nation.

(4) Reservations are to be listed as stated by each nation.

(5) If a nation has indicated that it will not implement “NOT IMPLEMENTING/NE
MET PAS EN APPLICATION” is entered; where reasons are given they are
placed after the reservations under the heading “comments”.

(6) When a NED or forecast NED has been determined it is entered here.

(7) In the case of a covering STANAG with an NED, an “X” is inserted in the
implementation column showing the services implementing the AP.

(8) In the case of an Unclassified STANAG, nations have or have not authorised the
release of the STANAG to NACC/PfP Partners.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

iii
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

NATO STANDARDIZATION AGREEMENT

(STANAG)

AIR RECONNAISSANCE IMAGERY DATA ARCHITECTURE

Annexes:

A. Auxiliary Data & Encoding Tables

B. Data Definitions
C. Abbreviations and Glossary

Related Documents:

DIAM 57-5 DOD EXPLOITATION OF MULTI-SENSOR

IMAGERY
APP 8 ALLIED TACTICAL AIR MESSAGES
(FORMATTED AND STRUCTURED)
ATP-47 HANDBOOK FOR AIR RECONNAISSANCE
TASKING AND REPORTING
STANAG 3596 AR AIR RECONNAISSANCE REQUEST AND
REPORTING GUIDE
STANAG 3837 AA AIRCRAFT STORES ELECTRICAL
INTERCONNECTION SYSTEM
STANAG 4283 NAV SPECIFICATIONS AND FORMATS FOR
INTEROPERABILITY BETWEEN MARITIME
PATROL AIRCRAFT AND MARITIME AIR
OPERATIONS CENTERS
STANAG 7024 AR IMAGERY AIR RECONNAISSANCE TAPE
RECORDER STANDARD
STANAG 7085 AR INTEROPERABLE DATA LINKS FOR IMAGING
SYSTEMS
ANSI X34-1977 AMERICAN NATIONAL STANDARDS INSTITUTE
- AMERICAN STANDARD CODE FOR
INFORMATION INTERCHANGE (ASCII)

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

1
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Table of Contents

TABLE OF CONTENTS ......................................................................................................................................2

1 INTRODUCTION.........................................................................................................................................5

2 DATA STRUCTURE....................................................................................................................................8
2.1 FILES..........................................................................................................................................................8
2.1.1 SENSOR OUTPUT DATA FILES ...........................................................................................................8
2.1.2 A UXILIARY DATA FILES.....................................................................................................................9
2.2 FIELDS .......................................................................................................................................................9
2.3 HEADER.....................................................................................................................................................9
2.4 BYTE OFFSET ADDRESSING ...................................................................................................................10
3 DATA CONTENT...................................................................................................................................... 10
3.1 SENSOR DATA ........................................................................................................................................10
3.1.1 SENSOR IMAGE DATA.......................................................................................................................11
3.1.2 SENSOR M ODELLING DATA.............................................................................................................11
3.2 A UDIO DATA ..........................................................................................................................................12
3.3 A UXILIARY DATA ..................................................................................................................................12
4 LOGICAL DATA FORMAT ENCODING......................................................................................... 12
4.1 GENERAL ENCODING REQUIREMENTS................................................................................................12
4.1.1 TYPES OF DATA FILE FIELDS...........................................................................................................12
4.1.2 DATA FIELD DEFAULT VALUES......................................................................................................13
4.1.3 TIME FIELDS.......................................................................................................................................13
4.1.4 RESERVED FIELDS AND ENCODING SCHEMES...............................................................................13
4.2 LOGICAL DATA FORMAT TABLES .......................................................................................................13
4.2.1 HEADER TABLE .................................................................................................................................13
4.2.2 A UXILIARY DATA TABLES...............................................................................................................13
5 TRANSPORT ARCHITECTURE......................................................................................................... 14
5.1 TRANSPORT SCENARIO .........................................................................................................................14
5.2 TRANSPORT M EDIUM DATA STRUCTURES.........................................................................................14
5.2.1 A RECORD ..........................................................................................................................................14
5.2.2 PREAMBLE /POSTAMBLE ...................................................................................................................15
5.2.3 SEGMENTS..........................................................................................................................................18
6 DATA PACKETS ....................................................................................................................................... 19
6.1 SYNCHRONISATION FIELD ....................................................................................................................20
6.2 HEADER FIELD .......................................................................................................................................20
6.3 CRC CHECKS ..........................................................................................................................................20
6.4 DATA FIELD............................................................................................................................................21
7 SENSOR DATA .......................................................................................................................................... 21
7.1 SENSOR CHARACTERISATION MODELS ..............................................................................................21
7.2 COORDINATE SYSTEMS.........................................................................................................................21
7.2.1 OVERVIEW .........................................................................................................................................21
7.2.2 COLLECTION PLATFORM GLOBAL POSITION ................................................................................23
7.2.3 A IRCRAFT REFERENCE .....................................................................................................................26
7.2.4 GIMBALS.............................................................................................................................................27
7.2.5 SENSOR ...............................................................................................................................................29
7.2.6 SAMPLE LOOK VECTORS ..................................................................................................................30
7.3 TARGET M ARKING AND M ENSURATION ............................................................................................30
ANNEX A – AUXILIARY DATA AND ENCODING TABLES ............................................................ 35

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

2
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-1 SOURCE / DATA FILE A DDRESS STRUCTURE .....................................................................................35

A-2 HEADER TABLE......................................................................................................................................38
A-2.1 U SE OF DATA FILE NUMBER AND TIME TAG HEADER FIELDS...................................................41
A-2.2 HIERARCHY OF SYNC TYPES ...........................................................................................................42
A-3 A UXILIARY DATA TABLES ...................................................................................................................43
A-3.1 FORMAT TIME TAG DATA TABLE ...................................................................................................43
A-4 M ISSION DATA TABLES ........................................................................................................................44
A-4.1 GENERAL A DMINISTRATIVE REFERENCE DATA TABLE ..............................................................44
A-4.2 M ISSION SECURITY DATA TABLE ...................................................................................................45
A-4.3 A IR TASKING ORDER DATA TABLE ...............................................................................................46
A-4.4 COLLECTION PLATFORM IDENTIFICATION DATA TABLE............................................................47
A-4.5 REQUESTER DATA TABLE ................................................................................................................48
A-4.6 REQUESTER REMARKS DATA TABLE .............................................................................................50
A-5 TARGET DATA TABLES.........................................................................................................................51
A-5.1 GENERAL TARGET INFORMATION DATA TABLE ..........................................................................51
A-5.2 GENERAL TARGET LOCATION DATA TABLE ................................................................................55
A-5.3 GENERAL TARGET EEI DATA TABLE ............................................................................................56
A-5.4 GENERAL TARGET REMARKS DATA TABLE .................................................................................57
A-6 PLATFORM DATA TABLES ....................................................................................................................58
A-6.1 M INIMUM DYNAMIC PLATFORM DATA TABLE ............................................................................58
A-6.2 COMPREHENSIVE DYNAMIC PLATFORM DATA TABLE ...............................................................62
A-7 SEGMENT /EVENT DATA TABLES.........................................................................................................67
A-7.1 END OF RECORD M ARKER DATA TABLE .......................................................................................67
A-7.2 END OF SEGMENT M ARKER DATA TABLE ....................................................................................68
A-7.3 EVENT M ARKER DATA TABLE ........................................................................................................69
A-7.4 SEGMENT INDEX DATA TABLE .......................................................................................................71
A-7.5 EVENT INDEX DATA TABLE ............................................................................................................73
A-8 U SER DEFINED DATA TABLES .............................................................................................................75
A-9 SENSOR PARAMETRIC DATA TABLES .................................................................................................76
A-9.1 SENSOR IDENTIFICATION DATA TABLE .........................................................................................76
A-9.2 SENSOR DESCRIPTION DATA TABLE ..............................................................................................78
A-9.3 SENSOR CALIBRATION DATA TABLE .............................................................................................83
A-9.4 SENSOR OPERATING STATUS DATA TABLE ..................................................................................84
A-9.5 SENSOR POSITION DATA TABLE .....................................................................................................85
A-9.6 M INIMUM SENSOR ATTITUDE DATA TABLE.................................................................................86
A-9.7 COMPREHENSIVE SENSOR ATTITUDE DATA TABLE ....................................................................87
A-9.8 GIMBALS POSITION DATA TABLE ..................................................................................................89
A-9.9 M INIMUM GIMBALS ATTITUDE DATA TABLE ..............................................................................90
A-9.10 COMPREHENSIVE GIMBALS ATTITUDE DATA TABLE ..................................................................91
A-9.11 SENSOR INDEX DATA TABLE ..........................................................................................................93
A-9.12 SENSOR ELEMENT DATA TABLE .....................................................................................................95
A-9.13 SENSOR SAMPLE COORDINATE DESCRIPTION DATA TABLE ......................................................99
A-9.14 SENSOR SAMPLE TIMING DESCRIPTION DATA TABLE ..............................................................100
A-9.15 SENSOR GROUPING DATA TABLE .................................................................................................101
A-10 SENSOR COMPRESSION TABLES ........................................................................................................102
A-10.1 SENSOR COMPRESSION DATA TABLE ..........................................................................................102
A-10.2 JPEG COMPRESSION DATA TABLES ............................................................................................103
A-10.3 JPEG SENSOR QUANTISATION DATA TABLE .............................................................................107
A-10.4 JPEG SENSOR HUFFMAN DATA TABLE ......................................................................................110
A-11 SENSOR DATA TABLES .......................................................................................................................113
A-11.1 SENSOR DATA TABLE .....................................................................................................................114
A-11.2 SENSOR SAMPLE “X” COORDINATE DATA TABLE .....................................................................116
A-11.3 SENSOR SAMPLE “Y” COORDINATE DATA TABLE .....................................................................117
A-11.4 SENSOR SAMPLE “Z” COORDINATE DATA TABLE .....................................................................118
A-11.5 SENSOR SAMPLE TIMING DATA TABLE .......................................................................................119
ANNEX B – DATA DEFINITIONS .............................................................................................................121
B-1 REAL NUMBERS (RN)..........................................................................................................................121
B-1.1 DOUBLE FORMAT ............................................................................................................................121

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

3
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

B-2 UNITS.....................................................................................................................................................123
B-2.1 DEFINITION ......................................................................................................................................123
B-2.2 W ORLD GEODETIC SYSTEM (WGS-84 - SEE ISO 6709/1983) .................................................124
B-2.3 TRUE HEADING, XY COORDINATES, AND RADIANS.................................................................124
B-2.4 DATE TIME GROUP .........................................................................................................................124
B-2.4.1 DEFINITION ..................................................................................................................................124
B-2.5 ORDER OF DATA .............................................................................................................................125
B-2.5.1 BIG ENDIAN BYTE ORDER.........................................................................................................125
B-2.6 ASCII (ISO/IEC 10646-1)............................................................................................................125
ANNEX C – ABBREVIATIONS AND GLOSSARY...............................................................................127
C-1 A BBREVIATIONS...................................................................................................................................127
C-2 GLOSSARY.............................................................................................................................................129

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

4
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

1 Introduction

NATO STANAG 7023 establishes a standard data format and a

standard transport architecture for the transfer of
reconnaissance imagery and associated auxiliary data
between reconnaissance Collection Systems and
Exploitation Systems. NATO STANAG 7023 is not a
communications protocol nor is it a document that will
solve implementation issues concerning communications.
The design of any system for communications robustness
must be made in consideration with STANAGs 7024 and 7085.

Figure 1 illustrates where NATO STANAG 7023 fits into the

overall reconnaissance architecture.

For technical questions regarding this STANAG please

address them to:

DERA Malvern
St. Andrews Road
Malvern
Worcestershire
United Kingdom

Attention: Mr.A.P.Branton

tel.44-(0)1684-894358
fax.44-(0)1684-896490

Requester Collection

NATO
STANAG
7023

Exploitation
Communication Station

Figure 1 - The Reconnaissance Cycle

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

5
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

NATO STANAG 7023 works in conjunction with other NATO

STANAGS 7024, 7085 and 4545 to complete the interface
between the Collection System and the Exploitation
System.

The flow of information begins in the Collection System.

The information is formed into the STANAG 7023 format and
then it flows to lower levels of the interface where it
may be transmitted on a transport medium or saved on a
storage medium. When the information arrives at the
Exploitation System the reverse process occurs.

Recce Platform STANAG Exploitation Facility

7024
7023 Data 7024 7024 7023 Data
Recorder Recorder

STANAG 7023 Data

7085
7085 Data Link Data Link

STANAG
4545
(Exploited Data)

Figure 2 – The Interoperability STANAGs

The following list of top level design aims for NATO

STANAG 7023 establish a basis for the design:

• promote interoperability
• handle primary imagery
• handle mission/intelligence data
• work in real time
• minimise platform processing
• assume exploitation of imagery has no prior
knowledge of source
• image format does not handicap sensor performance
• digital and analogue versions
• layered/modular architecture
• end-to-end protocol
• self-describing sensor data format
• addressable data files
• multi-sensor/multispectral
• hardware independent
• expandable

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

6
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

NATO STANAG 7023 is a self-describing format. The

auxiliary data defines the format of the image data. This
enables NATO STANAG 7023 to handle any image from any
type of sensor. Figure 3 illustrates this concept.

Exploitation
Collection Platform
Station
(Source) (Destination)

Imagery Data Imagery Data

Format Defined By
Auxiliary Data

Auxiliary Data Auxiliary Data

Format Defined by NATO

STANAG 7023

NATO
STANAG
7023

Figure 3 – Self-describing Format

The remainder of this document will focus on the

following areas:

• Data Structure - section 2 describes the methodology

with which the data is formatted.

• Data Content – section 3 identifies and categorises

the reconnaissance data to be transported from a
Collection System to an Exploitation System. In
Annex A, reconnaissance data is divided into two
functional categories:

• sensor data - actual imagery collected from a

sensor,

• auxiliary data - information required by an image

analyst to derive intelligence information from
the imagery and the information required by the
Exploitation System to process the raw imagery
data into a form which is useable by the imagery
analyst.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

7
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

• Logical Data Format Encoding – section 4 defines the

general encoding requirements for the data fields
within the header and data files.

• Transport Architecture - section 5 defines the data

structures required for the movement of imagery and
auxiliary data across the transport media. This
section of STANAG 7023 establishes a standard data
format encoding for the transfer of reconnaissance
imagery and associated auxiliary data between
Collection Systems and Exploitation Systems.

• Data Packets – section 6 defines the structure of

the data packet to be put on the transport medium.

2 Data Structure

This section defines how sensor and auxiliary data are

organised at the source and destination.

2.1 Files

There are basically two general categories of data files:

Sensor Output Data Files and Auxiliary Data Files.
Associated with each file is a Header. The length of each
file is defined in the Header.

Data File Summary

Each Data File is uniquely addressed

Each Data File has an associated Header
Header contains information about the Data File
Source Address (1 Byte): (256 different Data
Sources)
Data File Address (4 Bytes): (4,294,967,296
different Data Files for each Data Source)
Equivalent to 240 different file types
Data Files are variable in size
Auxiliary Data File format defined by NATO STANAG
7023
Sensor Data File format defined by Auxiliary Data
Files

2.1.1 Sensor Output Data Files

Sensor Output Data Files may be of variable length up to

a maximum of $FFFF FFFF (4 bytes). The format of the

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

8
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Sensor Data Files is defined in the Auxiliary Data Files.

The system designer will determine the method by which
sensor data is organised in the data files.

2.1.2 Auxiliary Data Files

Auxiliary Data Files support the processing and

exploitation of imagery. The format of the Auxiliary Data
Files are defined by this document. They are variable in
length and defined by the Data File Size field in the
Header. Examples of Auxiliary Data Files are: Mission
Data Files, Platform Data Files, and Sensor Parametric
Data Files.

2.2 Fields

The field structures for the Auxiliary Data Files are

determined by this document. The field structure for
Sensor Data Files are described by the Auxiliary Data
Files. The fields making up a data file may be either
mandatory, conditional, or optional. A value must exist
in all mandatory fields. Conditional fields depend on
values of other fields. Use of optional fields is left to
the discretion of the system designer. If conditional or
optional fields are not specified, they will contain a
default value for their particular type (see 4.1.2).

2.3 Header

Field Field name No. of

No. bytes
1 Edition number 1
2 Flags 1
3 Segment number 1
4 Source address 1
5 Data file address 4
6 Data file size 4
7 Data file number 4
8 Time tag 8
9 Sync type 1
10 Reserved 5
11 Checksum 2

The Header precedes every data file and contains

significant information about the data file. The length
of each Header is fixed at 32 bytes. The use of the
Header is mandatory.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

9
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

The Edition number has been included in the Header to

ensure that ground replay facilities identify the edition
of STANAG 7023 to be decoded. It is the first byte after
the Sync to ensure it is decoded correctly, i.e. if in
subsequent Editions the Header changed the edition number
will still be able to be decoded.

The Source Address field identifies the source of data.

This is an 8-bit field, making it possible to multiplex
up to 256 simultaneous sources of information.

The next field is the Data File Address. This is a 4 byte

field, making it possible to have up to 4,294,967,296
file types for each information source. Several gaps have
been intentionally left to facilitate future growth.

2.4 Byte offset addressing

The addressing mechanism used is byte offset from the

start of the record.

3 Data Content

Sources of the data include the air data computer, the

inertial navigation unit, the mission computer, and the
sensor management system. The data can be divided into
two generic categories of data, sensor data and auxiliary
data.

7023 Information
Sensor Data Auxiliary Data
Imagery Format
Mission
Platform
Sensor Parametric

7023 Data Sources

Sensor Data Auxiliary Data
Imaging Sensors Format Description Data - RMS
(64 Simultaneous) Target Data - Mission Computer
Platform Data - INS
Segment/Event Data - RMS
Sensor Parametric Data – RMS

3.1 Sensor Data

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

10
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Sensor data is imagery collected from reconnaissance

sensors classified by the type of data generated by the
sensor system (IR, EO, SAR). This standard characterises
sensors by how sensor data (at the interface to the
transport/storage interface) is mapped in the image
frame.

3.1.1 Sensor Image Data

The sensor image data can be in any form as long as the

sensor modelling data can process it. The sensor data can
be raw data directly out of the sensor or it can be data
that has been processed.

3.1.2 Sensor Modelling Data

There is a one-to-one correlation between the data in the

Sensor Modelling Data Files and the Image Data Files.
They are not necessarily the same size in bytes although
there is a one-to-one relationship between a pixel and a
coordinate component. The pixel size and the vector
component could be very different. Softcopy imaging
sensors used for mapping purposes shall be accompanied by
two-dimensional (2-D) one-to-one sensor mapping data. The
sensor modelling defaults to a standard sequential pixel
with equiangular separation across the field of view if
no modelling data is used. One method of defining a
sensor model is to use the "Two-Dimensional one-to-one
sensor Modelling Technique". The STANAG format is defined
to incorporate other future modelling approaches.

3.1.2.1 Two-Dimensional One-to-One Sensor Mapping Data

Provides the parameters to mathematically map the sensor

image to the projected object space. Describes sensor
sample ordering, mapping, and modelling parameters.
Sensor mapping data is tabular. The tables have the same
dimensions as the sensor image frame.

3.1.2.1.1 X, Y and Z Sample Coordinate Data

Provides look angle coordinates for each sample in a

frame. This enables processing equipment to map each
sample to the projected object space. The format of this
data is defined in the Sensor Sample Coordinate
Description Data Table.

3.1.2.1.2 Sample Timing Data

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

11
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Provides timing relationships between each sample in the

frame. The time is either the time elapsed since the
previous sample (differential) or the time at which the
sample was sampled on a running clock (cumulative). The
clock is reset periodically. The time at which the clock
is reset and the timing techniques are defined with this
data. The format of this data is defined in the Sensor
Sample Timing Description Data Table.

3.2 Audio Data

Allows the Pilot and or Reconnaissance Officer aboard the

collection platform to provide the interpreter on the
ground an audio narrative of events occurring during the
mission, e.g. identifying targets of opportunity. Not
supported within this Edition.

3.3 Auxiliary Data

Auxiliary data is divided into categories associated with

the source of the information. These categories are:
format description data, mission data, platform data,
event/index data, sensor parametric data.

4 Logical Data Format Encoding

This section defines general encoding requirements for

data fields within the header and data files. Logical
Data Format Encoding details the logical data
organisation and encoding requirements of the
reconnaissance data within the transport structures. This
format is designed to handle the numerous sensor types
and diverse sensor image formats currently in existence
and has reserved data areas for future systems.

4.1 General Encoding Requirements

4.1.1 Types of Data File Fields

Headers and auxiliary data files are composed of two

basic types of fields: encoded fields or immediate value
fields. The encoded value fields contain a value which
must be cross referenced to the appropriate lookup table
or decoded (e.g. Date Time Group) to determine the
information in that field. The immediate value fields
contain a value that can be read directly. There are
several methods of writing data into immediate value
fields, including schemes such as ASCII, Real Number (RN)
and Unsigned Binary.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

12
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

4.1.2 Data Field Default Values

Data Type Default (Null) Value

Real Number (RN) NaN
IEEE Double Format i.e. $FFFFFFFF FFFFFFFF
ASCII All characters set to $00
Date Time Group All bytes set to $00
Unsigned Binary All bytes set to $FF
(Immediate)
Unsigned Binary A valid encoding unit according to
(Encoded) the field

If there is no information to put in a field but it has

to be sent as a Mandatory requirement then a default
value shall be used in the field.

4.1.3 Time Fields

Throughout this format, time is assumed to be based on

Universal Time Coordinated (UTC), also known as Zulu
time.

4.1.4 Reserved Fields and Encoding Schemes

Fields and Encoding Schemes unused in the tables are to

be considered as “Reserved” for future use.

4.2 Logical Data Format Tables

The logical format of reconnaissance data contained in

the Header and Data Files is presented in Annex A in
tabular form. Data Tables specify the parameters of each
field contained in the Header or Data File.

4.2.1 Header Table

The logical data format of the data packet Header is

specified through the use of the Header Data Table.

4.2.2 Auxiliary Data Tables

The logical data format of each Auxiliary Data File is

presented via a data table. Located above the data table
is the Header Data File Address, which identifies each
data file. The tables contain descriptions of the fields
and encoding information.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

13
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

5 Transport Architecture

This section describes how sensor and auxiliary data will

be transported from the collection source to the
destination exploitation system.

5.1 Transport Scenario

Each data file in source memory is assembled with a

Header and sync pattern into a data packet. The data
packet is transported to the destination system. At the
destination system, the data packet is disassembled.

To add to the robustness of the data transfer, packets

can be re-sent. All re-sent packets shall have identical
header details.

5.2 Transport Medium Data Structures

Figure 5 illustrates the logical structure of data as it

resides on the transport medium.

Segment 0 Segment 1 Segment 2 Segment n

Segment

Packet 1 Packet 2 Packet 3 Packet m

Packet

Sync Header Data File

Figure 5 - Record / Segment / Packet Structure

5.2.1 A Record

A record is a collection of data packets, which are media

and system architecture independent, and which may
represent all or a portion of the data collected during

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

14
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

the course of a mission. This STANAG is concerned with

the contents and structure of a single record. Use of
multi-records is to be addressed in a future Edition.

The size of a record is the number of bytes contained in

the Sync, Header, and Data Files. It does not include any
filler bytes outside of the above three types of data
packets.

A record will contain a Preamble, one or more Data

Segments and optionally Postambles. Figure 6 is a
pictorial representation of a record (excluding the end
of record marker).

Preamble Image Postamble Image Postamble Image Postamble

Segment Segment Segment

Seg 0 Seg 1 Seg 2 Seg 3

Record

Figure 6 - A Record

5.2.2 Preamble/Postamble

5.2.2.1 Preamble

A 7023 preamble is a collection of 7023 packets received

(data link), or read from some medium (tape/disc etc.)
before the first data segment. The contents of the
preamble shall contain enough information for the
receiving ground station to interpret the contents of the
following data files/packets (the only proviso being the
hardware and software capability exists within the chosen
ground station).

For example one would expect to find the following

category of data files in the preamble:

Format Description Data Time Tag.

Sensor Parametric Data Information required to decode

the following sensor data.

Platform Data Aircraft Parameter description

data.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

15
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Mission Data Mission Details.

The preamble is produced prior to the reconnaissance

sortie and is not related in time to dynamic tables
generated during the sortie. For this reason the Time Tag
in the preamble is set to zero.

The default settings for the sensors, gimbals, etc are

defined in the tables in the preamble. During a data
segment these values may change but at the start of each
new segment they will take on the default values again.

Preamble data may be repeated in the postamble (with a

change of segment number and time tag). Should the
preamble be corrupted in any way, the repetition of
preamble information would enable imagery data to be
recovered. As the size of the preamble data is likely to
be minimal compared to the size of the sensor data this
repetition is considered to have minimal overhead for
transmission or recording.

5.2.2.2 Postamble

A 7023 postamble, if included in a record, is a

collection of 7023 packets received, or read from a
transport medium after a data segment. The contents of
the postamble shall contain enough information for the
receiving ground station to interpret the contents of the
preceding data files.

The use of the postamble is optional. It may be appended

to the preamble (for use with solid state recording
media) or it may be appended to the data segment(s).
Whichever mechanism of including a postamble is used it
must be maintained throughout the record. If a postamble
is generated and appended to a data segment then it must
be replicated and appended to each subsequent data
segment. The postamble segment number will take on the
value of the preceding data segment number (even if this
requires renumbering of the postamble segment number).

A postamble shall contain enough indexing data files to

define the position, type of targets, events and sensor
operating periods contained within the preceding data
segment.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

16
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

For example:

Sensor Index Used to interpret the operating periods

Data of the sensors e.g. to calculate
possible target coverage by the chosen
sensor.
Segment Index Used to define the position of the data
Data segment within the record.
Event Index Used to interpret the targets/events
Data contained within the preceding segment
of imagery data. e.g. target position
within the preceding data segment
(either on media or previously received
via data link).

Due to the minimal size of the preamble/postamble in

comparison to sensor data, it would be advisable to
send/record certain tables even though they have not
changed, e.g. Mission Data Tables.

A record containing postambles after the data segments

may have the format as:

Segment 0
Preamble files
End of segment marker
Segment 1
Data Files
Preamble files
Index tables for segment 1
End of segment marker
Segment 2
Data Files
Preamble files
Index tables for segment 1
Index tables for segment 2
End of segment marker
Segment 3
Data Files
Preamble files
Index tables for segment 1
Index tables for segment 2
Index tables for segment 3
End of segment marker
End of Record Marker

A record containing a postamble appended to the preamble

may have the format as:

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

17
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Segment 0
Preamble files
Index tables for segment 1
Index tables for segment 2
Index tables for segment 3
End of segment marker
Segment 1
Data Files
End of segment marker
Segment 2
Data Files
End of segment marker
Segment 3
Data Files
End of segment marker
End of Record Marker

5.2.3 Segments

Information recorded over the course of a mission is

divided into segments. There are no time gaps within a
segment.

The first segment is the preamble, which cannot contain

any dynamic data files.

Each subsequent segment may contain a mixture of sensor

and auxiliary information from each operating source.
Postamble files cannot contain any dynamic data files.

5.2.3.1 Segment numbering scheme

The preamble is always segment number 0. Postamble files

take on the same number as the previous data segment but
are identified in the Header by setting a flag.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

18
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Collection
Sources

Image Sensors Segment 1 Segment 2 Segment 3

1
2
3

Sensor
Parametric
Data
Platform
Data
Event
Data

Segment 1 Segment 2 Segment 3

Time

Figure 7 - Relationship of Segments to Events from

collection data sources

It is mandatory to generate certain tables at specific

points of activity within a segment.

Activity within a segment Mandatory Table

Change of sensor activation Sensor Description Data

Table

(i.e. if Field 9 changes)

Target Event Event Marker Data Table
End of Segment End of Segment Marker Data
Table

Indexing tables can only occur in the preamble and

postamble. Dynamic sensor related data tables can only
occur in the data segment.

6 Data Packets

A data packet is composed of three fields: the

synchronisation field, the header field, and the data
field. Each unique packet can be identified by an address
in its header field. The system designer must determine
how each individual transport system handles the
individual packets.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

19
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A Packet

Sync Header Data File

Sync - 10 Bytes
Header - 32 Bytes
Data File – 1 Byte to 4 GBytes

Figure 8 - Packet Composition

6.1 Synchronisation Field

The 10 byte synchronisation field contains the sync

pattern that identifies the beginning of each packet. The
serial synchronisation pattern shall be defined as the
following bit sequence. The hexadecimal transmission is:

SYNC HEADER DATA FILE

10 Bytes 32 Bytes 1 Byte to 4 GBytes
2 BYTES
Data File

Header
Length

CRC

CRC

$0D $79 $AB $21 $6F $34 $1A $72 $B9 $1C

The first byte to be transmitted shall be $0D and the

last byte shall be $1C in the above sequence.
6.2 Header Field

The Header describes the associated data file. The data

source and data file address fields are used together to
identify the type of data contained in the associated
data file. The 32 byte Header is identically structured
for each packet (sensor or auxiliary).

The Header section follows the synchronisation field

within each packet.

6.3 CRC checks

The CRC is mandatory for the Header and optional for the
Data File. A Flag in the Header will be set if the CRC is
used on the Data File. The CRC to be used is given below.

CRC-16 Polynomial: X 16 + X 15 + X2 +1.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

20
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Figure 9 – CRC for Header and Data File

6.4 Data Field

The data field contains the bulk of the information to be

transferred. The length of the data file is defined in
the header. The data field follows the header within each
packet. The data file length is inclusive of the CRC
bytes if used.

The transmission of data fields in a file is from left to

right or top to bottom as they are written in this
document.

7 Sensor Data

All Sensor Data Tables are defined on a per sensor basis.

A collection platform may define up to 64 sensors. Each
sensor is allocated a sensor ID in the range $00 to $3F.
The source address for a given sensor is generated from a
base address plus the sensors ID. The base address for
all parametric data is $40. When combined with the sensor
ID this forms a source address in the range $40 to $7F.

7.1 Sensor Characterisation Models

This type of data is descriptive of a specific sensor

type. Specific types of sensors (IR, EO) generate imagery
in different forms. As a result, different parameters are
required to describe the various forms of data generated
by these sensors (thermal IR responses, etc.).

This edition of STANAG 7023 provides modelling for 1-D

and 2-D passive one-to-one sensor models.

A one-to-one sensor model uniquely maps a single sample

to a single sensed position.

Other models will be supported by later versions of this

STANAG.

7.2 Coordinate Systems

7.2.1 Overview

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

21
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

There will be a logical progression of position and

attitude vectors, which will define the position, and
attitude of the collection platform sensor mounting and
the sensor itself.

All Position vectors are measured as x, y and z offsets

in metres from the origin of the preceding coordinate
system.

All Attitude vectors are measured in radians as rotations

about the z, y and x axis of the preceding coordinate
system.

This “chain” of vectors is defined as follows:

1. Aircraft Position Ap
Vector
2. Aircraft Attitude AA
Vector
3. Gimbals[0] Position GP0
Vector
4. Gimbals[0] Attitude GA0
Vector
5. Gimbals[1] Position GP1
Vector
6. Gimbals[1] Attitude GA1
Vector
7. ................... ....

8. Gimbals[n] Position GPn

Vector
9. Gimbals[n] Attitude Gan
Vector
10. Sensor Position SPn
Vector
11. Sensor Attitude San
Vector
12. Sensor Sample SSCxy
coordinates *

*The Sensor Sample Coordinates are given for a particular

(x, y) sample. These should be given as unit vectors. If
these are not given directly they should be calculated
when required from the Sensor Description Data. A typical
example of the above vectors for a single set of Gimbals
is shown below:

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

22
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Geometry
Aircraft
at t=1
Reference
Frame
Sensor
[a] Look Sensor
Vector Center
Aircraft Motion Sensor
of Optics Reference
S
Compensation Point
Frame
[s]
Gimbol Target
Position Vector
Vector T
G
Sensor
Gimbol Gimbol
Reference
Center Target
Aircraft Frame
Position [g] Earth Surface
Vector
A
Geodetic
Local Reference Target
Reference
Frame Location
Frame Vector
Local WGS-84 Geoid
Position L
Vector
E

Figure 10 - Vector diagram for Platform, Gimbals and

Sensor

7.2.2 Collection Platform Global Position

The global position of the collection Platform is given

by its latitude, longitude and height. The STANAG assumes
that this position is given for the platform motion
compensation point. In practice this may not be true.
Where the position is given for some other part of the
platform this will introduce small errors.

The accuracy of the position information will be

dependent on the navigation system employed. The majority
of navigation systems will be Inertial Navigation Systems
(INS). It is probable that the collection platform INS
will have some error associated with it, due to INS
drift. These systems may or may not be periodically

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

23
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

corrected using GPS. Dependent upon the GPS system

employed it may also have errors associated with it.

The platform height will normally be given by RADALT or

barometric pressure. The platform may also be capable of
determining its GPS height above the WGS-84 geodetic
datum. It is the responsibility of the collection
platform to supply the most accurate position and height
information that is available.

If the source of the height information is known the

relevant field should be used and the other fields set to
NaN. If the source is unknown all three fields should be
filled with the same data. If it is known that the source
is definitely not a particular source, the relevant field
should be filled with NaN.

The exploitation platform can make use of the type of

height field used within the table to improve its target
marking capabilities. GPS height will be assumed to be
referenced to the WGS-84 geodetic datum at the given
latitude and longitude. RADALT and barometric heights can
be assumed to be referenced to the terrain surface and
mean sea level at the given latitude and longitude. Using
maps that contain terrain information will allow the
calculation of the platform above the WGS-84 geodetic
datum.

Within STANAG 7023 there is no way to quantify any errors

within the INS, although the navigational confidence may
be indicated. The Dynamic Platform Data tables allow for
latitude, longitude, height above sea level, height above
the ground and GPS height. The exploitation platform will
have to take the values from the Dynamic Platform Data
Tables as accurate and valid for the motion compensation
point of the collection platform, while taking into
account the navigational confidence. It is possible for
the exploitation platform to determine error vectors for
latitude and longitude, via correlation of the targets
with appropriate map data.

In order to perform tasks such as target marking the

position and height of the aircraft may have to be
transformed from the global world coordinate system to a
local coordinate system.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

24
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Z
WGS-84 Geodetic V(y,z)
datum
Latitude

V Y

longitude
V(x,y)
X

Figure 11 - Global Coordinate System

The collection platform position vector Ap is described in

terms of the angle its Ap(x,y) projection it makes with
the Y-axis (longitude), the angle its Ap(y,z) projection
makes with the Y-axis (latitude) and the magnitude of the
vector. The magnitude of the vector gives the distance
from the centre of the geodetic datum. This can be
directly used to give height above the geodetic datum.
Local transforms can then be used to supply a local
coordinate system.

Aircraft reference
Coordinate System

Ap

Local Coordinate
system

Ground

MSL

WGS-84 datum

Figure 12 - Local Coordinate System

The height of the platform will usually be given as the

height above sea level or the height above ground. GPS
can give the height above the WGS-84 geodetic datum.

The position of the aircraft will be defined for the

point at which its latitude and longitude vector crosses
the height datum. The method used to obtain the platform

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

25
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

height will determine the origin of the local coordinate

system.

Dependent upon the sophistication of the exploitation

platform height may be referenced to a local terrain
datum which can be used to determine a more accurate
target location or the terrain may be considered flat.

7.2.3 Aircraft Reference

The Roll, Pitch, and Yaw of the aircraft is referenced to

the aircraft reference coordinate system. The aircraft
reference coordinate system is defined with its positive
x-axis along the track of the aircraft. The positive y-
axis along the starboard wing and the positive z-axis
vertically downwards along the line from the motion
compensation point of the aircraft to the NADIR. Such
that the artificial horizon defines a plane parallel to
the xy plane.

Right Side View

y z

Figure 13 - Aircraft Coordinate System

The parameters for Roll, Pitch, and Yaw are recorded in

the Dynamic platform data tables. The senses for Roll
Pitch and Yaw are defined below.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

26
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Yaw

X(+)

+ve

Y(+)

Roll
Pitch
+ve

+ve

Z(+)

Figure 14 - Sense for Roll, Pitch, and Yaw

7.2.4 Gimbals

The collection platform may or may not have gimbals.

Although platform models may model gimbals for a sensor

it is not mandatory to transmit gimbals tables for non
existent gimbals. If no gimbals position or attitude
tables are sent then the exploitation platform model
should assume a position vector of (0,0,0) and an
attitude vector of (0,0,0).

Because gimbals may not have coaxial axial centres of

rotation it may be necessary to define a single physical
gimbals with multiple gimbals tables. The STANAG allows
for up to 16 gimbals stages per sensor.

Each gimbals stage will consist of position vector and an

attitude vector.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

27
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Coordinate System defined

y' by previous stage
x'
x
y

z' Gimbals
Position
Vector

Gimbals attitude
vector defines new
z
coordinate system

Figure 15 - Gimbals Position and Attitude

The gimbals stages will form a chain of position and

attitude vectors. The first stage will have its origin at
the platform centre of motion, and be referenced to the
platform coordinate system. The last stage will describe
the position and attitude for the sensor mounting plate.

7.2.4.1 Gimbals Position Vectors

The gimbals position vector defines the offset of its

axis of rotation from the gimbals mounting point.
Dependent upon the type of gimbals being described it is
possible that this vector may vary during the STANAG 7023
record. Typically however this vector will be used to
describe the static or stationary offset of the centre of
the rotation of this gimbals stage with respect to the
previous stage’s coordinate system.

7.2.4.2 Gimbals Attitude

The gimbals attitude vector defines the rotation of

gimbals with respect to the previous stage’s coordinate
system. If the physical gimbals axes of rotation all
cross at a single point then a single gimbals attitude
vector can be used to describe the rotations possible
with the gimbals, as in case 1 below. If the gimbals are
not coaxial then multiple gimbals stages will be needed,
as in case 2 below.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

28
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Case 1 Case 2
Rotation
Rotation about Z’
about Z’

Rotation
Rotation about X’
about X’

Figure 16 - Single and multiple stage gimbals

Multiple gimbal stages can also be used to simplify

gimbals rotation at some arbitrary orientation. The first
gimbal stage is used to define an offset and rotation to
the arbitrary orientation. The second stage then defines
an offset of zero and a rotation about a single axis. The
first stage position, attitude and the second stage
position tables need only be written during the preamble.
The second stage attitude is then only written when it
changes. This will simplify the collection platform as no
calculations are required to report changes to the
gimbals attitude and the change can be written directly
as a single field in the second stage attitude table.

7.2.5 Sensor

It is possible for a collection platform to not transmit

any gimbals tables but to directly show the position and
attitude of the sensor with respect to the platform
centre of motion. If no gimbals positions or attitudes
are transmitted then these should be modelled as zero.
The sensor position and attitude are then effectively
referenced from the platform’s centre of motion.

The sensor has its own coordinate system. All sensors are
assumed to have the look vector along the x-axis.

Linescan sensors scan lines in the xy plane. Unless

otherwise stated by sensor modelling the scan is assumed
to be the (Line FOV/2) either side of the x-axis.
Frame scan sensors are assumed to scan lines as per
linescan sensors and frames in the z direction. Unless
otherwise stated by sensor modelling the scan is assumed
to be the (Frame FOV/2) either side of the x-axis.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

29
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

The actual scan direction +/- y and +/- z is defined in

the sensor description data table. Where y is in the high
frequency scanning direction and z is in the low
frequency scanning direction.

Figure 17 - Sensor Look vector

Where x’, y’ and z’ are the coordinate system defined by

a previous stage.

7.2.5.1 Sensor Position Vector

The sensor position vector describes the position of the

sensor’s centre of optics with respect to its mounting
origin.

7.2.5.2 Sensor Attitude

The sensor attitude vector describes the look vector of

the sensors optics. The rotation vector can be used to
apply a rotational offset to the sensor for scanning
directions other than +/- y for lines and +/- z for
frames.

7.2.6 Sample Look vectors

The Sample Look vector for a given sample can be obtained

either directly from sensor modelling data or indirectly
from the field of view and the number of pixels.

7.3 Target Marking and Mensuration

One of the requirements of reconnaissance imagery is to

be able to derive target coordinates from the imagery and
to make distance measurements on or from the imagery.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

30
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

This is sometimes difficult because imagery has several

types of distortions. NATO STANAG 7023 contains the
required information to characterise the distortions of
the imagery so the imagery interpreter can perform
mensuration and target locating from the reconnaissance
imagery.

• aircraft position (lat, long, and altitude)

• aircraft attitude (yaw, pitch, and roll)
• aircraft linear velocities (x, y, z)
• aircraft linear accelerations (x, y, z)
• aircraft angular rates (about x, y, z)
Target
• aircraft angular accelerations (about x, y, z) Transfer
Location
• sensor calibration data (temporal and geometric) Function
(x, y, z)
• sensor imagery (target vector)
• sensor gimbal angles
• sensor gimbal angular rates
• sensor gimbal angular accelerations
• position of sensor w.r.t gimbal
• position of gimbal w.r.t. motion compensation point

The model presented below is a first order model and does

not take first order and second order derivatives into
account.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

31
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

In order to perform target marking and mensuration it is

necessary to calculate the sample position vector (or
base vector) and look vector for a given sample. This
basically gives the position of the centre of optics and
a unit vector in the look direction of the sample. If the
image samples are transformed for display an inverse
transform will have to be applied to the display pixel
before performing the following calculation.

Unit sample
Sample base vector look vector
(the centre of optics)

Target

Terrain

Figure 18 - Base Vector and Sample Look Vector

Conceptually it is relatively simple to calculate the

position of the sensor centre of optics and its look
vector, from the platform, gimbals and sensor vectors
described above.

[ R] = [ Pp ] * [ PA ] * [G P0 ] * [G A0 ]*......[G Pn ]* [G An ] * [ S p ] * [S A ]

where:

R is the resultant transformation matrix.

Pp is the translation matrix for the platforms position.
PA is the rotational matrix for the platform. (Roll,
Pitch, Yaw).
GP0 is the translation matrix for the first stage gimbals
position.
GA0 is the rotational matrix for the first stage gimbals.
GPn is the translation matrix for the nth stage gimbals
position.
GAn is the rotational matrix for the nth stage gimbals.
Sp is the translation matrix for the Sensor’s position.
SA is the rotational matrix for the Sensor.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

32
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

This can then be used to determine the position of the

centre of optics by evaluating the resultant trans-
formation matrix for the Sensors centre of optics (0, 0,
0). This will result in a position vector Rp.

We then take the unit look vector for the sample in which
we are interested.

The unit vector for the sensor’s centre sample will be

(1, 0, 0).

The transformation matrix is then re-evaluated for the

unit look vector Rl, of the appropriate sample. The
required Resultant unit look vector is then given by (Rl
- Rp).

Sensor base Required unit

vector look vector

Transformed sample
look vector

Figure 19 - Calculation of Base and Sample Look Vectors

In practice the position of the platform is given in
latitude, longitude and height. This does not lend itself
to the above approach without some modification. Two
possible approaches are available:

1. Define a local coordinate system at ground level for

the aircraft’s lat and long. Then assume a flat
coordinate system referencing the platform at (0, 0,
height) relative to this coordinate system. Any
calculated target position would then be at the
aircraft latitude and longitude plus an offset to
the target.

2. Reference the aircraft location to the centre of the

earth. The aircraft height and the target height can

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

33
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

be calculated from the WGS-84 ellipsoid and local

terrain data. For this it is necessary to define a
world coordinate system and its relationship to
latitude, longitude and WGS-84.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

34
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Annex A – Auxiliary Data and Encoding Tables

The Tables in Annex A allow a collection system to transmit sufficient sensor data and auxiliary
data to enable an exploitation system to display and exploit imagery.

It is not necessary for collection systems to use the full set of STANAG 7023 Tables. The set of
Tables used by a collection system will be dependent upon the requirements of the platform and
sensor suite. The collection system must make no assumptions about the capability of the
exploitation system to receive and decode its data stream. If the data is required by the
exploitation system and it is available then the collection system should transmit it.

An exploitation system must have the capability to receive the full set of STANAG 7023 Tables.

A-1 Source / Data File Address Structure

Source File Source Data File Data File Annex

Address Address No.
(Hex) (Hex)
Format $00 Format Time Tag Data Table $0000 0001 A-3.1
Description
Data

Mission Data $10 General Administrative Reference Data Table $0000 0000 A-4.1
$10 Mission Security Data Table $0000 0010 A-4.2
$10 Air Tasking Order Data Table $0000 0020 A-4.3
$10 Collection Platform Identification Data $0000 0030 A-4.4
Table
$10 Requester Data Table $0000 0040 to A-4.5
$0000 005F
$10 Requester Remarks Data Table $0000 0060 to A-4.6
$0000 007F

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

35
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Source File Source Data File Data File Annex

Address Address No.
(Hex) (Hex)

Target Data $11 General Target Information Data Table $0000 0000 to A-5.1
$0000 0FF0
$11 General Target Location Data Table $0000 1000 to A-5.2
$0000 1FFF
$11 General Target EEI Data Table $0000 2000 to A-5.3
$0000 2FFF
$11 General Target Remarks Data Table $0000 3000 to A-5.4
$0000 3FFF

Platform Data $20 Minimum Dynamic Platform Data Table $0000 0000 A-6.1
$20 Comprehensive Dynamic Platform $0000 0001 A-6.2
Data Table

Segment/Event $30 End of Record Marker Data Table $0000 0000 A-7.1
Index Data
$30 End of Segment Marker Data Table $0000 0001 A-7.2
$30 Event Marker Data Table $0000 0002 A-7.3
$30 Segment Index Data Table $0000 0100 to A-7.4
$0000 FF00
$30 Event Index Data Table $0000 0101 to A-7.5
$0000 FFFF

User Defined $3F User Defined Data Table $0000 0000 to A-8
Data $0000 FFFF

Sensor $40 to $7F Sensor Identification Data Table $0000 0000 A-9.1
Parametric
Data
$40 to $7F Sensor Description Data Table $0000 0001 A-9.2

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

36
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Source File Source Data File Data File Annex

Address Address No.
(Hex) (Hex)
$40 to $7F Sensor Calibration Data Table $0000 0002 A-9.3
$40 to $7F Sensor Operating Status Data Table $0000 0006 A-9.4
$40 to $7F Sensor Position Data Table $0000 0010 A-9.5
$40 to $7F Minimum Sensor Attitude Data Table $0000 0020 A-9.6
$40 to $7F Comprehensive Sensor Attitude Data Table $0000 0030 A-9.7
$40 to $7F Gimbals Position Data Table $0000 0050 to A-9.8
$0000 005F
$40 to $7F Minimum Gimbals Attitude Data Table $0000 0060 to A-9.9
$0000 006F
$40 to $7F Comprehensive Gimbals Attitude Data Table $0000 0070 to A-9.10
$0000 007F
$40 to $7F Sensor Index Data Table $0000 0200 to A-9.11
$0000 02FF
$40 to $7F Sensor Element Data Table $0000 1000 A-9.12
$40 to $7F Sensor Sample Coordinate Description Data $0000 1010 A-9.13
Table
$40 to $7F Sensor Sample Timing Description Data Table $0000 1020 A-9.14
$40 Sensor Grouping Data Table $0000 0080 A-9.15
$40 to $7F Sensor Compression Data Table $0000 0100 A-10.1
$40 to $7F JPEG Sensor Quantisation Data Table $0000 0101 A-10.3
$40 to $7F JPEG Sensor Huffman Data Table $0000 0102 A-10.4

Sensor Data S80 to $BF Sensor Data Table $0000 0000 A-11.1
S80 to $BF Sensor Sample “x” Coordinate Data Table $0000 0010 A-11.2
S80 to $BF Sensor Sample “y” Coordinate Data Table $0000 0020 A-11.3
S80 to $BF Sensor Sample “z” Coordinate Data Table $0000 0030 A-11.4
S80 to $BF Sensor Sample Timing Data Table $0000 0050 A-11.5

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

37
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-2 Header Table

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Edition Number Mand 1 Immed Unsigned For example:
Binary $02 = Edition 2.
2 Flags Mand 1 Encode Unsigned Bit 0 = Unused.
Binary Bit 1 = Compression indicator.
Set to “1” when data is compressed.
Bit 2 = CRC indicator.
Set to “1” when the last two bytes
of the data file are used as a CRC
error correction code.
Bit 3 = Preamble and Postamble table
indicator.
Set to “1” for preamble and
postamble tables.
3 Segment Number Mand 1 Immed Unsigned For example:
Binary $01 = Segment number 1.
4 Source Address Mand 1 Encode Unsigned $00 = FORMAT DESCRIPTION DATA
Binary $10 = MISSION DATA
$11 = TARGET DATA
$20 = PLATFORM DATA
$30 = SEGMENT/EVENT INDEX DATA
$3F = USER DEFINED DATA
$40 to $7F = SENSOR PARAMETRIC DATA
$80 to $BF = SENSOR DATA
5 Data File Address Mand 4 Encode Unsigned See section A-1.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

38
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Binary
6 Data File Size Mand 4 Immed Unsigned The size of the Data File in bytes.
Binary Maximum value = $FFFF FFFF.
7 Data File Number Mand 4 Immed Unsigned This is a generation sequence number
Binary (not necessarily a transmission
sequence number) and acts as a
counter per source address within a
segment. The initial value for each
counter will be zero. The counter
values will be reset to zero at
segment boundaries. Counter values
will be allowed to wrap around
within segments.
8 Time Tag Mand 8 Immed Unsigned This is an incrementing counter that
Binary increases at a rate defined in the
Format Time Tag Data File. The
purpose of the Time Tag is to
preserve the relative time between
events that happen at the source.
The value of the Time Tag in the
Header is equal to the condition of
the Time Tag counter in the source
equipment at the time of the first
sample in the Data File.

For files in the Preamble the Time

Tag is set to zero. The Time Tag
counter increments from zero at the

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

39
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
start of segment number one.
9 Sync Type Mand 1 Encode Unsigned $00 = INACTIVE
Binary $01 = SUPER FRAME SYNC
$02 = FRAME SYNC
$04 = FIELD SYNC
$08 = SWATH SYNC
$0A = LINE SYNC
$0C = TILE SYNC
10 Reserved Mand 5
11 Checksum Mand 2 Encode Unsigned CRC-16
Binary Polynomial: X16 + X 15 + X 2 + 1

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

40
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-2.1 Use of Data File Number and Time Tag Header Fields

The Data File Number and Time Tag fields are combined to describe specific related data packets.
Their use and interpretation is described below.

Packet Source Data File Time Tag Remarks

No. Address Number

1 X 1 1 New Packet Type X

2 X 2 1 Overflow Packet for Packet No 1
3 X 3 1 Overflow Packet for Packet No 1
4 X 4 2 New Packet Type X
5 X 5 3 New Packet Type X
6 Y 1 3 New Packet Type Y
7 X 6 4 New Packet Type X
8 X 6 5 Invalid Packet
Different Time Tags and identical Data File Numbers are
not allowed.
9 X 7 6 New Packet Type X
10 X 7 6 Redundant Packet
(must contain an exact copy of Packet No 9)

Relationship between Data File Number and Time Tag

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

41
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-2.2 Hierarchy of Sync Types

SUPER FRAME

FRAME

FIELD

SWATH

TILE

LINE

A representation of the build up of a frame using swaths, tiles and lines is given in the
diagram following the Sensor Description Data Table (A-9.2).

The SUPER FRAME sync is the highest order sync used in this edition of the standard. Its use is
for systems that build up a larger picture from FRAMES.

The FIELD sync has a specialist use for interlaced systems.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

42
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-3 Auxiliary Data Tables

A-3.1 Format Time Tag Data Table

Source Type : Format Description Data

Source Address : $00
File Address : $0000 0001

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Time Tag Increments Mand 8 Immed RN Value of “Tick” in fractions of a
second or whole seconds; e.g. the RN
value could indicate microseconds or
milliseconds.

The SI unit of time is the second.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

43
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-4 Mission Data Tables

Mission data is provided for the imagery interpreter and can be transported with imagery data to
describe the tasking of the particular sortie being flown. It includes information normally
contained in a fragmentary order (FRAG), an abbreviated form of an “Operations (OPS) Order”
which is generally more specific and time sensitive.

A-4.1 General Administrative Reference Data Table

Source Type : Mission Data

Source Address : $10
File Address : $0000 0000

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Mission Number Mand 8 Immed ASCII Number assigned to the recce
mission.
2 Mission Start Time Mand 8 Encode DTG Mission date and time.
3 Project Identifier Opt 2 Encode ASCII Project identifier code assigned to
Code (PIC) the platform.
Encoding defined in DIAM 57-5.
4 Number of Targets Mand 1 Immed Unsigned Number of preplanned targets.
Binary Range of values: 0-255
5 Number of Mand 1 Immed Unsigned Number of units requesting reports.
Requesters Binary Range of values: 0-32
There can be no Requesters or up to
32 Requesters.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

44
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-4.2 Mission Security Data Table

Source Type : Mission Data

Source Address : $10
File Address : $0000 0010

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Mission Security Mand 64 Immed ASCII Security classification of the
Classification overall mission.
2 Date Opt 8 Encode DTG Effective date of security
classification guide.
3 Authority Opt 60 Immed ASCII Authority issuing the downgrade. The
security Classification Guide.
4 Downgrading Opt 1024 Immed ASCII Downgrading instructions.
Instructions

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

45
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-4.3 Air Tasking Order Data Table

Source Type : Mission Data

Source Address : $10
File Address : $0000 0020

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Air Tasking Order Mand 7 Immed ASCII Reference number - identifies the
Title ATO.
2 Air Tasking Order Mand 20 Immed ASCII Unit designator of ATO point of
Originator origin.
3 Air Tasking Order Opt 10 Immed ASCII Unique number which identifies the
Serial Number specific mission.
4 Date Time Group Opt 8 Encode DTG Date and Time the ATO originated.
5 Qualifier Opt 3 Immed ASCII Denotes a version of the basic ATO.
6 Qualifier Serial Opt 2 Immed Unsigned Starts at 1 for first qualifying
Number Binary message sent for basic ATO.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

46
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-4.4 Collection Platform Identification Data Table

Source Type : Mission Data

Source Address : $10
File Address : $0000 0030

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Squadron Opt 6 Immed ASCII Identifies squadron performing
reconnaissance mission.
2 Wing Opt 4 Immed ASCII Identifies the wing with which the
squadron is associated.
3 Aircraft Type Opt 16 Immed ASCII Type of aircraft used in the
mission.
4 Aircraft Tail Opt 6 Immed ASCII Tail number of aircraft used in the
Number mission.
5 Sortie Number Mand 2 Immed Unsigned A reference used to identify the
Binary images taken by all the sensors
during one air reconnaissance
sortie.
6 Pilot ID Opt 3 Immed ASCII Used to identify the pilot.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

47
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-4.5 Requester Data Table

Each requester is assigned a unique requester index number. STANAG 7023 can handle both
Information Requesters and Mission Requesters simultaneously. This table describes the Requester
and the required Report type, it also identifies the communications channels to be used.

Source Type : Mission Data

Source Address : $10
File Address Range : $0000 0040 to $0000 005F

File Addressing scheme is $0000 00xx where bits 0-4 represents the Requester Index Number as an
offset from $0000 0040.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Report Message Type Mand 1 Encode Unsigned Identifies type of report requested.
Binary $01 INFLIGHTREP
$02 RECCEXREP
$03 IPIR/SUPIR
$04 IPIR/SUPIR (ADP)
$05 RADARXREP
$06 RECCEXREP (ADP)
2 Message Mand 16 Immed ASCII Communications channel used for the
Communications transmission of alphanumeric
Channel messages.
3 Secondary Imagery Mand 16 Immed ASCII Communications channel used for the
Dissemination transmission of processed
Channel (annotated) imagery and imagery
derived products.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

48
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
4 LTOIV (Latest Time Mand 8 Encode DTG The latest time that the information
of Intelligence is of value. The time by which the
Value) intelligence is to be received by
the Requester.
5 Requester Serial Mand 6 Immed ASCII Reference number used to identify
Number the requesting agency or unit.
6 Mission Priority Mand 1 Encode Unsigned The priority of the mission to the
Binary individual requester.
$01 PRIORITY 1 (TOP PRIORITY)
$02 PRIORITY 2
$03 PRIORITY 3
7 Requester Address Mand 512 Immed ASCII Address of requester.
8 Requester Type Mand 1 Encode Unsigned Used to identify the type of
Binary Requester.
$01 MISSION REQUESTER
$02 INFORMATION REQUESTER
9 Operation Codeword Opt 48 Immed ASCII Codeword name.
10 Operation Plan Opt 48 Immed ASCII Operation plan details.
Originator & Number
11 Operation Option Opt 48 Immed ASCII Primary operation option name.
Name - Primary
12 Operation Option Opt 48 Immed ASCII Secondary operation option name.
Name - Secondary
13 Exercise Nickname Opt 48 Immed ASCII Nickname of exercise.
14 Message Additional Opt 48 Immed ASCII Additional information.
Identifier

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

49
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-4.6 Requester Remarks Data Table

The least significant bits of the file address are used to associate the requester remarks with
the appropriate requester.

Source Type : Mission Data

Source Address : $10
File Address Range : $0000 0060 to $0000 007F

File Addressing scheme is $0000 00xx where bits 0-4 represents the Requester Index Number as an
offset from $0000 0060.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Remarks Mand 1024 Immed ASCII Additional information provided by
the requester.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

50
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-5 Target Data Tables

A-5.1 General Target Information Data Table

Targets can be collected on any particular mission, or for any number of operations and for any
number of requesters. If the requester or the targets must be associated with a particular
operation then target and requester IDs will be used.

The Fields to be completed within the table will depend on the target type; line, area or point.

Source Type : Target Data

Source Address : $11
File Address Range : $0000 0000 to $0000 0FF0

File Addressing scheme is $0000 0xx0 where xx represents the target number.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Target Type Mand 1 Encode Unsigned Used to define the target type.
Binary $00 POINT
$01 LINE
$02 AREA
$04 STRIP
See definitions following this
table.
2 Target Priority Mand 1 Encode Unsigned The targets rank of importance or
Binary necessity.
$01 PRIORITY 1 (TOP PRIORITY)

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

51
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
$02 PRIORITY 2
$03 PRIORITY 3
3 Basic Encyclopaedia Opt 16 Immed ASCII Pre-established reference number
(BE) Number assigned to target.
4 Target Security Opt 64 Immed ASCII Security classification of the
Classification individual target.
5 Required Time on Opt 8 Encode DTG Time at which the reconnaissance
Target platform is located at the target
position.
6 Requested Sensor Opt 1 Encode Unsigned Indicates the requested type of
Type Binary imagery collected at this target.
$01 FRAMING
$02 LINESCAN
$03 PUSHBROOM
$04 PAN FRAME
$05 STEP FRAME
$10 SAR
$11 MTI
7 Requested Sensor Opt 1 Encode Unsigned Requested sensor response band.
Response Band Binary $01 VISUAL
$02 NEAR IR
$03 IR
$04 DUAL BAND
$10 MICROWAVE
$11 mm WAVE
8 Requested Opt 1 Encode Unsigned Collection technique for this
Collection Binary target.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

52
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Technique $01 VERTICAL
$02 FORWARD OBLIQUE
$03 RIGHT OBLIQUE
$04 LEFT OBLIQUE
$05 BEST POSSIBLE
9 Number of Locations Mand 1 Immed Unsigned Number of locations in the target
Binary type search.
10 Requester Address Mand 4 Encode Unsigned Used to identify Requester(s).
Index Binary LSB = Requester 0
MSB = Requester 31

The 32 bits have a one-to-one

mapping with the Requester Index
Number. If the bit is set then the
Requester(s) require Target
Information.

Bit 0 maps to $0000 0040

Bit 1 maps to $0000 0041
Bit 2 maps to $0000 0042
……………………………………………………………
Bit 31 maps to $0000 005F
11 Target Name Opt 32 Immed ASCII Target reference name.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

53
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Definition of target types [ATP-47(A)]:

Point: A point target is a precisely defined point location and should be expressed to an
accuracy of 100 metres. The planned sensor coverage should be not less than 100 metres
radius around the defined location.

Line: A line search is a section of a Line of Communication (LOC) and is identified by

precisely defined point locations for the start and end points, and by a description of
the LOC.

Area: Area searches are tasked by identifying the corners of the required area coverage.

Strip: A strip point is a straight line between 2 defined point locations.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

54
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-5.2 General Target Location Data Table

This file is used to determine the target location.

Source Type : Target Data

Source Address : $11
File Address Range : $0000 1000 to $0000 1FFF

File Addressing scheme is $0000 1xxy where xx represents the target number, and y the location
number.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Start, Target or Mand 8+8 Immed RN+RN Latitude and longitude of start
Corner Location location of the target.
2 Start, Target or Opt 8 Immed RN Elevation of start location of the
Corner Elevation target in metres.
3 Target Diameter or Opt 8 Immed RN Target diameter or width in metres.
Width
4 Map Series Opt 8 Immed ASCII Map series.
5 Sheet Number of Opt 14 Immed ASCII Map sheet number.
Target Location
6 Inverse Map Scale Opt 8 Immed RN eg.1:50,000 is RN = 50,000.
7 Map Edition Number Opt 1 Immed Unsigned Edition number of map.
Binary
8 Map Edition Date Opt 8 Encode DTG Date of map.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

55
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-5.3 General Target EEI Data Table

Source Type : Target Data

Source Address : $11
File Address Range : $0000 2000 to $0000 2FFF

File Addressing scheme is $0000 2xxy where xx represents the target number, and y the location
number.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Target Category/ Mand 32 Immed ASCII Critical items of information that
Essential Elements are to be answered regarding the
of Information specific target. The method in
which EEIs are described is defined
in the Point Target General
Information File.
2 EEI/Target Category Mand 1 Encode Unsigned Standard NATO Target definitions.
Designation Scheme Binary $01 NATO STANAG 3596
3 Weather Over the Opt 7 Encode ASCII Standard NATO Codes (TARWI).
Target Reporting See document ATP-47 for codes.
Code

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

56
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-5.4 General Target Remarks Data Table

Source Type : Target Data

Source Address : $11
File Address Range : $0000 3000 to $0000 3FFF

File Addressing scheme is $0000 3xxy where xx represents the target number, and y the location
number.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Remarks Mand 1024 Immed ASCII A free text remarks field referring
to the mission.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

57
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-6 Platform Data Tables

Platform data is provided for both the interpreter and exploitation processing equipment. This
data describes information about the collection platform on which the sensor suite is located.

Note:

• Only one Dynamic Data Table is required, i.e. Minimum or Comprehensive.

• The mission data file(s) can be repeated throughout the mission, and will not change within
the course of a mission. The rate of repetition is flexible - mission data file(s) may be
repeated as the mission varies (at each new target, change in FOV, etc.).

A-6.1 Minimum Dynamic Platform Data Table

Source Type : Platform Data

Source Address : $20
File Address : $0000 0000

Table Requirement : Conditional on the Comprehensive Dynamic Platform Data Table not sent

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Aircraft Time Mand 8 Encode DTG Time at which data was collected.
2 Aircraft Mand 8+8 Immed RN+RN The position of the platform given
Geo-Location as latitude and longitude in
radians.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

58
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
3 MSL Altitude Cond 8 Immed RN Altitude above mean sea level. A
value for height must appear in 1 or
more of fields 3, 4 or 5.
4 AGL Altitude Cond 8 Immed RN Altitude above ground level. A value
for height must appear in 1 or more
of fields 3, 4 or 5.
5 GPS Altitude Cond 8 Immed RN Altitude above the WGS-84 geodetic
datum. A value for height must
appear in 1 or more of fields 3, 4
or 5.
6 Aircraft true Cond 8 Immed RN Airspeed. This field is conditional
airspeed on field 7. One or other or both
must be sent.
7 Aircraft ground Cond 8 Immed RN Velocity over the ground. This field
speed is conditional on field 6. One or
other or both must be sent.
8 Aircraft true Cond 8 Immed RN Platform ground track angle relative
Course to true north . Aircraft heading
corrected for drift. Either field 12
or field 8 must be sent.
9 Aircraft true Mand 8 Immed RN Platform heading relative to true
Heading north.
10 Aircraft Pitch Mand 8 Immed RN Rotation about the y-axis
Nose up = +ve.
0.0 = Aircraft z-axis aligned to

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

59
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Nadir.
11 Aircraft Roll Mand 8 Immed RN Rotation about x-axis
Port wing up = +ve.
12 Aircraft Yaw Cond 8 Immed RN Angle of heading from track over
ground. Rotation about z-axis in the
xy plane Nose starboard to track =
+ve. Either field 12 or field 8 must
be sent.
13 Navigational Opt 3 Encode Unsigned The following 2-bit codes exist for
Confidence Binary all fields above 12 * 2 = 24bits =
3bytes.
$0 FAIL
$1 POSSIBLE FAILURE
$2 DE-RATED
$3 FULL SPECIFICATION

Order of Navigational Confidence 2-bit codes:

MSByte LSByte
F12 F11 F10 F9 F8 F7 F6 F5 F4 F3 F2 F1

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

60
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Where Fn is a 2-bit code for field number n, as defined above. E.g. F1 is a 2-bit code that
gives the navigational confidence of the field 1 the Aircraft Time, F2 is a 2-bit code which
gives the navigational confidence of the field 2 the Aircraft Geo-Location.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

61
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-6.2 Comprehensive Dynamic Platform Data Table

Source Type : Platform Data

Source Address : $20
File Address : $0000 0001

Table Requirement : Conditional on the Minimum Dynamic Platform Data Table not sent.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Aircraft Time Mand 8 Encode DTG Time at which data was collected.
2 Aircraft Mand 8+8 Immed RN+RN The position of the platform given
Geo-Location as latitude and longitude in
radians.
3 MSL Altitude Cond 8 Immed RN Altitude above mean sea level. A
value for height must appear in 1 or
more of fields 3, 4 or 5.
4 AGL Altitude Cond 8 Immed RN Altitude above ground level. A value
for height must appear in 1 or more
of fields 3, 4 or 5.
5 GPS Altitude Cond 8 Immed RN Altitude above the WGS-84 geodetic
datum. A value for height must
appear in 1 or more of fields 3, 4
or 5.
6 Aircraft true Cond 8 Immed RN Airspeed. This field is conditional
airspeed on field 7. One or other or both
must be sent.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

62
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
7 Aircraft ground Cond 8 Immed RN Velocity over the ground. This field
speed is conditional on field 6. One or
other or both must be sent.
8 Aircraft true Cond 8 Immed RN Platform ground track angle relative
Course to true north. Aircraft heading
corrected for drift. Either field 12
or field 8 must be sent.
9 Aircraft true Mand 8 Immed RN Platform heading relative to true
Heading north.
10 Aircraft Pitch Mand 8 Immed RN Rotation about the y-axis
Nose up = +ve.
0.0 = Aircraft z-axis aligned to
Nadir.
11 Aircraft Roll Mand 8 Immed RN Rotation about x-axis
Port wing up = +ve.
12 Aircraft Yaw Cond 8 Immed RN Angle of heading from track over
ground. Rotation about z-axis in the
xy plane Nose starboard to track =
+ve. Either field 12 or field 8 must
be sent.
13 Aircraft Velocity Opt 8 Immed RN The projection of the velocity
North vector on an earth stabilised North
vector. North is (+).
14 Aircraft Velocity Opt 8 Immed RN The projection of the velocity
East vector on an earth stabilised East

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

63
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
vector. East is (+).
15 Aircraft Velocity Opt 8 Immed RN The projection of the velocity
Down vector on a gravity vector. Rate of
change of aircraft altitude. Down is
(+).
16 Aircraft Opt 8 Immed RN The projection of the Acceleration
Acceleration North of aircraft on an earth stabilised
North vector.
17 Aircraft Opt 8 Immed RN The projection of the Acceleration
Acceleration East of aircraft on an earth stabilised
gravity vector.
18 Aircraft Opt 8 Immed RN The projection of the Acceleration
Acceleration Down of aircraft on an earth stabilised
North vector.
19 Aircraft Heading Opt 8 Immed RN Rate of change of aircraft true
Rate heading.
20 Aircraft Pitch Rate Opt 8 Immed RN Rate of change of aircraft true
Pitch angle.
21 Aircraft Roll Rate Opt 8 Immed RN Rate of change of aircraft true Roll
angle.
22 Aircraft Yaw Rate Opt 8 Immed RN Rate of change of aircraft true yaw
angle.
23 Aircraft Heading Opt 8 Immed RN Angular acceleration of aircraft
angular heading angle.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

64
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Acceleration
24 Aircraft Pitch Opt 8 Immed RN Angular acceleration of aircraft
angular Pitch angle.
Acceleration
25 Aircraft Roll Opt 8 Immed RN Angular acceleration of aircraft
angular Roll angle.
Acceleration
26 Aircraft Yaw Opt 8 Immed RN Angular acceleration of aircraft Yaw
angular angle.
Acceleration
27 V/H Opt 8 Immed RN The ratio of velocity to height.
Used to correct sensor geometry.
28 Navigational Opt 7 Encode Unsigned The following 2 bit codes exist for
Confidence Binary all fields above 27 * 2 = 54bits =
7bytes.
$0 FAIL
$1 POSSIBLE FAILURE
$2 DE-RATED
$3 FULL SPECIFICATION

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

65
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Order of Navigational Confidence 2-bit codes:

MSByte ----- LSByte

--
NU F27 F26 F25 F24 --- --- F5 F4 F3 F2 F1
--- ---
- -

Where Fn is a 2-bit code for field number n, as defined above. E.g. F1 is a 2-bit code that
gives the navigational confidence of the field 1 the Aircraft Time, F2 is a 2-bit code which
gives the navigational confidence of the field 2 the Aircraft Geo-Location.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

66
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-7 Segment/Event Data Tables

A-7.1 End of Record Marker Data Table

This table is to mark the end of a record. Its Header segment value will increment by one from
the previous End of Segment Marker (EOS) value. The exception to this rule is when the last EOS
Header segment number = $FF (the maximum permitted value) then the EOR Header segment value will
also take on the value $FF. In all situations this table will be considered independent of the
previous segment.

Segment EOS Segment EOS Segment EOS EOR

Repeat
0 0 1 1 for N N N+1
segment or or or
2 onwards $FF $FF $FF

Where EOS = End of Segment Marker Data Table, EOR = End of Record Marker Data Table.

Source Type : Segment/Event Data

Source Address : $30
File Address : $0000 0000
Table Requirement : MANDATORY

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Size of record Mand 8 Immed Unsigned The total number of bytes in the
Binary whole of the record including this
table.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

67
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-7.2 End of Segment Marker Data Table

This table is to mark the end of a segment. It is the last segment table to be generated for the
segment. The Time Tag value in the Header must be equal to or exceed the value for all previous
Time Tags generated for other segment data files.

Source Type : Segment/Event Data

Source Address : $30
File Address : $0000 0001
Table Requirement : MANDATORY

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Size of segment Mand 8 Immed Unsigned The total number of bytes in the
Binary whole of the segment including this
table.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

68
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-7.3 Event Marker Data Table

This table is used to mark the position of an event in the data segment.

Source Type : Segment/Event Data

Source Address : $30
File Address : $0000 0002
Table Requirement : CONDITIONAL on an event occurring.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Event Number Mand 1 Immed Unsigned Event number.
Binary
2 Event Type Mand 1 Encode Unsigned $00 Pre-programmed Point Event/Target
Binary $01 Pre-programmed Duration START
$02 Pre-programmed Duration END
$03 Manual Point Event/Target
$04 Manual Duration START
$05 Manual Duration END
$06 Recce Waypoint
3 Primary Sensor Mand 1 Immed Unsigned If there is only one sensor:
Number Binary Set fields 3, 4 and 5 to the
primary sensor number.
4 Secondary Sensor Opt 1 Immed Unsigned If there are two sensors:
Number Binary Set field 3 to the primary
number, and
Set fields 4 and 5 to the
secondary sensor number.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

69
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
5 Third Sensor Number Opt 1 Immed Unsigned If there are three sensors:
Binary Set field 3 to the primary
sensor number, and
Set field 4 to the secondary
sensor number, and
Set field 5 to the tertiary
sensor number.
6 Target number Opt 1 Immed Unsigned Target number ID.
Binary

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

70
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-7.4 Segment Index Data Table

Functions as a directory used to identify segments that occurred during a record on the
transport media. The indexing scheme utilising this data is based on the fact that the structure
consists of chronologically ordered data.

Source Type : Segment/Event Data

Source Address : $30
File Address Range : $0000 0100 to $0000 FF00

File Addressing scheme is $0000 xx00 where xx represents the segment number.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Start of data Mand 8 Immed Unsigned Number of bytes offset from start of
segment Binary record to start of data segment.
2 End of data segment Mand 8 Immed Unsigned Number of bytes offset from start of
Binary record to end of data segment.
3 Start time of Mand 8 Encode DTG Time imaging started in the data
recording segment defined by this segment
index.
4 Stop time of Mand 8 Encode DTG Time imaging ended in the data
recording segment defined by this segment
index.
5 Start of Header Mand 8 Immed Unsigned Value of the time tag in the first
Time Tag Binary header of the segment.
6 End of Header Time Mand 8 Immed Unsigned Value of the time tag in the last
Tag Binary header of the segment.
7 Aircraft location Mand 8+8 Immed RN+RN Platform latitude and longitude

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

71
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
at the start of location at segment start.
recording of the
segment
8 Aircraft location Mand 8+8 Immed RN+RN Platform latitude and longitude
at the end of location at segment end.
recording of the
segment

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

72
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-7.5 Event Index Data Table

The Event Index data structure keeps a chronological record of each event. The Event Index data
structure can be thought of as a table of contents for the entire record.

Source Type : Segment/Event Data

Source Address : $30
File Address Range : $0000 0101 to $0000 FFFF

File Addressing scheme is $0000 xxyy where xx represents the segment number, and yy the event
number. xx and yy have the range $01 to $FF.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Event Type Mand 1 Encode Unsigned $00 Pre-programmed Point Event/Target
Binary $01 Pre-programmed Duration START
$02 Pre-programmed Duration END
$03 Manual Point Event/Target
$04 Manual Duration START
$05 Manual Duration END
$06 Recce Waypoint
2 Target Number Cond 1 Immed Unsigned If event is imaging over a target
Binary then value = Target Number
If no target then value = $00
3 Target Sub-section Cond 1 Immed Unsigned If the event is not a Point Event
Binary then this is the associated leg or
corner number. If the event is a
Point Event the field value = $00.
4 Time Tag Mand 8 Immed Unsigned Time Tag in Header.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

73
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Binary
5 Event Time Opt 8 Encode DTG The time of the event in DTG format.
6 Aircraft Geo- Opt 8+8 Immed RN+RN Latitude and Longitude. Platform
Location location in radians.
7 Primary Sensor Mand 1 Immed Unsigned If there is only one sensor:
Number Binary Set fields 7, 8 and 9 to the
primary sensor number.
8 Secondary Sensor Opt 1 Immed Unsigned If there are two sensors:
Number Binary Set field 7 to the primary
number, and
Set fields 8 and 9 to the
secondary sensor number.
9 Third Sensor Number Opt 1 Immed Unsigned If there are three sensors:
Binary Set field 7 to the primary
sensor number, and
Set field 8 to the secondary
sensor number, and
Set field 9 to the tertiary
sensor number.
10 Event position in Mand 8 Immed Unsigned Number of bytes offset from start of
the record Binary record to start of event.
11 Event Name Opt 32 Immed ASCII Reference name of the event.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

74
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-8 User Defined Data Tables

A section of the address space has been reserved for user defined tables. The format and
contents of the tables are to be determined by the user. The User Defined Tables must not
contain any information necessary for the interpretation or exploitation of the data.

Non host exploitation systems should be aware that data in these tables will be irrelevant to
their system and should not be acted upon.

The use of these tables must follow all of the protocols of other STANAG 7023 tables, e.g. a
STANAG 7023 Sync and Header must precede the table.

Source Type : User Defined Data

Source Address : $3F
File Address Range : $0000 0000 to $0000 FFFF

File Addressing scheme is $0000 xxxx where xxxx is determined by the user.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

75
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9 Sensor Parametric Data Tables

Auxiliary parameters are used to describe the sensor data thereby allowing destination equipment
to decipher the sensor data and to produce a literal image. Sensor Parametric data is divided
into two general categories:

1) General sensor description data used to describe any sensor system regardless of the type of
sensor. General descriptive data such as sensor identification parameters and sensor data
compression information is included in this category.

2) Sensor specific description data.

A-9.1 Sensor Identification Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0000

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Sensor Type Mand 1 Encode Unsigned Classification indicative of the
Binary characteristics of the collection
device.
$00 INACTIVE
$01 FRAMING
$02 LINESCAN
$03 PUSHBROOM

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

76
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
$04 PAN FRAME
$05 STEP FRAME
$10 SAR
$11 MTI
2 Sensor Serial Opt 16 Immed ASCII Serial number of the sensor.
Number
3 Sensor Model Number Opt 16 Immed ASCII Model number of the sensor.
4 Sensor Modelling Mand 1 Encode Unsigned Defines the interpretation of the
Method Binary sensor data.
$00 BASIC SEQUENTIAL MODELLING
$01 VECTOR MODELLING
5 Number of Gimbals Mand 1 Immed Unsigned The number of gimbals defined for
Binary the sensor.
Range of values: 0 to 16.

If the Sensor Modelling Method is VECTOR MODELLING then the following tables are to be used:

Sensor sample “x” coordinate data table

Sensor sample “y” coordinate data table
Sensor sample “z” coordinate data table

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

77
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.2 Sensor Description Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0001

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Frame or Swath size Mand 4 Immed Unsigned The number of lines per frame or
Binary swath.
2 Line time Mand 8 Immed RN The duration of an active part of
the line in seconds.
3 Line size of active Mand 4 Immed Unsigned The number of samples per line of
data Binary significant data.
4 Packets per Frame Mand 4 Immed Unsigned The total number of packets
or Swath Binary transmitted for a complete Framing
Sensor Frame or Linescan Sensor
Swath. This will be a multiple of
the number of tiles per line, i.e.
the total number of tiles in a frame
or swath.
5 Size of tile in the Mand 4 Immed Unsigned The tile size in the high frequency
high frequency Binary scanning direction.
scanning direction
If no tile exists the size is taken
as the line size in Field 3.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

78
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Any padding of zeroes is always in
the maximum scan direction.
6 Size of tile in the Mand 4 Immed Unsigned The tile size in the low frequency
low frequency Binary scanning direction.
scanning direction
If no tiles exist the size is taken
as the frame or swath size in Field
1.

Any padding of zeroes is always in

the maximum scan direction.
7 Number of tiles per Mand 4 Immed Unsigned If no tile exists the value is taken
line Binary as $0000 0001.
8 Number of swaths Mand 4 Immed Unsigned The number of swaths that make up a
per frame Binary complete frame. It indicates how
many groups of lines the frame has
been divided into.
For a linescan sensor this value
will be $0000 0001.
9 Sensor mode Mand 1 Encode Unsigned $00 OFF
Binary $01 ON
$02 STANDBY
$04 TEST
$05 FAIL
10 Pixel size Mand 2 Immed Unsigned The number of bits per pixel.
Binary
11 Elements per pixel Mand 2 Immed Unsigned The number of elements per pixel.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

79
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Binary
12 Data Ordering Mand 1 Encode Unsigned Type of multispectral data ordering.
Binary $00 INACTIVE (Unispectral data)
$01 BAND INTERLEAVED BY PIXEL
$02 BAND SEQUENTIAL
$03 BAND INTERLEAVED BY LINE
13 Line FOV Mand 8 Immed The field of view across a line. The
FOV angle in radians.
14 Frame or Swath FOV Mand 8 Immed RN The field of view of a frame or
swath orthogonal to the line FOV.
The FOV angle in radians.
15 Number of Fields Mand 1 Immed Unsigned The number of fields which make up
Binary one frame of an interlaced framing
sensor.
$00 INVALID e.g. linescan sensor
$01 NON-INTERLACED FRAMING SENSOR
16 High frequency Mand 1 Encode Unsigned The line scanning direction.
scanning direction Binary $00: Scan in the –y direction.
$01: Scan in the +y direction.
17 Low frequency Mand 1 Encode Unsigned The frame scanning direction.
scanning direction Binary $00: Scan in the –z direction.
S01: Scan in the +z direction.

For n elements the pixel size is:

Pixel size = Element size (ID = 0) + Element size (ID = 1) + … + Element size (ID = n-1)

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

80
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

General 2 = Duration for 3

8: No of Swaths
Sensor y
9: any “Line Direction” Direction
10, 11: Pixel-Info
12: Data Ordering
15: Interlaced
Sensors 7 =n 000
000
Tile 1 Tile 2 ... Tile n
6 000

Frame
5 000
13

1 Se
14 Di nso
re
ct r x
io
“Frame n
Direction” 17
000
Sensor z 000
Direction Tile m
000
000
3 16
4 =m

Interpretation of the Sensor Description Data Table

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

81
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

The STANAG 7023 Sensor Frame Description to accommodate Tiles

(e.g. JPEG files)

Second Tile of Second

Swath (TILE SYNC)
Second Tile of First Last Tile of First Swath
Swath (TILE SYNC) (TILE SYNC)
Third Tile of First
Swath (TILE SYNC)

Maximum Number of Lines per Frame = 4.29G Lines

First Tile of First Swath
(FRAME SYNC)

1* 2* 3* n*

Maximum Number of Swaths per Frame = 4.29G

First Tile of Second
Swath (SWATH SYNC) n+1* n+2* n+3*

First Tile of Third

Swath (SWATH SYNC) * = STANAG 7023 Data File
Number (Header)

Swaths repeat until end

Tiles repeat until end of

of frame

Swaths
frame

Maximum Number of Samples per Line = 4.29G Samples

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

82
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.3 Sensor Calibration Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0002

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Calibration date Mand 8 Encode DTG The date the sensor was calibrated.
2 Calibration Agency Mand 91 Immed ASCII The Agency which performed the
calibration.
Agency name, address and phone
number.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

83
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.4 Sensor Operating Status Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0006

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Status Mand 256 Immed ASCII Sensor error description.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

84
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.5 Sensor Position Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0010

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 X vector component Mand 8 Immed RN X component of the offset vector.
2 Y vector component Mand 8 Immed RN Y component of the offset vector.
3 Z vector component Mand 8 Immed RN Z component of the offset vector.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

85
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.6 Minimum Sensor Attitude Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0020

Table Requirement : Conditional on the Comprehensive Sensor Attitude Data Table not sent.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Rotation about Mand 8 Immed RN Rotation of the sensor in the xy
Z-axis plane in radians.
2 Rotation about Mand 8 Immed RN Rotation of the sensor in the xz
Y-axis plane in radians.
3 Rotation about Mand 8 Immed RN Rotation of the sensor in the yz
X-axis plane in radians.

The order of rotation of the sensor is in the order of the fields, i.e. Z-axis, Y-axis, X-axis.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

86
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.7 Comprehensive Sensor Attitude Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0030

Table Requirement : Conditional on the Minimum Sensor Attitude Data Table not sent

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Rotation about Mand 8 Immed RN Rotation of the sensor in the xy
Z-axis plane in radians.
2 Rotation about Mand 8 Immed RN Rotation of the sensor in the xz
Y-axis plane in radians.
3 Rotation about Mand 8 Immed RN Rotation of the sensor in the yz
X-axis plane in radians.
4 Rotation rate about Mand 8 Immed RN Rate of rotation of the sensor in
Z-axis the xy plane in radians/sec.
5 Rotation rate about Mand 8 Immed RN Rate of rotation of the sensor in
Y-axis the xz plane in radians/sec.
6 Rotation rate about Mand 8 Immed RN Rate of rotation of the sensor in
X-axis the yz plane in radians/sec.
7 Rotation Mand 8 Immed RN Acceleration of rotation of the
acceleration about sensor in the xy plane in
Z-axis radians/sec2.
8 Rotation Mand 8 Immed RN Acceleration of rotation of the

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

87
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
acceleration about sensor in the xz plane in
Y-axis radians/sec2.
9 Rotation Mand 8 Immed RN Acceleration of rotation of the
acceleration about sensor in the yz plane in
X-axis radians/sec2.

The order of rotation of the sensor is in the order of the fields, i.e. Z-axis, Y-axis, X-axis.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

88
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.8 Gimbals Position Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address Range : $0000 0050 to $0000 005F

File Addressing scheme is $0000 005x where x represents the gimbal ID.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 X vector component Mand 8 Immed RN X component of the offset vector.
2 Y vector component Mand 8 Immed RN Y component of the offset vector.
3 Z vector component Mand 8 Immed RN Z component of the offset vector.

The sensor is attached to the last gimbal (if gimbals are used) and will have its own position
data in the Sensor Position Data Table.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

89
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.9 Minimum Gimbals Attitude Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address Range : $0000 0060 to $0000 006F

File Addressing scheme is $0000 006x where x represents the gimbal ID.

Table Requirement : Conditional that the Comprehensive Gimbals Attitude Data Table is not sent

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Rotation about Mand 8 Immed RN Rotation of the gimbals in the xy
Z-axis plane in radians.
2 Rotation about Mand 8 Immed RN Rotation of the gimbals in the xz
Y-axis plane in radians.
3 Rotation about Mand 8 Immed RN Rotation of the gimbals in the yz
X-axis plane in radians.

The order of rotation of the gimbals is in the order of the fields, i.e. Z-axis, Y-axis, X-axis.

The sensor is attached to the last gimbal (if gimbals are used) and will have its own attitude
data in the Sensor Attitude Data Tables.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

90
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.10 Comprehensive Gimbals Attitude Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address Range : $0000 0070 to $0000 007F

File Addressing scheme is $0000 007x where x represents the gimbal ID.

Table Requirement : Conditional that the Minimum Gimbals Attitude Data Table is not sent

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Rotation about Mand 8 Immed RN Rotation of the gimbals in the xy
Z-axis plane in radians.
2 Rotation about Mand 8 Immed RN Rotation of the gimbals in the xz
Y-axis plane in radians.
3 Rotation about Mand 8 Immed RN Rotation of the gimbals in the yz
X-axis plane in radians.
4 Rotation rate about Mand 8 Immed RN Rate of rotation of the gimbals in
Z-axis the xy plane in radians/sec.
5 Rotation rate about Mand 8 Immed RN Rate of rotation of the gimbals in
Y-axis the xz plane in radians/sec.
6 Rotation rate about Mand 8 Immed RN Rate of rotation of the gimbals in
X-axis the yz plane in radians/sec.
7 Rotation Mand 8 Immed RN Acceleration of rotation of the
acceleration about gimbals in the xy plane in

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

91
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Z-axis radians/sec2.
8 Rotation Mand 8 Immed RN Acceleration of rotation of the
acceleration about gimbals in the xz plane in
Y-axis radians/sec2.
9 Rotation Mand 8 Immed RN Acceleration of rotation of the
acceleration about gimbals in the yz plane in
X-axis radians/sec2.

The order of rotation of the gimbals is in the order of the fields, i.e. Z-axis, Y-axis, X-axis.

The sensor is attached to the last gimbal (if gimbals are used) and will have its own attitude
data in the Sensor Attitude Data Tables.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

92
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.11 Sensor Index Data Table

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address Range : $0000 0200 to $0000 02FF

File Addressing scheme is $0000 02xx where xx represents the segment number.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Collection Start Mand 8 Encode DTG The date and time at the start of
Time the sensor activation.
2 Collection Stop Mand 8 Encode DTG The date and time at the end of the
Time sensor activation.
3 Start Header Time Mand 8 Immed Unsigned The time tag of the first header for
Tag Binary the sensor activation.
4 End Header Time Tag Mand 8 Immed Unsigned The time tag of the last header for
Binary the sensor activation.
5 Aircraft location Mand 8+8 Immed RN+RN Latitude and Longitude.
at Collection Start
Time
6 Aircraft location Mand 8+8 Immed RN+RN Latitude and Longitude.
at Collection End
Time
7 Sensor Start Mand 8 Immed Unsigned Number of bytes offset from start of

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

93
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
Position Binary record to start of sensor
activation.
8 Sensor End Position Mand 8 Immed Unsigned Number of bytes offset from start of
Binary record to end of sensor activation.
9 (*) Repeat fields 1-8 for each sensor
activation.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

94
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.12 Sensor Element Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 1000

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Element size Mand 1 Immed Unsigned The number of bits in the element.
Binary
2 Element Bit offset Mand 2 Immed Unsigned The start bit offset of this element
Binary within a composite sample.
3 Sensor Element ID Mand 2 Immed Unsigned The sensor element ID. Unique for
Binary each element.
4 Minimum wavelength Mand 8 Immed RN Wavelength in metres.
5 Maximum wavelength Mand 8 Immed RN Wavelength in metres.
6 (*) Repeat Fields 1-5 for each element.

The STANAG allows up to 64K elements per sensor.

The elements are used to indicate different receptor bands of the sensor. E.g. a colour camera
might have 3 elements: 1 for red, 1 for green, and 1 for blue. Starting from 0, the elements
shall be identified by an incremental Sensor Element ID number.

The above table allows for arbitrary length Element sizes.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

95
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

By specifying the size and bit offset we assume contiguous bits for an element.

The examples below show three possible representations (band interleaved by pixel (BIP), band
sequential (BSQ), band interleaved by line (BIL)) for an RGB image.

Case 1 (BIP): R G B R G B R G B R G B R G B R G B ... (Line 1)

R G B R G B R G B R G B R G B R ... (Line 2)
R G B R G B R G B R G B R G ... (Line 3)
R G B R G B R G B R G B ... (Line 4)
R G B R G B R G B R B ... (Line 5)
....

Case 2 (BSQ): R R R R R R R R R R R R R R R R R R ... (ID = 0, Line 1)

R R R R R R R R R R R R R R R R ... (ID = 0, Line 2)
R R R R R R R R R R R R R R ... (ID = 0, Line 3)
R R R R R R R R R R R R ... (ID = 0, Line 4)
....

G G G G G G G G G G G G G G G G G G ... (ID = 1, Line 1)

G G G G G G G G G G G G G G G G ... (ID = 1, Line 2)
G G G G G G G G G G G G G G ... (ID = 1, Line 3)
G G G G G G G G G G G G ... (ID = 1, Line 4)
....

B B B B B B B B B B B B B B B B B B ... (ID = 2, Line 1)

B B B B B B B B B B B B B B B B ... (ID = 2, Line 2)
B B B B B B B B B B B B B B ... (ID = 2, Line 3)
B B B B B B B B B B B B ... (ID = 2, Line 4)
....

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

96
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Case 3 (BIL): R R R R R R R R R R R R R R R R R R ... (ID = 0, Line 1)

G G G G G G G G G G G G G G G G G G ... (ID = 1, Line 1)
B B B B B B B B B B B B B B B B B B ... (ID = 2, Line 1)
R R R R R R R R R R R R R R R R ... (ID = 0, Line 2)
G G G G G G G G G G G G G G G G ... (ID = 1, Line 2)
B B B B B B B B B B B B B B B B ... (ID = 2, Line 2)
R R R R R R R R R R R R R R ... (ID = 0, Line 3)
G G G G G G G G G G G G G G ... (ID = 1, Line 3)
B B B B B B B B B B B B B B ... (ID = 2, Line 3)
R R R R R R R R R R R R ... (ID = 0, Line 4)
....

The size of a frame, swath or tile shall be given by the number of lines and the number of
samples per line. For example, this means that for tiles that are different in their data
ordering only (BIP, BIL or BSQ ordered sensor data) the tile sizes have to be the same.

Sample size

It should be noted that in BIP the three sensor elements (R, G, B) are combined into one
composite sample, leading to a sample size of 3 x 8 = 24 bits. In the BSQ and BIL cases the
samples of the sensor elements are not combined into a composite one, but remain individually
ordered by line or band. Therefore, in these cases one sample contains only the information from
a single sensor element, leading to a sample size of 8 bits, which is equal to the corresponding
element size.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

97
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Example RGB-Sensor:

(For Elements per pixel and Data Ordering see Sensor Description Data Table)

BIP BSQ BIL

Case 1 Case 2 Case 3
Sample size 24 8 8
Elements per pixel 3 3 3
Data Ordering $01 $02 $03
Element Size, ID = 0 (R) 8 8 8
Element Size, ID = 1 (G) 8 8 8
Element Size, ID = 2 (B) 8 8 8
Element Bit Offset 0 0 0
ID = 0 (R)
Element Bit Offset 8 0 0
ID = 1 (G)
Element Bit Offset 16 0 0
ID = 2 (B)

In the case of unispectral data (e.g. B/W-Sensor), the field Data Ordering shall be set equal to
$00, Elements per pixel equal = 1, and Element size = Sample size.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

98
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.13 Sensor Sample Coordinate Description Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 1010

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Size of “x” vector Mand 1 Immed Unsigned The number of bits used in the
component Binary vector.
Range $00 to $FF.
2 Size of “y” vector Mand 1 Immed Unsigned The number of bits used in the
component Binary vector.
Range $00 to $FF.
3 Size of “z” vector Mand 1 Immed Unsigned The number of bits used in the
component Binary vector.
Range $00 to $FF.
4 (*) Repeat Fields 1-3 for each element.
Maximum number of elements = 64k.

This table is used in conjunction with the Sensor Element Data Table and the Sensor Sample
Timing Description Data Table.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

99
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.14 Sensor Sample Timing Description Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 1020

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Timing method Mand 1 Encode Unsigned Describes the type of time interval
Binary represented by the timing data.

CUMULATIVE represents the time

relative to the Header Time Tag.
DIFFERENTIAL represents the change
in time from one sampling to the
next.

$00 UNUSED
$01 CUMULATIVE
$02 DIFFERENTIAL
2 (*) Repeat Field 1 for each element.
Maximum number of elements = 64k.

This table is used in conjunction with the Sensor Element Data Table and the Sensor Sample
Coordinate Description Data Table.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

100
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-9.15 Sensor Grouping Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

Source Type : Sensor Parametric Data

Source Address : $40
File Address : $0000 0080

This table is of variable length dependent upon the number of sensors in the group.
Table size = (n + 3) bytes.

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Group ID Mand 1 Immed Unsigned Sensor Group Identifier
Binary
2 Group type Mand 1 Encode Unsigned $00 = Coverage
Binary $01 = Spectral
3 Number of sensor Mand 1 Immed Unsigned Number of sensor source IDs that are
IDs within the Binary grouped together, e.g. #n.
Group
4 Sensor ID Mand 1 Immed Unsigned Sensor ID #1
Binary
5 Sensor ID Cond 1 Immed Unsigned Sensor ID #2
Binary
Repeat until all #n sensor IDs are
recorded.
Sensor ID Cond 1 Immed Unsigned Sensor ID #n.
Binary

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

101
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-10 Sensor Compression Tables

A-10.1 Sensor Compression Data Table

Identifies the algorithms and parameters of the imagery compression scheme used. This file
defines the compression scheme used on the image data. If the sensor data is not compressed then
this file is not used.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0100

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Compression Mand 1 Encode Unsigned Algorithm used to compress sensor
algorithm Binary data.
$02 JPEG (ISO/IEC 10918-1:1994)

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

102
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-10.2 JPEG Compression Data Tables

If Image Compression is by the JPEG method, then the tables described in this section may be
required.

The JPEG compression method complies with the international standard for image compression,
ISO/IEC 10918-1:1994.

The JPEG compression format specified within STANAG 7023 ensures that each Image Data Packet
contains only complete fully ISO/IEC JPEG compliant interchange format data stream.

An important table to be used in conjunction with JPEG compression format is the Sensor
Description Data Table and the figure that appears with it – The STANAG 7023 Sensor Frame
Description to accommodate Tiles (e.g. JPEG files).

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

103
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

JPEG Interchange Format (monochrome and interleaved

YCbCr601)

ENTROPY
DRI and
DQT and DHT and SOF and SOS and DATA and
SOI PARAMETERS EOI
PARAMETERS PARAMETERS PARAMETERS PARAMETERS optional RST
(Optional)
Markers

JPEG Interchange Format (Non-interleaved YCbCr601)

ENTROPY
DRI and
DQT and DHT and SOF and SOS and DATA and
SOI PARAMETERS
PARAMETERS PARAMETERS PARAMETERS PARAMETERS optional RST
(Optional)
Markers

ENTROPY ENTROPY
SOS and DATA and SOS and DATA and
EOI
PARAMETERS optional RST PARAMETERS optional RST
Markers Markers

The JPEG Interchange Format

For low bandwidth systems the JPEG abbreviated image format can be used, in which case the JPEG
Sensor Quantisation Data Table and the JPEG Sensor Huffman Data Table can be omitted from the
Image Data Packets. These two tables must occur elsewhere in the record prior to the relevant
Image Data Packets.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

104
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

JPEG Abbreviated Format (monochrome and interleaved

YCbCr601)
ENTROPY DATA
DRI and
SOF and SOS and with interleaved
SOI PARAMETERS EOI
PARAMETERS PARAMETERS optional RST
(Optional)
Markers

JPEG Abbreviated Format (Non-interleaved YCbCr601)

ENTROPY
DRI and
SOF and SOS and DATA and
SOI PARAMETERS
PARAMETERS PARAMETERS optional RST
(Optional)
Markers

ENTROPY ENTROPY
SOS and DATA and SOS and DATA and
EOI
PARAMETERS optional RST PARAMETERS optional RST
Markers Markers

The JPEG Abbreviated Image Format

The JPEG processes supported by STANAG 7023 are the 8-bit precision baseline JPEG process and
the 12-bit precision extended sequential JPEG process for both monochrome and colour images.

Arithmetic entropy coding, and progressive/hierarchical representations are not supported by

STANAG 7023.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

105
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

It is mandatory to convert RGB colour source data to YCbCr601 in accordance with CCIR601 before
JPEG compression.

Each Image Data Packet shall contain one single JPEG image. The required JPEG markers within
this JPEG image are as follows. (The order that the markers appear in the Image Data Packet is
as listed):

SOI Start of Image Marker

SOF0 or SOF 1 Start of Frame Marker and Parameters
SOS Start of Scan Marker and Parameters
EOI End of Image Marker

The JPEG interchange format requires that the following markers appear between SOI and SOS and
before each subsequent SOS if subsequent SOS markers exist:

DQT Define Quantisation Table Marker and Parameters

DHT Define Huffman Table Marker and Parameters

One or both of these two markers (DQT and DHT) may be omitted if the abbreviated image format is
used.

If scan restarts are used then the Define Restart Interval Marker (DRI) and Parameters shall
appear between SOI and SOS and before each subsequent SOS if there is more than one scan.

No other JPEG markers are allowed by STANAG 7023.

Compressed image data shall follow each SOS. RSTn markers may be interleaved within the
compressed image data if specified by the Define Restart Interval Marker.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

106
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-10.3 JPEG Sensor Quantisation Data Table

This JPEG Sensor Quantisation Data Table is used whenever one or more of the current
quantisation tables 0 to 3 are to be updated with new custom quantisation values. Tq (See field
3) is used to specify which table is to be replaced.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0101

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 DQT Mand 2 Encode Unsigned Ensures that a JPEG decoder can
Define Quantisation Binary identify this table type and
Table Marker understand its contents.
This field is included here to
conform with ISO/IEC 10918-1:1994
Value = $FFDB
2 Lq Mand 2 Immed Unsigned Describes the length in bytes of
Length of Binary this table. The Length excludes
parameters Field 1.
This field is included here to
conform with ISO/IEC 10918-1:1994
3 PqTq Quantisation Mand 1 Encode Unsigned Binary Pq specifies the precision of
table element Binary the quantisation table values Qk in
precision quantisation table number Tq

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

107
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme

Encoded as binary XY where;

X (4 Bits) is the precision, with:
$0 is 8-bit precision
$1 is 16-bit precision.
Y (4 Bits) is the quantisation table
number $0 to $3.
4 Qk Quantisation Mand 64 Immed Unsigned Specifies the 64 custom quantisation
table elements (64) or Binary table elements for the table
in zigzag order 128 referred to in field 3.
Zigzag is defined in ISO/IEC 10918-
1:1994.
5 (*) (*) (*) (*) (*) (*)

(*) Fields 3 and 4 repeat for each additional Quantisation Table up to a maximum of four tables
in total.

This table shall be used for the JPEG Abbreviated Image Format.

There are four possible Quantisation Tables that are numbered 0 to 3. It is mandatory for STANAG
7023 collection platforms and exploitation systems that support JPEG compression to have
Quantisation Tables 0 and 1 pre-entered with the following default Quantisation Tables. These
default tables are permanently stored in both the collection platforms and exploitation
platforms.

Quantisation Table 0 shall be the table that appears in section K.1 Table K.1 Luminance
Quantisation Table of ISO/IEC 10918-1:1994.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

108
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Quantisation Table 1 shall be the table that appears in section K.1 Table K.2 Chrominance
Quantisation Table of ISO/IEC 10918-1:1994.

The Default Quantisation Table 0 shall be used as the default table for monochrome imagery.

The Quantisation Tables 2 and 3 have no values until written by this JPEG Sensor Quantisation
Data Table. The default tables are permanently valid unless overwritten by a custom table during
the mission. Once any of the four Quantisation Tables are overwritten by a custom table that
table shall be permanently valid unless it is overwritten by a new custom table later in the
mission.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

109
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-10.4 JPEG Sensor Huffman Data Table

This JPEG Sensor Huffman Data Table is used whenever one or more of the current DC or AC Huffman
tables 0 to 3 are to be updated with new custom DC or AC Huffman values. TcTh is used to specify
which table is to be replaced.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
01xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Parametric Data

Source Address : $40 to $7F
File Address : $0000 0102

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 DHT Mand 2 Encode Unsigned Ensures that a JPEG decoder can
Define Huffman Binary identify this table type and
Table marker understand its contents.
This field is included here to
conform to ISO/IEC 10918-1:1994.
Value = $FFC4
2 Lh Mand 2 Immed Unsigned Describes the length in bytes of
Length of Binary this table. The Length excludes
parameters Field 1.
This field is included here to
conform to ISO/IEC 10918-1:1994.
3 TcTh Mand 1 Encode Unsigned Binary specifies whether the
Huffman Table Class Binary following table is a DC or an AC
and Table table and also specifies the table
Identifier identification number.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

110
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme

Encoded as binary byte XY where;

X (4 Bits) is the table type, with:
$0 = DC
$1 = AC.
Y (4 Bits) is the huffman table
number from $0 to $3.
4 L1 Mand 16 Immed Unsigned Details the number of huffman codes
Number of codes in Binary that exist for each of the 16
each length lengths. The lengths are from 1 to
16.
5 Vi,j Mand 12, Immed Unsigned Details the values of the huffman
Huffman Code Values 16, Binary codes for each of the 16 lengths.
162,
or No of bytes = 12 for 8-bit greyscale
226 DC table or YCbCr601 colour DC
table.
No of bytes = 16 for 12-bit
greyscale DC table.
No of bytes = 162 for 8-bit
greyscale AC table or YCbCr601
colour AC table.
No of bytes = 226 for 12-bit
greyscale AC table.
6 (*) (*) (*) (*) (*) (*)

(*) Fields 3, 4 and 5 repeat for each additional Huffman Table up to a maximum of eight tables
in total (four DC and four AC tables).

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

111
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

This table shall be used for the JPEG Abbreviated Image Format.

There are four possible DC Huffman Tables and four possible AC Huffman Tables that are each
numbered 0 to 3. It is mandatory for STANAG 7023 collection platforms and exploitation systems
that support JPEG compression to have DC and AC Huffman Tables 0 and 1 pre-entered with the
following default Huffman Tables. These default tables are permanently stored in both the
collection platforms and exploitation platforms.

DC Huffman Table 0 shall be the table that appears in section K.3.1 Table K.3 Luminance DC
Difference Table of ISO/IEC 10918-1:1994.

DC Huffman Table 1 shall be the table that appears in section K.3.1 Table K.4 Chrominance
DC Difference Table of ISO/IEC 10918-1:1994.

AC Huffman Table 0 shall be the table that appears in section K.3.2 Table K.5 Table for
Luminance AC Coefficients of ISO/IEC 10918-1:1994.

AC Huffman Table 1 shall be the table that appears in section K.3.2 Table K.6 Table for
Chrominance AC Coefficients of ISO/IEC 10918-1:1994.

The Default DC and AC Huffman Table 0 shall be used as the default table for monochrome imagery.

The Huffman Tables 2 and 3 have no values until written by this JPEG Sensor Huffman Data Table.
The default tables are permanently valid unless overwritten by a custom table during the
mission. Once any of the four DC or AC Huffman Tables are overwritten by a custom table that
table shall be permanently valid unless it is overwritten by a new custom table later in the
mission.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

112
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-11 Sensor Data Tables

(WARNING NOTICE – THESE TABLES MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER
IMPLEMENTATION OF THESE TABLES IS VALID FOR THIS EDITION.)

The Sensor Data Tables are five tables with their own Data File Address. These tables are used
to describe the sensor data and its pixel registration (x, y, z) within the image. The sensor
sample timing describes the time relationship between adjacent pixels.

The Data File Addresses of the Sensor Data Tables are as follows.

Data File Data File Address

Sensor Data Table $0000 0000
Sensor Sample “x” Coordinate Table $0000 0010
Sensor Sample “y” Coordinate Table $0000 0020
Sensor Sample “z” Coordinate Table $0000 0030
Sensor Sample Timing Table $0000 0050

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

113
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-11.1 Sensor Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

This table is used to transmit the sensor data.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
10xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Data

Source Address : $80 to $BF
File Address : $0000 0000

Field Field name Req. No. Field Encoding Description/Encoding units

Bits Type Scheme
1 Sensor data Mand Sample Immed See next The encoding scheme is described by
size column the following 2 tables:
1. Sensor Description Data Table
2. Sensor Element Data Table
2 (*) Repeat for each sample.

The data file size must be a multiple of whole bytes. Any padding will be in the last byte and
from the LSB towards the MSB. Examples 1 and 2 show how the bits are packed into the data file
for a RGB band interleaved by pixel (BIP) representation for a 3 byte data file containing 3
elements, i.e. one sample. (In reality the data file size would be much bigger containing many
samples).

If in example 2 there were 750 6-bit RGB elements (250 BIP samples) to make 250 pixels, then:

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

114
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Total no. of bits in table = 750 x 6 = 4500 bits, and 4500 bits = 562 bytes and 4 bits, the
padding is xxxx. The data file size for the 750 6-bit elements would be 563 bytes.

Example 1
3 8-bit RGB elements making a single BIP sample.

Red = 112 10 Green = 86 10 Blue = 5010

0 1 1 1 0 0 0 0 0 1 0 1 0 1 1 0 0 0 1 1 0 0 1 0

Byte 1 Byte 2 Byte 3

MSB LSB

Example 2
3 6-bit RGB elements making a single BIP sample. The least significant bits are padded with
xxxxxx.

Red = 45 10 Green = 37 10 Blue = 1810

1 0 1 1 0 1 1 0 0 1 0 1 0 1 0 0 1 0 X X X X X X

Byte 1 Byte 2 Byte 3

MSB LSB

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

115
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-11.2 Sensor Sample “x” Coordinate Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

This table is used to describe the pixel registration of the sensor data.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
10xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Data

Source Address : $80 to $BF
File Address : $0000 0010

Field Field name Req. No. Field Encoding Description/Encoding units

Bits Type Scheme
1 Sample “x” Mand Size of Immed See next The encoding scheme is described by
coordinate “x” column the following 2 tables:
vector 1. Sensor Description Data Table
component 2. Sensor Sample Coordinate
Description Data Table
2 (*) Repeat for each sample.

The data file size must be a multiple of whole bytes. Any padding will be in the last byte and
from the LSB towards the MSB.

This table is used for the sensor modelling method VECTOR MODELLING.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

116
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-11.3 Sensor Sample “y” Coordinate Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

This table is used to describe the pixel registration of the sensor data.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
10xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Data

Source Address : $80 to $BF
File Address : $0000 0020

Field Field name Req. No. Field Encoding Description/Encoding units

Bits Type Scheme
1 Sample “y” Mand Size of Immed See next The encoding scheme is described by
coordinate “y” column the following 2 tables:
vector 1. Sensor Description Data Table
component 2. Sensor Sample Coordinate
Description Data Table
2 (*) Repeat for each sample.

The data file size must be a multiple of whole bytes. Any padding will be in the last byte and
from the LSB towards the MSB.

This table is used for the sensor modelling method VECTOR MODELLING.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

117
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-11.4 Sensor Sample “z” Coordinate Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

This table is used to describe the pixel registration of the sensor data.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
10xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Data

Source Address : $80 to $BF
File Address : $0000 0030

Field Field name Req. No. Field Encoding Description/Encoding units

Bits Type Scheme
1 Sample “z” Mand Size of Immed See next The encoding scheme is described by
coordinate “z” column the following 2 tables:
vector 1. Sensor Description Data Table
component 2. Sensor Sample Coordinate
Description Data Table
2 (*) Repeat for each sample.

The data file size must be a multiple of whole bytes. Any padding will be in the last byte and
from the LSB towards the MSB.

This table is used for the sensor modelling method VECTOR MODELLING.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

118
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

A-11.5 Sensor Sample Timing Data Table

(WARNING NOTICE – THIS TABLE MAY BE SUBJECT TO CHANGE IN FUTURE EDITIONS. HOWEVER IMPLEMENTATION
OF THIS TABLE IS VALID FOR THIS EDITION.)

This table is used to describe the timing of the sensor data samples.

The sensor number is encoded into the Source Address. The binary form of the Source Address is:
10xxxxxx, where xxxxxx is the sensor number.

Source Type : Sensor Data

Source Address : $80 to $BF
File Address : $0000 0050

Field Field name Req. No. Field Encoding Description/Encoding units

Bytes Type Scheme
1 Sample Timing Mand 8 Immed RN Timing value in seconds.

The encoding scheme is described by

the following 2 tables:
1. Sensor Description Data Table
2. Sensor Sample Timing Description
Data Table
2 (*) Repeat for each sample.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

119
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3

Differential timing

Sample Sample Sample Sample Sample Sample Sample

3 2 1.5 1 1.5 2 3

0 3 5 6.5 7.5 9 11 14
Time (ms)
Cumulative timing

Example of Sample Timing methods

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

120
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex B

Annex B – Data Definitions

B-1 Real Numbers (RN)

Definition of a Real Number (RN) - IEEE Standard 754.

Real numbers in STANAG 7023 are represented in the IEEE

double format.

B-1.1 Double Format

The IEEE double format consists of three fields: a 52-bit

fraction, f; an 11-bit biased exponent, e; and a l-bit
sign, S. These fields are stored contiguously in two
successively addressed 32-bit words, as shown in Figure
B-1.

Real Number Big Endian Byte Ordering:

[byte 8 MSB][byte 7][byte 6][byte 5][byte 4][byte 3]byte 2][byte 1][byte 0 LSB]
Increasing byte ordering in the record→

If f [31:0] denotes the least significant 32 bits of the

fraction, then bit 0 is the least significant bit of the
entire fraction and bit 31 is the most significant of the
32 least significant fraction bits.

In the other 32-bit word, bits 0-19 contain the 20 most

significant bits of the fraction, f [51:32], with bit 0
being the least significant of these 20 most significant
fraction bits, and bit 19 being the most significant bit
of the entire fraction; bits 20-30 contain the 11-bit
biased exponent, e, with bit 20 being the least
significant bit of the biased exponent and bit 30 being
the most significant; and the highest-order bit 31
contains the sign bit, S.

Figure B-1 numbers the bits as though the two contiguous

32-bit words were one 64-bit word in which bits 0-51
store the 52-bit fraction, f; bits 52-62 store the 11-bit
biased exponent, e; and bit 63 stores the sign bit, S.

S e [62:52] f [51:32]

f [31:0]

Figure B-1 - Double Storage Format

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

121
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex B
The values of the bit patterns in these three fields
determine the value represented by the overall bit
pattern.

Table B-1 shows the correspondence between the values of

the bits in the three constituent fields, on the one
hand, and the value represented by the double-format bit
pattern on the other; u means don’t care, because the
value of the indicated field is irrelevant to the
determination of value for the particular bit pattern in
double format.

Double-Format Bit Pattern Value

0< e <2047 (-1)s x 2e-1023 x l.f (normal
numbers)
e=O; f≠0 (-1)s x 2-l022 x O.f (subnormal
(at least one bit in f is numbers)
nonzero)
e=O; f=0 (-1)s x 0.0 (signed zero)
(all bits in f are zero)
s=0; e=2047; f=.000—00 +INF (positive infinity)
(all bits in f are zero)
s=1; e=2047; f =.000—00 -INF (negative infinity)
(all bits in f are zero)
s=u; e=2047; f≠0 NaN (Not-a-Number)
(at least one bit in f is
nonzero)

Table B-1 - Values Represented by Bit Patterns in IEEE

Double Format.

Notice that when e<2047, the value assigned to the

double-format bit pattern is formed by inserting the
binary radix point immediately to the left of the
fraction’s most significant bit, and inserting an
implicit bit immediately to the left of the binary point.
The number thus formed is called the significant. The
implicit bit is so named because its value is not
explicitly given in the double-format bit pattern, but is
implied by the value of the biased exponent field.

For the double-format, the difference between a normal

number and a subnormal number is that the leading bit of
the significand (the bit to the left of the binary point)
of a normal number is 1, whereas the leading bit of the
significand of a subnormal number is 0. Double-format
subnormal numbers were called double-format denormalized
numbers in IEEE Standard 754.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

122
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex B
The 52-bit fraction combined with the implicit leading
significand bit provides 53 bits of precision in double-
format normal numbers.

Examples of important bit patterns in the double-storage

format are shown in Table B-2. The bit patterns in the
second column appear as two 8-digit hexadecimal numbers.
For the SPARC and HP 700 architectures, the left one is
the value of the lower addressed 32-bit word, and the
right one is the value of the higher addressed 32-bit
word, while for the x86 and PowerPC architectures, the
left one is the higher addressed word, and the right one
is the lower addressed word.

Common Name Bit Pattern (Hex) Equivalent Value

+0 00000000 00000000 0.0
-0 80000000 00000000 -0.0
1 3FF00000 00000000 1.0
2 40000000 00000000 2.0
max normal 7FEFFFFF FFFFFFFF 1.7976931348623157e+308
number
min. positive 00100000 00000000 2.2250738585072014e-308
normal number
max subnormal 000FFFFF FFFFFFFF 2.2250738585072009e-308
number
min. positive 00000000 00000001 4.9406564584124654e-324
subnormal
number
+ ∞ 7FF00000 00000000 Infinity
- ∞ FFF00000 00000000 -Infinity
Not-a-Number FFFFFFFF FFFFFFFF NaN

Table B-2 - Bit Patterns in Double-Storage Format and

their IEEE Values

The STANAG 7023 chosen hex value of a NaN as shown in

Table B-2.

B-2 Units

B-2.1 Definition

SI Units (plus derived units). See ISO 1000.

Time = seconds
Length = metres
Area = metres2
Height = metres
Velocity = metres/sec
Acceleration = metres/sec 2

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

123
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex B
Angle = radians
Angular Velocity = radians/sec
Angular Acceleration = radians/sec2

B-2.2 World Geodetic System (WGS-84 - see ISO

6709/1983)

Latitude and Longitude will be represented as a Real

Number + Real Number (RN+RN). The format will be Latitude
followed by Longitude. The Real Numbers will be in double
format.

The form will be:

RADIANS, rads(.)decimal rads of the earth’s curvature.

(Just like any length is metre(.)decimal metre) (+ve East
of the meridian, and +ve North of the equator).

B-2.3 True Heading, XY Coordinates, and Radians

North = 0 rads

West = - π/2 rads East = + π/2 rads

South = -π rads

The range of radians will be: -π ≤ radians < +π

B-2.4 Date Time Group

B-2.4.1 Definition

Total Bytes = 8, Unsigned Binary

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

124
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex B
byte 7 transmitted first ... byte 0.

BYTES
7 & 6 5 4 3 2 1 & 0
YEAR MONTH DAY HOUR MINUTE MILLISECOND
(1-12) (1-31) (0-23) (0-59) (0-59999)
1997 12 01 07 59 1500
8 7 6 5 4 3 2 1
0000 1100 0000 0000 0000 0011 0000 1101
0111 1101 1100 0001 0111 1011 0101 1100
07, CD 0C 01 07 3B 05, DC

Example - 1st December 1997, 07:59. 1.5 seconds

1500 ms = 1.5 seconds.

B-2.5 Order of Data

B-2.5.1 Big Endian Byte Order

Data within STANAG 7023 tables is written using the Big

Endian Byte Order Format where the Most Significant Bit
of a byte is bit 7, the Least Significant Bit of a byte
is bit 0.
MSB LSB
1 0 0 1 1 1 0 1
Bit 7 Bit 6 Bit 5 Bit 4 Bit 3 Bit 2 Bit 1 Bit 0

Binary Number represents 9D (16) or 157 (10)

Bytes are ordered Most Significant Byte first, Least

Significant Byte last. E.g. for an 8 byte Field the
ordering would be.

[byte 8 MSB][byte 7][byte 6][byte 5][byte 4][byte 3]

[byte 2][byte 1][byte 0 LSB]
Increasing byte ordering in the record →

B-2.6 ASCII (ISO/IEC 10646-1)

8-bit ASCII characters are LEFT justified. ASCII fields

are to be used as free text for transmission of non-
encoded immediate information.

The subset of ASCII characters to be used are the

printable characters plus the NULL, i.e.:

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

125
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex B

NULL ($00)
space ($20) to tilde ($7E)

The following string “Hello” encoded into an 8 byte wide

ASCII field, is represented as follows:

H e l l o NULL NULL NULL

48(16) 65(16) 6C(16) 6C(16) 6F(16) 00(16) 00(16) 00(16)
72(10) 101(10) 108(10) 108(10) 111(10) 0(10) 0(10) 0(10)
BYTE 7 BYTE 6 BYTE 5 BYTE 4 BYTE 3 BYTE 2 BYTE 1 BYTE 0
WRITTEN WRITTEN
FIRST LAST

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

126
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex C

Annex C – Abbreviations and Glossary

C-1 Abbreviations

ASCII American Standard Code for

Information Interchange
ATO Air tasking Order
BE Basic Encyclopaedia
Cond Conditional Requirement
CRC Cyclic Redundancy Check
DHT Define Huffman Tables
DIAM Defense Intelligence Agency
DQT Define Quantisation Tables
DRI Define Restart Interval
DTG Date Time Group
EEI Essential Elements of
Information
Encode Encoded Value
EO Electro-Optical
EOI End Of Image
FOV Field of View
FRAG Fragmentary Order
GPS Global Positioning System
Hex Hexadecimal
Immed Immediate Value
INS Inertial Navigation System
IR Infra Red
ISO/IEC International Standards
Organisation / International
Electrotechnical Commission
JPEG Joint Photographic Experts
Group
LSB Least Significant Byte
LTOIV Latest Time of Intelligence
Value
Mand Mandatory Requirement
mm Millimetre
MSB Most Significant Byte
MTI Moving Target Indicator
NaN Not a Number
NATO North Atlantic Treaty
Organisation
Opt Optional Requirement
RGB Red, Green, Blue
RMS Reconnaissance Management
System

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

127
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex C
RN Real Number
RST Restart
SAR Synthetic Aperture Radar
SOF Start Of Frame
SOF0 Start Of Frame for 8-bit
Baseline JPEG
SOF1 Start Of Frame for 12-bit
Extended Sequential JPEG
SOI Start Of Image
SOS Start Of Scan
UTC Universal Time Coordinated
V/H The ratio of velocity to
height. Used to correct sensor
geometry.
YCbCr601 Luminance Chrominance Colour
Space in accordance with
CCIR601

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

128
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex C

C-2 Glossary

Auxiliary data Information generated by the

collection system to describe all
aspects of the mission as required
except for the sensor data.
Auxiliary data file A logical grouping of auxiliary data.
Byte Eight binary digits (bits)
CRC-16 An error checking algorithm for use
on data.
Data file The realisation of a Table as a data
stream.
Data file address Allows each Table to have a unique
address. Used to relate the data file
to a specific Table for decoding
purposes.
Data file number A generation sequence number (not
necessarily a transmission sequence
number) and acts as a counter per
source address.
Data file size The number of bytes in a data file.
Data Segment A segment that is primarily used for
sensor data files but could also have
interleaved auxiliary data files.
Element The smallest definable sensitive area
of the detector array of a sensor. A
sensor element produces an output
representing the detected energy from
a scene element within one single
wavelength band to which the sensor
is sensitive.

Pixels are made form samples;

Samples are made from elements.

Pixel size ≥ Sample size

Sample size ≥ Element size
Field (picture) An interleaved part of a frame, e.g.
a standard TV frame is made up of two
fields. Not all frames use fields.
Field of view (FOV) The area of coverage of a specific
sensor. Usually stated in angular
dimensions.
Fragmentary order (FRAG) An abbreviated form of an “Operations
(OPS) Order”, generally more specific
and time sensitive.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

129
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex C
Frame A pixel representation of the full
FOV of a sensor.

The hierarchy of image sections and

sub-sections is:
SUPER FRAMEs are made up from
FRAMEs which are made up from
SWATHs which are made up from
LINEs.
Gimbals A mechanical structure that enables a
sensor to reposition itself relative
to the platform.
Header A 32 byte table preceding a data
file. Its contents define the
structure of the associated data
file.
Information Requester A person who requests information
from the mission but who was not
responsible for requesting or
planning the mission.
Line A single row of pixels. A sub-set of
a Frame.

The hierarchy of image sections and

sub-sections is:
SUPER FRAMEs are made up from
FRAMEs which are made up from
SWATHs which are made up from
LINEs.
Mission Requester A person who requests a mission to be
flown or planned to obtain
information.
Packet A data structure consisting of a
sync, a header, and a data file.
Pan framing sensor A pan framing sensor collects data
samples while the sensor is in
continuous motion.
Pixel A picture element. The smallest
resolvable area of an image, either
on screen or stored in memory.
Samples relating to the same pixel
shall not be spread over more than
one frame, swath or tile of sensor
data.

Pixels are made form samples;

Samples are made from elements.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

130
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex C
Pixel size ≥ Sample size
Sample size ≥ Element size
Postamble A collection of auxiliary data files
to enable efficient analysis of the
record. Postamble data files are
optional and may be appended to the
preamble (if possible) or appended to
the data segments.
Preamble The first segment in a record. The
contents of a preamble shall enable
an exploitation system to interpret
and act upon subsequent segments.
RADALT Radar Altimeter. A radio ranging
instrument which measures the
distance between the instrument and
the ground or surface level.
Typically in the context of aircraft
the RADALT is the "radar altitude"
above ground level, i.e. the actual
height of the aircraft above the
nearest surface vertically below the
aircraft.
Record The top level data structure
consisting of all of the segments.
A record may contain all or a portion
of the data collected during a
mission.
Sample A digital value representing the
output of one or more sensor
elements. The ordering of the samples
can differ from sensor to sensor.

Pixels are made form samples;

Samples are made from elements.

Pixel size ≥ Sample size

Sample size ≥ Element size
Scene element An area on the ground that is
projected onto a single sensor
element of the sensor at a given
instant in time.
Segment A segment consists of a set of
interleaved packets of data without
any time discontinuities. Segments
are defined for the purpose of
transmitting related sensor data and
auxiliary data.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

131
 NATO UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)
STANAG 7023 Edit. 2 Draft3
Annex C
Sensor data Image data collected by a sensor.
Sensor data file A logical grouping of data for a
specific sensor.
Source address Related tables have the same source
address for “high level” addressing.
Step framing sensor A step framing sensor collects data
samples while the sensor is moved in
a step-stop motion.
Super frame A collection of image frames.

The hierarchy of image sections and

sub-sections is:
SUPER FRAMEs are made up from
FRAMEs which are made up from
SWATHs which are made up from
LINEs.
Swath A sub-section of a frame.

The hierarchy of image sections and

sub-sections is:
SUPER FRAMEs are made up from
FRAMEs which are made up from
SWATHs which are made up from
LINEs.
Sync A prescribed bit pattern used as a
marker to enable systems to recognise
the start of system specific data
streams.
Table The STANAG 7023 documented
representation of a data file.
Target index number A unique number assigned to each
target to associate it with related
target information tables.
Tick The user defined unit of time for the
system.
Tile A rectangular area of a frame
described by the number of lines and
the number of samples per line.
Time tag A counter used by the system. The
Tick sets the incremental rate.
Used for time sequencing data.
WARNING NOTICE Some tables associated with multi-
spectral sensors and images are in
their infancy and may be subject to
change in future Editions. These
tables have been marked with a
suitable WARNING NOTICE.

NATO/PfP UNCLASSIFIED
(RELEASABLE FOR INTERNET TRANSMISSION)

132