SIST EN 16604-30-03:2020
(Main)Space - Space Situational Awareness Monitoring - Part 30-03: Observation System Data Message (OSDM)
Space - Space Situational Awareness Monitoring - Part 30-03: Observation System Data Message (OSDM)
1.1 Purpose:
The Observing System Data Message (OSDM) is a standard message format to be used in the exchange of optical telescope, laser ranging station, and radar (observing systems) information between Space situational Awareness (SSA) data providers, owners/operators of observing systems, and other parties. These messages can inform SSA data providers, which are the consumers of observing system output data, on the parameters of the observing systems.
The OSDM standard will:
a) enable consistent data exchange between observation data providers and SSA systems;
b) facilitate data exchange automation and ingestion of observation data from different providers;
c) facilitate SSA system architecture performance simulations; and
d) provide a quick way to estimate the expected performance from one observing system.
1.2 Applicability:
The Observing System Data Message standard is applicable to all SSA activities, especially Space Surveillance and Tracking (SST) and near-Earth objects (NEO), and other fields where the acquisition of astrometric and photometric data plays a role (e.g. space debris, observational astronomy). The standard contains a message designed to contain observing system parameters exchanged between producers and consumers of astrometric and/or photometric data. These data include observing system name, location, type (optical/radar), operator and tracking/survey performance.
The OSDM is suitable for both manual and automated interaction, but will not contain a large amount of data. The message is self contained and can be paired with several Tracking Data Messages (TDM – specified reference [1]), FITS images (specified in reference [2]), or other formats containing the observation data.
The OSDM standard only applies to the message format, structure and content. The exchange method is beyond the scope of the standard, and it is due to be specified in an ICD, though an ICD is not always required. The methods used to produce the data in the message are also beyond the scope of the standard.
1.3 Document structure:
Clause 5 provides an overview of the OSDM.
Clause 6 described the structure and content of the 'keyword = value' (KVN) version of the OSDM.
Clause 7 described the strucuture and content of the XML version of the OSDM.
Clause 8 describes the data and syntax of OSDM messages, in both KVN and XML.
Annex A lists agreed values for some of the OSDM keywords.
Annex B presents some examples of OSDMs.
Raumfahrt - Überwachung der Weltraumlageerfassung - Teil 30-03: Beobachtungssystembeschreibungs-Nachricht
1.1 Zweck
OSDM (en: Observing System Data Message) bezeichnet ein Standardnachrichtenformat, das für den Austausch von Informationen von optischen Teleskopen, Stationen für Laserentfernungsmessungen und Radars (Beobachtungssystemen) zwischen SSA-Datenanbietern (en: Space Situational Awareness, Weltraumlageerfassung), Eignern/Betreibern von Beobachtungssystemen und anderen Beteiligten zu verwenden ist. Mithilfe dieser Nachrichten können SSA-Datenanbieter, welche die Verbraucher von Ausgangsdaten von Beobachtungssystemen sind, über die Parameter der Beobachtungssysteme informiert werden.
Durch die OSDM-Norm wird Folgendes erreicht:
a) einheitlicher Datenaustausch zwischen Beobachtungsdatenanbietern und SSA-Systemen;
b) einfachere Automatisierung des Datenaustausches und einfachere Aufnahme von Beobachtungsdaten verschiedener Anbieter;
c) einfachere Simulation der Leistung von SSA-Systemarchitekturen;
d) schnellere Einschätzung der erwarteten Leistung eines einzigen Beobachtungssystems.
1.2 Anwendbarkeit
Die OSDM-Norm ist auf alle Aktivitäten zur Weltraumlageerfassung (SSA) anwendbar, insbesondere auf die Weltraumüberwachung und Bahnverfolgung (en: Space Surveillance and Tracking, SST) und auf erdnahe Objekte (en: near-Earth objects, NEO) sowie auf andere Bereiche, in denen die Aufzeichnung von astrometrischen und photometrischen Daten eine Rolle spielt (z. B. Weltraumschrott, beobachtende Astronomie). Die Norm beschreibt eine Nachricht, die dafür vorgesehen ist, Parameter eines Beobachtungssystems zu enthalten, die zwischen Erzeugern und Verbrauchern von astrometrischen und/oder photometrischen Daten ausgetauscht werden. Zu diesen Daten gehören Name, Standort, Art (optisch/Radar), Betreiber und Trackings-/Durchmusterungsleistung des Beobachtungs¬systems.
Die OSDM eignet sich sowohl für die manuelle als auch für die automatisierte Interaktion, enthält jedoch keine große Datenmengen. Die Nachricht ist in sich geschlossen und kann mit mehreren TDM-Nachrichten (siehe Verweisung [1]), FITS-Bildern (siehe Verweisung [2]) oder anderen Formaten, die Beobachtungs-daten enthalten, kombiniert werden.
Die OSDM-Norm bezieht sich nur auf das Nachrichtenformat, die Struktur und den Inhalt. Das Austauschverfahren liegt außerhalb des Anwendungsbereichs dieser Norm und wird voraussichtlich in einem ICD festgelegt werden, auch wenn ein ICD nicht immer gefordert wird. Die Verfahren zur Erzeugung der Daten in der Nachricht liegen auch außerhalb des Anwendungsbereichs dieser Norm.
1.3 Aufbau des Dokuments
Abschnitt 5 gibt einen Überblick über OSDM.
Abschnitt 6 beschreibt die Struktur und den Inhalt der KVN-Version (‚keyword = value‘) der OSDM.
Abschnitt 7 beschreibt die Struktur und den Inhalt der XML-Version der OSDM.
In Abschnitt 8 sind die Daten und die Syntax von OSDM-Nachrichten sowohl in KVN als auch in XML beschrieben.
Anhang A führt vereinbarte Werte für einige der OSDM-Schlüsselwörter auf.
Anhang B enthält einige Beispiele für OSDMs.
Espace - Surveillance de la représentation situationnelle de l'espace - Partie 30-03 : Message de données des systèmes d'observation (OSDM)
1.1 Objet
Le message de données du système d'observation (OSDM, Observing System Data Message) est un format de message normalisé servant à échanger des informations sur les télescopes optiques, les stations de télémétrie laser et les radars (systèmes d'observation) entre les fournisseurs de données de représentation situationnelle de l'espace (SSA, Space Situational Awareness), les propriétaires et opérateurs de systèmes d'observation, et les autres parties. Ces messages peuvent servir à communiquer des informations sur les paramètres des systèmes d'observation aux fournisseurs de données SSA (qui sont les consommateurs des données de sortie du système d'observation).
La norme OSDM :
a) permettra un échange de données cohérent entre les fournisseurs de données d'observation et les systèmes SSA ;
b) facilitera l'automatisation des échanges de données et l'importation de données d'observation provenant de différents fournisseurs ;
c) simplifiera les simulations de performance de l'architecture des systèmes SSA ; et
d) fournira un moyen rapide d'estimer les performances attendues d'un système d'observation.
1.2 Applicabilité
La norme sur les messages de données du système d'observation s'applique à toutes les activités SSA, notamment la surveillance de l'espace et le suivi des objets en orbite (SST) ainsi que les objets géocroiseurs (NEO), et à d'autres domaines où intervient l'acquisition de données astrométriques et photométriques (par exemple, débris spatiaux, astronomie d'observation). La norme présente un message destiné à contenir les paramètres du système d'observation échangés entre les producteurs et les consommateurs de données astrométriques et/ou photométriques. Ces données comprennent le nom du système d'observation, l'emplacement, le type (optique/radar), l'opérateur et les performances du suivi ou de l'étude.
L'OSDM convient aux interactions manuelles et automatisées, mais ne contient pas une grande quantité de données. Le message est autonome et peut être associé à plusieurs messages de données de suivi (TDM – voir référence bibliographique [1]), à des images FITS (voir référence bibliographique [2]) ou à d'autres formats contenant des données d'observation.
La norme OSDM s'applique uniquement au format, à la structure et au contenu du message. La méthode d'échange dépasse le cadre de la norme et elle doit être spécifiée dans un DCI, même si un DCI n'est pas toujours nécessaire. Les méthodes utilisées pour produire les données contenues dans un message dépassent également le cadre de la norme.
1.3 Structure du document
L’Article 5 fournit une vue d'ensemble de l’OSDM.
L’Article 6 décrit la structure et le contenu de la version KVN (notation « mot-clé = valeur ») de l'OSDM.
L’Article 7 décrit la structure et le contenu de la version XML de l'OSDM.
L’Article 8 présente les données et la syntaxe des messages OSDM, au format KVN et XML.
L’Annexe A fournit une liste des valeurs convenues pour certains mots-clés utilisés dans les messages OSDM.
L’Annexe B présente quelques exemples d'OSDM.
Vesolje - Nadzorovanje in spremljanje razmer v vesolju - 30-03. del: Sporočilo o podatkih opazovalnega sistema
General Information
Standards Content (Sample)
SLOVENSKI STANDARD
SIST EN 16604-30-03:2020
01-oktober-2020
Vesolje - Nadzorovanje in spremljanje razmer v vesolju - 30-03. del: Sporočilo o
podatkih opazovalnega sistema
Space - Space Situational Awareness Monitoring - Part 30-03: Observation System Data
Message (OSDM)
Raumfahrt - Überwachung der Weltraumlageerfassung - Teil 30-03:
Beobachtungssystembeschreibungs-Nachricht
Espace - Surveillance de la représentation situationnelle de l'espace - Partie 30-03 :
Message de données des systèmes d'observation (OSDM)
Ta slovenski standard je istoveten z: EN 16604-30-03:2020
ICS:
35.240.99 Uporabniške rešitve IT na IT applications in other fields
drugih področjih
49.140 Vesoljski sistemi in operacije Space systems and
operations
SIST EN 16604-30-03:2020 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
SIST EN 16604-30-03:2020
---------------------- Page: 2 ----------------------
SIST EN 16604-30-03:2020
EUROPEAN STANDARD
EN 16604-30-03
NORME EUROPÉENNE
EUROPÄISCHE NORM
July 2020
ICS 35.240.99; 49.140
English version
Space - Space Situational Awareness Monitoring - Part 30-
03: Observation System Data Message (OSDM)
Espace - Surveillance de la représentation Raumfahrt - Überwachung der Weltraumlageerfassung
situationnelle de l'espace - Partie 30-03 : Message de - Teil 30-03: Beobachtungssystembeschreibungs-
données des systèmes d'observation (OSDM) Nachricht
This European Standard was approved by CEN on 17 May 2020.
CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for
giving this European Standard the status of a national standard without any alteration. Up-to-date lists and bibliographical
references concerning such national standards may be obtained on application to the CEN-CENELEC Management Centre or to
any CEN and CENELEC member.
This European Standard exists in three official versions (English, French, German). A version in any other language made by
translation under the responsibility of a CEN and CENELEC member into its own language and notified to the CEN-CENELEC
Management Centre has the same status as the official versions.
CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy,
Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of North Macedonia, Romania, Serbia,
Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
CEN-CENELEC Management Centre:
Rue de la Science 23, B-1040 Brussels
© 2020 CEN/CENELEC All rights of exploitation in any form and by any means Ref. No. EN 16604-30-03:2020 E
reserved worldwide for CEN national Members and for
CENELEC Members.
---------------------- Page: 3 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
Contents Page
European foreword . 4
1 Scope . 5
2 Normative references . 6
3 Terms and definitions . 6
4 Abbreviated terms and unit conventions . 6
4.1 Abbreviated terms . 6
4.2 Unit conventions . 7
5 Overview . 8
6 Observing System Data Message structure and content in KVN . 8
6.1 General . 8
6.1.1 OSDM contents . 8
6.1.2 OSDM KVN contents . 8
6.1.3 OSDM file naming . 9
6.1.4 OSDM exchange method . 9
6.2 OSDM Header . 9
6.3 OSDM Metadata . 10
6.3.1 OSDM metadata lines . 10
6.3.2 OSDM metadata mandatory and optional keywords . 10
6.4 OSDM data . 12
6.4.1 OSDM data contents . 12
6.4.2 OSDM data lines . 12
6.4.3 OSDM data logical block headings . 23
6.4.4 OSDM data comment lines . 23
6.4.5 Location logical block . 23
6.4.6 Radar, SLR and telescope logical blocks . 23
6.4.7 Radar performance . 23
6.4.8 Radar duty cycle . 23
6.4.9 Observing system pointing capabilities . 23
6.4.10 Radar, SLR, and telescope parameters keywords . 24
6.4.11 SNR units . 24
6.4.12 Multi-static sensors . 25
7 The OSDM in XML . 25
7.1 General – The OSDM/XML schema . 25
7.1.1 Applicability . 25
7.1.2 The OSDM/XML schema . 25
7.1.3 Data types and relationship with CCSDS Navigation Data Messages . 25
7.2 OSDM/XML basic structure . 25
7.2.1 Structure of an OSDM in XML . 25
7.2.2 Structure of an OSDM body in XML . 25
7.2.3 Structure of an OSDM segment in XML . 25
7.3 OSDM/XML tags . 25
7.3.1 KVN keyword tag case . 25
7.3.2 XML message structure case . 26
7.4 Constructing an OSDM/XML instance . 26
7.4.1 General . 26
2
---------------------- Page: 4 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
7.4.2 XML version . 26
7.4.3 The root data element . 26
7.4.4 OSDM/XML header section . 26
7.4.5 OSDM/XML body section . 27
7.4.6 The OSDM/XML metadata section . 27
7.4.7 The OSDM/XML data section . 27
7.4.8 Units in the OSDM/XML . 28
7.4.9 Local operations . 28
8 Observing System Data Message data and syntax . 28
8.1 Common OSDM syntax . 28
8.1.1 OSDM lines . 28
8.1.2 OSDM values . 29
8.1.3 OSDM units . 29
8.1.4 OSDM comments . 29
8.2 The OSDM in KVN . 30
8.2.1 OSDM lines in KVN . 30
8.2.2 OSDM keywords in KVN . 30
8.2.3 OSDM units in KVN . 32
8.2.4 OSDM comments in KVN . 32
8.3 The OSDM in XML . 32
8.3.1 OSDM lines in XML . 32
8.3.2 OSDM values in XML . 32
8.3.3 OSDM/XML comments . 33
Annex A (normative) Values for the LOCATION_TYPE, REF_FRAME, SURVEY_TYPE,
TRACKING_TYPE, and OUTPUT_DATA_TYPES keywords . 34
Annex B (informative) Observing System Data Message examples . 37
Bibliography . 43
3
---------------------- Page: 5 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
European foreword
This document (EN 16604-30-03:2020) has been prepared by Technical Committee CEN/CLC/JTC 5
“Space”, the secretariat of which is held by DIN.
This European Standard shall be given the status of a national standard, either by publication of an
identical text or by endorsement, at the latest by January 2021, and conflicting national standards shall
be withdrawn at the latest by January 2021.
Attention is drawn to the possibility that some of the elements of this document may be the subject of
patent rights. CEN shall not be held responsible for identifying any or all such patent rights.
This document has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association.
According to the CEN-CENELEC Internal Regulations, the national standards organisations of the
following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria,
Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland,
Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Republic of
North Macedonia, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the
United Kingdom.
4
---------------------- Page: 6 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
1 Scope
1.1 Purpose:
The Observing System Data Message (OSDM) is a standard message format to be used in the exchange
of optical telescope, laser ranging station, and radar (observing systems) information between Space
Situational Awareness (SSA) data providers, owners/operators of observing systems, and other parties.
These messages can inform SSA data providers, which are the consumers of observing system output
data, on the parameters of the observing systems.
The OSDM standard will:
a) enable consistent data exchange between observation data providers and SSA systems;
b) facilitate data exchange automation and ingestion of observation data from different providers;
c) facilitate SSA system architecture performance simulations; and
d) provide a quick way to estimate the expected performance from one observing system.
1.2 Applicability:
The Observing System Data Message standard is applicable to all SSA activities, especially Space
Surveillance and Tracking (SST) as well as near-Earth objects (NEO), and other fields where the
acquisition of astrometric and photometric data plays a role (e.g. space debris, observational
astronomy). The standard contains a message designed to contain observing system parameters
exchanged between producers and consumers of astrometric and/or photometric data. These data
include observing system name, location, type (optical/radar), operator and tracking/survey
performance.
The OSDM is suitable for both manual and automated interaction, but will not contain a large amount of
data. The message is self contained and can be paired with several Tracking Data Messages (TDM –
specified reference [1]), FITS images (specified in reference [2]), or other formats containing the
observation data.
The OSDM standard only applies to the message format, structure and content. The exchange method is
beyond the scope of the standard, and it is due to be specified in an ICD, though an ICD is not always
required. The methods used to produce the data in the message are also beyond the scope of the
standard.
1.3 Document structure:
Clause 5 provides an overview of the OSDM.
Clause 6 described the structure and content of the 'keyword = value' (KVN) version of the OSDM.
Clause 7 described the structure and content of the XML version of the OSDM.
Clause 8 describes the data and syntax of OSDM messages, in both KVN and XML.
Annex A lists agreed values for some of the OSDM keywords.
Annex B presents some examples of OSDMs.
5
---------------------- Page: 7 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 17107, Space data and information transfer systems — XML specification for navigation data
messages
Paul V. Biron and Ashok Malhotra, eds. XML Schema Part 2: Datatypes. 2nd ed. W3C Recommendation.
N.p.: W3C, October 2004
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
— IEC Electropedia: available at http://www.electropedia.org/
— ISO Online browsing platform: available at http://www.iso.org/obp
NOTE For more information on terms and nomenclature, the CEN/CENELEC SST/NEO glossary of terms [3]
will be consulted.
3.1
observation
unique measurement of an object's location from a single observing system at a single time
EXAMPLE azimuth from a single radar at a single time
3.2
observing system
system (telescope, radar or SLR station) capable of acquiring observations (usually called 'sensor' in
SST)
4 Abbreviated terms and unit conventions
4.1 Abbreviated terms
The following abbreviated terms will be used in this document:
ASCII American Standard Code for Information Interchange
CCSDS Consultative Committee for Space Data Systems
ID IDentifier
ISO International Organization for Standardization
KVN Keyword Value Notation
n/a not applicable or not available
NEO Near Earth Object(s)
6
---------------------- Page: 8 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
OD Orbit Determination
SANA Space Assigned Numbers Authority
SLR Satellite Laser Ranging
SSA Space Situational Awareness
SST Space Surveillance and Tracking
TDM Tracking Data Message
UTC Coordinated Universal Time
XML eXtensible Markup Language
4.2 Unit conventions
The OSDM generally uses units that are part of the International System of Units (SI), either base,
derived, or non-SI units that are accepted for use within the SI (see [4]). The following units are used in
the OSDM:
— km: kilometres;
— m: metres;
— mm: millimetre;
— mcm: micrometre;
— nm: nanometre;
— h: hour (3600 s);
— s: second;
— ps: picosecond;
— K: kelvin;
— dB: decibel;
— Hz: hertz;
— kW: kilowatt;
— mJ: millijoule;
— deg: degree of arc; and
— arcsec: second of arc.
The following conventions are used for compound units:
— a single asterisk for multiplication: '*' (eg 'kg*s');
7
---------------------- Page: 9 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
— a single forward slash for division: '/' (eg 'm/s'); and
— a double asterisk for exponents: '**' (eg 'mm**2').
The usual mathematical conventions for operation order apply.
5 Overview
The OSDM is an ASCII format file, encode as either plain text (referred to as KVN – Keyword Value
Notation) or XML (see Paul V. Biron and Ashok Malhotra, eds. XML Schema Part 2: Datatypes, and also
Bibliographical Entries [5] and [6]).
The OSDM contains information about one observing system:
— information about the message itself (creation date, creator, etc.);
— identification of the observing system (name, owner, operator, etc.);
— reference performance (success rate, MTBF, etc.);
— observing system location (whether ground-based or in orbit, x/y/z, etc.); and
— observing system performance parameters (max elevation, minimum Sun/Moon distance, etc.).
This type of information is used by SSA operators, space agencies and spacecraft operators to determine
proper OD configuration or to simulate observing system performance. The OSDM can be used for
passive optical telescopes, SLR stations, and radars; both on ground and in orbit.
6 Observing System Data Message structure and content in KVN
6.1 General
6.1.1 OSDM contents
The OSDM shall be plain text consisting of information on one observing system. It shall be readable by
both humans and computers.
6.1.2 OSDM KVN contents
The OSDM in KVN shall consist of digital data represented as ASCII text lines. The OSDM shall contain:
a) a header; and
b) a metadata/data section.
8
---------------------- Page: 10 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
NOTE
1) KVN messages contain one keyword per line (see 8.2.1.4).
2) The standard order of keywords in the KVN representation is fixed in this standard, as listed in Tables 1, 2,
and 3 (see 8.2.1.7).
6.1.3 OSDM file naming
A naming scheme should be agreed on a case-by-base basis between the entities exchanging the
message. The file name syntax and length shall not violate the computer environment contraints.
6.1.4 OSDM exchange method
The OSDM exchange method should be determined on a case-by-case basis and should be documented
in an ICD.
6.2 OSDM Header
The header shall only consist of the KVN elements defined in Table 1, which specifies for each element:
a) the keyword;
b) a short description;
c) examples of allowed values; and
d) whether the keyword is mandatory (M) or optional (O).
9
---------------------- Page: 11 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
Table 1 — OSDM KVN header
Keyword Description of values Example of values M/O
CEN_OSDM_VERS Format version in the form of ‘x.y’, where ‘y’ is 0.6 M
incremented for corrections and minor changes,
1.0
and ‘x’ is incremented for major changes.
COMMENT Comments (allowed in the SDM Header only COMMENT This is a O
immediately after the SDM version number). comment
CREATION_DATE File creation date and time in UTC. For format 2001–11– M
specification see 8.2.2.5. 06T11:17:33
2002–204T15:56:23
ORIGINATOR Creating agency or operator. If the originator is CNES, ESOC, GSFC, M
listed in the SANA organizations registry [7], the GSOC, JPL, JAXA,
value should be taken from the abbreviation INTELSAT/USA
column there. The country of origin should also be
provided where the originator is not a national
space agency.
MESSAGE_ID ID that uniquely identifies a message from a given 20170823AA456 M
originator. The format and content of the message
identifier value are at the discretion of the
originator.
6.3 OSDM Metadata
6.3.1 OSDM metadata lines
The OSDM metadata shall only consist of the KVN elements defined in Table 2, where the following are
specified:
a) keyword;
b) a short description;
c) normative values or example of values;
d) whether the values listed are normative (N – all the values allowed are present in the third column)
or examples (E); and
e) whether the keyword is mandatory (M) or optional (O).
6.3.2 OSDM metadata mandatory and optional keywords
Mandatory keywords shall appear in every OSDM's metadata section. Optional keywords may or may
not appear, based on the message producer's requirements and the particular application.
10
---------------------- Page: 12 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
Table 2 — OSDM KVN metadata
Keyword Description of values Examples N/E M/O
COMMENT Comments (allowed only at COMMENT This is a E O
the beginning of the OSDM comment
metadata).
SYSTEM_NAME Observing system for which OGS TELESCOPE E M
the information is provided.
SPADE
SYSTEM_ID Observing system identifier IAC-80 E O
(if any exists):
2012–068A
— the COSPAR ID should be
used for an orbiting
sensor;
— The Observatory ID from
the IAU should be used
for ground-based
telescopes, if one exists.
SITE_NAME Name of the site where the TEIDE OBSERVATORY E O
observing system is located.
SITE_ID Identifier of the site where OAM1 E O
the observing system is
located (if any exists).
SYSTEM_TYPE Type of the observing ACTIVE OPTICAL N M
system: radar, optical
PASSIVE OPTICAL
telescope (passive optical),
RADAR
SLR station (active optical).
SYSTEM_OWNER Entity owning the observing ESA E M
system. If the originator is
IAC
listed in the SANA
Organizations Registry [7],
the value should be taken
from the abbreviation
column there. The country of
origin should also be
provided where the
originator is not a national
space agency.
11
---------------------- Page: 13 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
Keyword Description of values Examples N/E M/O
SYSTEM_OPERATOR Entity operating the ESA E M
observing system. If the
NASA
originator is listed in the
ESO
SANA Organizations Registry
[7], the value should be taken
from the abbreviation
column there. The country of
origin should also be
provided where the
originator is not a national
space agency.
OPERATOR_CONTACT_POSITION Position of the contact person STAFF ASTRONOMER E O
at the sensor operator.
NETWORK
CONTROLLER
OPERATOR_PHONE The contact person's phone +123456789 E O
number.
OPERATOR_EMAIL The contact person's email JOHN.DOE@ESA.NET E O
address.
6.4 OSDM data
6.4.1 OSDM data contents
The OSDM data section shall be formatted as logical blocks:
— reference performance;
— location;
— pointing performance and restrictions;
— radar parameters;
— telescope parameters;
— SLR parameters; and
— expected observation accuracy.
6.4.2 OSDM data lines
The logical blocks of the OSDM data section shall consist of KVN lines defined in Table 3, which
specifies:
a) keyword;
b) description of the content;
12
---------------------- Page: 14 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
c) units to be used; and
d) whether the keyword is mandatory (M), or optional (O).
NOTE Due to limited space some keywords are split into multiple lines. There are no line breaks in keywords
in OSDM messages.
Table 3 — OSDM KVN data
Keyword Description of values Examples units M/O
Reference performance and general capabilities
COMMENT Comments (allowed only at COMMENT This is a n/a O
the beginning of each OSDM comment
data logical block).
SUCCESS_RATE Statistical success rate of the 0.994 n/a O
observing system (0 to 1).
0.341
MTBF Mean Time Between Failures 3394494934 h O
in hours.
MTTR Mean Time To Recover from a 0.44 h O
failure in hours.
AVAILABILITY System availability (as a 100 % O
percentage of total
observation time) for the
intended task.
DATA_LATENCY Mean time between aquiring 2 h O
an observation and delivering
it in the OUTPUT_FORMAT to
the consumer (in hours).
OUTPUT_DATA_TYPES Comma separated list of the AZEL, RANGE n/a M
observation types the system
DOPPLER_INTEGRATED
can generate. Use of values
other than those listed in
Table A.5 in Annex A should
be documented in an ICD.
OUTPUT_FORMAT Comma separated list of the TDM n/a M
formats in which the
FITS
observations can be delivered.
INPUT_FORMAT The format the system can OEM, TLE n/a M
receive observation request,
TSM, OEM
either specific
PRM
scheduling/pointing or orbit
formats.
13
---------------------- Page: 15 ----------------------
SIST EN 16604-30-03:2020
EN 16604-30-03:2020 (E)
Keyword Description of values Examples units M/O
CORRECTIONS_APPLIED Comma-separated list of the ANNUAL ABERRATION, n/a M
corrections appl
...
SLOVENSKI STANDARD
oSIST prEN 16604-30-03:2019
01-september-2019
Vesolje - Nadzorovanje in spremljanje razmer v vesolju - 30-03. del: Sporočilo o
podatkih opazovalnega sistema
Space - Space Situational Awareness Monitoring - Part 30-03: Observation System Data
Message (OSDM)
Raumfahrt - Überwachung der Weltraumlageerfassung - Teil 30-03:
Beobachtungssystembeschreibungs-Nachricht
Ta slovenski standard je istoveten z: prEN 16604-30-03
ICS:
35.240.99 Uporabniške rešitve IT na IT applications in other fields
drugih področjih
49.140 Vesoljski sistemi in operacije Space systems and
operations
oSIST prEN 16604-30-03:2019 en,fr,de
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
---------------------- Page: 1 ----------------------
oSIST prEN 16604-30-03:2019
---------------------- Page: 2 ----------------------
oSIST prEN 16604-30-03:2019
EUROPEAN STANDARD
DRAFT
prEN 16604-30-03
NORME EUROPÉENNE
EUROPÄISCHE NORM
May 2019
ICS 35.240.99; 49.140
English version
Space - Space Situational Awareness Monitoring - Part 30-
03: Observation System Data Message (OSDM)
Raumfahrt - Überwachung der Weltraumlageerfassung
- Teil 30-03: Beobachtungssystembeschreibungs-
Nachricht
This draft European Standard is submitted to CEN members for enquiry. It has been drawn up by the Technical Committee
CEN/CLC/JTC 5.
If this draft becomes a European Standard, CEN and CENELEC members are bound to comply with the CEN/CENELEC Internal
Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any
alteration.
This draft European Standard was established by CEN and CENELEC in three official versions (English, French, German). A
version in any other language made by translation under the responsibility of a CEN and CENELEC member into its own
language and notified to the CEN-CENELEC Management Centre has the same status as the official versions.
CEN and CENELEC members are the national standards bodies and national electrotechnical committees of Austria, Belgium,
Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany,
Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania,
Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and United Kingdom.
Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are
aware and to provide supporting documentation.Recipients of this draft are invited to submit, with their comments, notification
of any relevant patent rights of which they are aware and to provide supporting documentation.
Warning : This document is not a European Standard. It is distributed for review and comments. It is subject to change without
notice and shall not be referred to as a European Standard.
---------------------- Page: 3 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
Contents Page
European foreword . 4
1 Scope . 5
2 Normative references . 6
3 Terms and definitions . 6
4 Abbreviated terms and unit conventions . 6
4.1 Abbreviated terms . 6
4.2 Unit conventions . 7
5 Overview . 8
6 Observing System Data Message structure and content in KVN . 8
6.1 General . 8
6.1.1 OSDM contents . 8
6.1.2 OSDM KVN contents . 8
6.1.3 OSDM file naming . 9
6.1.4 OSDM exchange method . 9
6.2 OSDM Header . 9
6.3 OSDM Metadata . 10
6.3.1 OSDM metadata lines . 10
6.3.2 OSDM metadata mandatory and optional keywords . 10
6.4 OSDM data . 12
6.4.1 OSDM data contents . 12
6.4.2 OSDM data lines . 12
6.4.3 OSDM data logical block headings . 23
6.4.4 OSDM data comment lines . 23
6.4.5 Location logical block . 23
6.4.6 Radar, SLR and telescope logical blocks . 23
6.4.7 Radar performance . 23
6.4.8 Radar duty cycle . 23
6.4.9 Observing system pointing capabilities . 23
6.4.10 Radar, SLR, and telescope parameters keywords . 24
6.4.11 SNR units . 24
6.4.12 Multi-static sensors . 24
7 The OSDM in XML . 25
7.1 General – The OSDM/XML schema . 25
7.1.1 Applicability . 25
7.1.2 The OSDM/XML schema . 25
7.1.3 Data types and relationship with CCSDS Navigation Data Messages . 25
7.2 OSDM/XML basic structure . 25
7.2.1 Structure of an OSDM in XML . 25
7.2.2 Structure of an OSDM body in XML . 25
7.2.3 Structure of an OSDM segment in XML . 25
7.3 OSDM/XML tags . 25
7.3.1 KVN keyword tag case . 25
7.3.2 XML message structure case . 26
7.4 Constructing an OSDM/XML instance . 26
7.4.1 General . 26
2
---------------------- Page: 4 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
7.4.2 XML version . 26
7.4.3 The root data element . 26
7.4.4 OSDM/XML header section . 26
7.4.5 OSDM/XML body section . 27
7.4.6 The OSDM/XML metadata section . 27
7.4.7 The OSDM/XML data section . 27
7.4.8 Units in the OSDM/XML . 28
7.4.9 Local operations . 28
8 Observing System Data Message data and syntax . 28
8.1 Common OSDM syntax . 28
8.1.1 OSDM lines . 28
8.1.2 OSDM values . 29
8.1.3 OSDM units . 29
8.1.4 OSDM comments . 29
8.2 The OSDM in KVN . 30
8.2.1 OSDM lines in KVN . 30
8.2.2 OSDM keywords in KVN . 30
8.2.3 OSDM units in KVN . 32
8.2.4 OSDM comments in KVN . 32
8.3 The OSDM in XML . 32
8.3.1 OSDM lines in XML . 32
8.3.2 OSDM values in XML . 32
8.3.3 OSDM/XML comments . 33
Annex A (normative) Values for the LOCATION_TYPE, REF_FRAME, SURVEY_TYPE,
TRACKING_TYPE, and OUTPUT_DATA_TYPES keywords . 34
Annex B (informative) Observing System Data Message examples . 37
Bibliography . 43
3
---------------------- Page: 5 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
European foreword
This document (prEN 16604-30-03:2019) has been prepared by Technical Committee CEN/CLC/JTC 5
“Space”, the secretariat of which is held by DIN.
This document is currently submitted to the CEN Enquiry.
This document has been prepared under a mandate given to CEN by the European Commission and the
European Free Trade Association.
4
---------------------- Page: 6 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
1 Scope
1.1 Purpose:
The Observing System Data Message (OSDM) is a standard message format to be used in the exchange
of optical telescope, laser ranging station, and radar (observing systems) information between Space
situational Awareness (SSA) data providers, owners/operators of observing systems, and other parties.
These messages can inform SSA data providers, which are the consumers of observing system output
data, on the parameters of the observing systems.
The OSDM standard will:
a) enable consistent data exchange between observation data providers and SSA systems;
b) facilitate data exchange automation and ingestion of observation data from different providers;
c) facilitate SSA system architecture performance simulations; and
d) provide a quick way to estimate the expected performance from one observing system.
1.2 Applicability:
The Observing System Data Message standard is applicable to all SSA activities, especially Space
Surveillance and Tracking (SST) and near-Earth objects (NEO), and other fields where the acquisition of
astrometric and photometric data plays a role (e.g. space debris, observational astronomy). The
standard contains a message designed to contain observing system parameters exchanged between
producers and consumers of astrometric and/or photometric data. These data include observing
system name, location, type (optical/radar), operator and tracking/survey performance.
The OSDM is suitable for both manual and automated interaction, but will not contain a large amount of
data. The message is self contained and can be paired with several Tracking Data Messages (TDM –
specified reference [1]), FITS images (specified in reference [2]), or other formats containing the
observation data.
The OSDM standard only applies to the message format, structure and content. The exchange method is
beyond the scope of the standard, and it is due to be specified in an ICD, though an ICD is not always
required. The methods used to produce the data in the message are also beyond the scope of the
standard.
1.3 Document structure:
Clause 5 provides an overview of the OSDM.
Clause 6 described the structure and content of the 'keyword = value' (KVN) version of the OSDM.
Clause 7 described the strucuture and content of the XML version of the OSDM.
Clause 8 describes the data and syntax of OSDM messages, in both KVN and XML.
Annex A lists agreed values for some of the OSDM keywords.
Annex B presents some examples of OSDMs.
5
---------------------- Page: 7 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any amendments) applies.
ISO 11104:2011, Space data and information transfer systems – Time code formats (CCSDS 301.0-B-4)
ISO 17107, Space data and information transfer systems – XML specification for navigation data messages
(CCSDS)
nd
PAUL V. Biron and Ashok Malhotra, eds. XML Schema Part 2: Datatypes. 2 ed. W3C Recommendation.
N.p.: W3C, October 2004
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
ISO and IEC maintain terminological databases for use in standardization at the following addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
NOTE For more information on terms and nomenclature, the CEN/CENELEC SST/NEO glossary of terms [3]
will be consulted.
3.1
observation
unique measurement of an object's location from a single observing system at a single time
(e.g. azimuth from a single radar at a single time)
3.2
observing system
system (telescope, radar or SLR station) capable of acquiring observations (usually called 'sensor' in
SST)
3.3
sensor track
set of at least three observations for the same object, from the same observing system, and with each
observation withing a specified number of minutes of the other observations in the track (depends on
the object's orbit)
4 Abbreviated terms and unit conventions
4.1 Abbreviated terms
The following abbreviated terms will be used in this document:
ASCII American Standard Code for Information Exchange
CCSDS Consultative Committee for Space Data Systems
ID IDentifier
6
---------------------- Page: 8 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
ISO International Organization for Standardization
KVN Keyword Value Notation
n/a not applicable or not available
NEO Near Earth Object(s)
OD Orbit Determination
SANA Space Assigned Numbers Authority
SLR Satellite Laser Ranging
SSA Space Situtational Awareness
SST Space Surveillance and Tracking
TDM Tracking Data Message
UTC Coordinated Universal Time
XML eXtensible Markup Language
4.2 Unit conventions
The OSDM generally uses units that are part of the International System of Units (SI), either base,
derived, or non-SI units that are accepted for use within the SI (see [4]). The following units are used in
the OSDM:
— km: kilometres;
— m: metres;
— mm: millimetre;
— mcm: micrometre;
— nm: nanometre;
— h: hour (3600 s);
— s: second;
— ps: picosecond;
— K: kelvin;
— dB: decibel;
— Hz: hertz;
— kW: kilowatt;
— mJ: millijoule;
7
---------------------- Page: 9 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
— deg: degree of arc; and
— arcsec: second of arc.
The following conventions are used for compound units:
— a single asterisk for multiplication: '*' (eg 'kg*s');
— a single forward slash for division: '/' (eg 'm/s'); and
— a double asterisk for exponents: '**' (eg 'mm**2').
The usual mathematical conventions for operation order apply.
5 Overview
The OSDM is an ASCII format file, encode as either plain text (referred to as KVN – Keyword Value
Notation) or XML (see Paul V. Biron and Ashok Malhotra, eds. XML Schema Part 2: Datatypes, and also
Bibliographical Entries [5] and [6]).
The OSDM contains information about one observing system:
— information about the message itself (creation date, creator, etc.);
— identification of the observing system (name, owner, operator, etc.);
— reference performance (success rate, MTBF, etc.);
— observing system location (whether ground-based or in orbit, x/y/z, etc.); and
— observing system performance parameters (max elevation, minimum Sun/Moon distance, etc.).
This type of information is used by SSA operators, space agencies and spacecraft operators to determine
proper OD configuration or to simulate observing system performance. The OSDM can be used for
passive optical telescopes, SLR stations, and radars; both on ground and in orbit.
6 Observing System Data Message structure and content in KVN
6.1 General
6.1.1 OSDM contents
The OSDM shall be plain text consisting of information on one observing system. It shall be readable by
both humans and computers.
6.1.2 OSDM KVN contents
The OSDM in KVN shall consist of digital data represented as ASCII text lines. The OSDM shall contain:
a) a header; and
b) a metadata/data section.
8
---------------------- Page: 10 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
NOTE
1) KVN messages contain one keyword per line (see 8.2.1.4).
2) The standard order of keywords in the KVN representation is fixed in this standard, as listed in Tables 1, 2,
and 3 (see 8.2.1.7).
6.1.3 OSDM file naming
A naming scheme should be agreed on a case-by-base basis between the entities exchanging the
message. The file name syntax and length shall not violate the computer environment contraints.
6.1.4 OSDM exchange method
The OSDM exchange method should be determined on a case-by-case basis and should be documented
in an ICD.
6.2 OSDM Header
The header shall only consist of the KVN elements defined in Table 1, which specifies for each element:
a) the keyword;
b) a short description;
c) examples of allowed values; and
d) whether the keyword is mandatory (M) or optional (O).
9
---------------------- Page: 11 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
Table 1 — OSDM KVN header
Keyword Description of values Example of values M/O
CEN_OSDM_VERS Format version in the form of ‘x.y’, where ‘y’ is 0.6 M
incremented for corrections and minor changes,
1.0
and ‘x’ is incremented for major changes.
COMMENT Comments (allowed in the SDM Header only COMMENT This is a O
immediately after the SDM version number). comment
CREATION_DATE File creation date and time in UTC. For format 2001–11– M
specification see 8.2.2.5. 06T11:17:33
2002–204T15:56:23
ORIGINATOR Creating agency or operator. If the originator is CNES, ESOC, GSFC, M
listed in the SANA organizations registry [7], the GSOC, JPL, JAXA,
value should be taken from the abbreviation INTELSAT/USA
column there. The country of origin should also be
provided where the originator is not a national
space agency.
MESSAGE_ID ID that uniquely identifies a message from a given 20170823AA456 M
originator. The format and content of the message
identifier value are at the discretion of the
originator.
6.3 OSDM Metadata
6.3.1 OSDM metadata lines
The OSDM metadata shall only consist of the KVN elements defined in Table 2, where the following are
specified:
a) keyword;
b) a short description;
c) normative values or example of values;
d) whether the values listed are normative (N – all the values allowed are present in the third column)
or examples (E); and
e) whether the keyword is mandatory (M) or optional (O).
6.3.2 OSDM metadata mandatory and optional keywords
Mandatory keywords shall appear in every OSDM's metadata section. Optional keywords may or may
not appear, based on the message producer's requirements and the particular application.
10
---------------------- Page: 12 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
Table 2 — OSDM KVN metadata
Keyword Description of values Examples N/E M/O
COMMENT Comments (allowed only at COMMENT This is a E O
the beginning of the OSDM comment
metadata).
SYSTEM_NAME Observing system for which OGS TELESCOPE E M
the information is provided.
SPADE
SYSTEM_ID Observing system identifier IAC-80 E O
(if any exists):
2012–068A
— the COSPAR ID should be
used for an orbiting
sensor;
— The Observatory ID from
the IAU should be used
for ground-based
telescopes, if one exists.
SITE_NAME Name of the site where the TEIDE OBSERVATORY E O
observing system is located.
SITE_ID Identifier of the site where OAM1 E O
the observing system is
located (if any exists).
SYSTEM_TYPE Type of the observing ACTIVE OPTICAL N M
system: radar, optical
PASSIVE OPTICAL
telescope (passive optical),
RADAR
SLR station (active optical).
SYSTEM_OWNER Entity owning the observing ESA E M
system. If the originator is
IAC
listed in the SANA
Organizations Registry [7],
the value should be taken
from the abbreviation
column there. The country of
origin should also be
provided where the
originator is not a national
space agency.
SYSTEM_OPERATOR Entity operating the ESA E M
observing system. If the
NASA
11
---------------------- Page: 13 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
Keyword Description of values Examples N/E M/O
originator is listed in the ESO
SANA Organizations Registry
[7], the value should be taken
from the abbreviation
column there. The country of
origin should also be
provided where the
originator is not a national
space agency.
OPERATOR_CONTACT_POSITION Position of the contact person STAFF ASTRONOMER E O
at the sensor operator.
NETWORK
CONTROLLER
OPERATOR_PHONE The contact person's phone +123456789 E O
number.
OPERATOR_EMAIL The contact person's email JOHN.DOE@ESA.NET E O
address.
6.4 OSDM data
6.4.1 OSDM data contents
The OSDM data section shall be formatted as logical blocks:
— reference performance;
— location;
— pointing performance and restrictions;
— radar parameters;
— telescope parameters;
— SLR parameters; and
— expected observation accuracy.
6.4.2 OSDM data lines
The logical blocks of the OSDM data section shall consist of KVN lines defined in Table 3, which
specifies:
a) keyword;
b) description of the content;
c) units to be used; and
12
---------------------- Page: 14 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
d) whether the keyword is mandatory (M), or optional (O).
NOTE Due to limited space some keywords are split into multiple lines. There are no line breaks in keywords
in OSDM messages.
Table 3 — OSDM KVN data
Keyword Description of values Examples units M/O
Reference performance and general capabilities
COMMENT Comments (allowed only at COMMENT This is a n/a O
the beginning of each OSDM comment
data logical block).
SUCCESS_RATE Statistical success rate of the 0.994 n/a O
observing system (0 to 1).
0.341
MTBF Mean Time Between Failures 3394494934 h O
in hours.
MTTR Mean Time To Recover from a 0.44 h O
failure in hours.
AVAILABILITY System availability (as a 100 % O
percentage of total
observation time) for the
intended task.
DATA_LATENCY Mean time between aquiring 2 h O
an observation and delivering
it in the OUTPUT_FORMAT to
the consumer (in hours).
OUTPUT_DATA_TYPES Comma separated list of the AZEL, RANGE n/a M
observation types the system
DOPPLER_INTEGRATED
can generate. Use of values
other than those listed in
Table A.5 in Annex A should
be documented in an ICD.
OUTPUT_FORMAT Comma separated list of the TDM n/a M
formats in which the
FITS
observations can be delivered.
INPUT_FORMAT The format the system can OEM, TLE n/a M
receive observation request,
TSM, OEM
either specific
PRM
scheduling/pointing or orbit
formats.
13
---------------------- Page: 15 ----------------------
oSIST prEN 16604-30-03:2019
prEN 16604-30-03:2019 (E)
Keyword Description of values Examples units M/O
CORRECTIONS_APPLIED Comma-separated list of the ANNUAL ABERRATION, n/a M
corrections applied to the TIME BIAS
output data by the system.
Location
COMMENT Comments (allowed only at COMMENT This is a n/a O
the beginning of each OSDM comment
data logical block).
LOCATION_TYPE The sensor location type, GROUND-BASED n/a M
whether ground-based, in
ORBIT
orbit, or mounted on a ship or
SHIPBORNE
aeroplane. Values other than
AIRBORNE
those listed in Table A.1 in
Annex A should be
documented in an ICD.
CENTER_NAME The celestial body on which EARTH n/a M
the observing system is
MARS
located or which the
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.