ISO 22644:2006
(Main)Space data and information transfer systems — Orbit data messages
Space data and information transfer systems — Orbit data messages
ISO 22644:2006 specifies two standard message formats for use in transferring spacecraft orbit information between space Agencies: the Orbit Parameter Message (OPM) and the Orbit Ephemeris Message (OEM). Such exchanges are used for pre-flight planning for tracking or navigation support; scheduling tracking support; carrying out tracking operations (sometimes called metric predicts); performing orbit comparisons; carrying out navigation operations such as orbit propagation. ISO 22644:2006 includes sets of requirements and criteria that the message formats have been designed to meet. For exchanges where these requirements do not capture the needs of the participating Agencies, another mechanism may be selected.
Systèmes de transfert des informations et données spatiales — Messages pour données d'orbites
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 22644
First edition
2006-05-01
Space data and information transfer
systems — Orbit data messages
Systèmes de transfert des informations et données spatiales —
Messages pour données d'orbites
Reference number
ISO 22644:2006(E)
©
ISO 2006
---------------------- Page: 1 ----------------------
ISO 22644:2006(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
© ISO 2006
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO 2006 – All rights reserved
---------------------- Page: 2 ----------------------
ISO 22644:2006(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 22644 was prepared by the Consultative Committee for Space Data Systems (CCSDS) (as
CCSDS 502.0-B-1, September 2004) and was adopted (without modifications except those stated in Clause 2
of this International Standard) by Technical Committee ISO/TC 20, Aircraft and space vehicles, Subcommittee
SC 13, Space data and information transfer systems.
© ISO 2006 – All rights reserved iii
---------------------- Page: 3 ----------------------
INTERNATIONAL STANDARD ISO 22644:2006(E)
Space data and information transfer systems — Orbit data
messages
1 Scope
This International Standard specifies two standard message formats for use in transferring spacecraft orbit
information between space Agencies: the Orbit Parameter Message (OPM) and the Orbit Ephemeris Message
(OEM). Such exchanges are used for
⎯ pre-flight planning for tracking or navigation support;
⎯ scheduling tracking support;
⎯ carrying out tracking operations (sometimes called metric predicts);
⎯ performing orbit comparisons;
⎯ carrying out navigation operations such as orbit propagation.
This International Standard includes sets of requirements and criteria that the message formats have been
designed to meet. For exchanges where these requirements do not capture the needs of the participating
Agencies another mechanism may be selected.
The scope and field of application are furthermore detailed in subclauses 1.1 and 1.2 of the enclosed CCSDS
publication.
2 Requirements
Requirements are the technical recommendations made in the following publication (reproduced on the
following pages), which is adopted as an International Standard:
CCSDS 502.0-B-1, September 2004, Orbit data messages.
For the purposes of international standardization, the modifications outlined below shall apply to the specific
clauses and paragraphs of publication CCSDS 502.0-B-1.
Pages i to v
This part is information which is relevant to the CCSDS publication only.
Page 1-2
Add the following information to the reference indicated:
[1] CCSDS Green Books are now available at http://public.ccsds.org/publications/GreenBooks.aspx
© ISO 2006 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO 22644:2006(E)
3 Revision of publication CCSDS 502.0-B-1
It has been agreed with the Consultative Committee for Space Data Systems that Subcommittee
ISO/TC 20/SC 13 will be consulted in the event of any revision or amendment of publication CCSDS 502.0-B-1.
To this end, NASA will act as a liaison body between CCSDS and ISO.
2 © ISO 2006 – All rights reserved
---------------------- Page: 5 ----------------------
ISO 22644:2006(E)
Consultative
Committeefor
SpaceDataSystems
RECOMMENDATION FOR SPACE
DATA SYSTEM STANDARDS
ORBIT DATA
MESSAGES
CCSDS 502.0-B-1
BLUE BOOK
September 2004
© ISO 2006 – All rights reserved 3
---------------------- Page: 6 ----------------------
ISO 22644:2006(E)
(Blank page)
4 © ISO 2006 – All rights reserved
---------------------- Page: 7 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
AUTHORITY
Issue: Blue Book, Issue 1
Date: September 2004
Location: Electronic Ballot
This document has been approved for publication by the Management Council of the
Consultative Committee for Space Data Systems (CCSDS) and represents the consensus
technical agreement of the participating CCSDS Member Agencies. The procedure for
review and authorization of CCSDS Recommendations is detailed in the Procedures Manual
for the Consultative Committee for Space Data Systems (reference [5]), and the record of
Agency participation in the authorization of this document can be obtained from the CCSDS
Secretariat at the address below.
This Recommendation is published and maintained by:
CCSDS Secretariat
Office of Space Communication (Code M-3)
National Aeronautics and Space Administration
Washington, DC 20546, USA
CCSDS 502.0-B-1 Page i September 2004
© ISO 2006 – All rights reserved 5
---------------------- Page: 8 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
STATEMENT OF INTENT
The Consultative Committee for Space Data Systems (CCSDS) is an organization officially
established by the management of member space Agencies. The Committee meets
periodically to address data systems problems that are common to all participants, and to
formulate sound technical solutions to these problems. Inasmuch as participation in the
CCSDS is completely voluntary, the results of Committee actions are termed
Recommendations and are not considered binding on any Agency.
This Recommendation is issued by, and represents the consensus of, the CCSDS Plenary
body. Agency endorsement of this Recommendation is entirely voluntary. Endorsement,
however, indicates the following understandings:
– Whenever an Agency establishes a CCSDS-related standard, this standard will be in
accord with the relevant Recommendation. Establishing such a standard does not
preclude other provisions which an Agency may develop.
– Whenever an Agency establishes a CCSDS-related standard, the Agency will provide
other CCSDS member Agencies with the following information:
• The standard itself.
• The anticipated date of initial operational capability.
• The anticipated duration of operational service.
– Specific service arrangements are made via memoranda of agreement. Neither this
Recommendation nor any ensuing standard is a substitute for a memorandum of
agreement.
No later than five years from its date of issuance, this Recommendation will be reviewed by
the CCSDS to determine whether it should: (1) remain in effect without change; (2) be
changed to reflect the impact of new technologies, new requirements, or new directions; or,
(3) be retired or canceled.
In those instances when a new version of a Recommendation is issued, existing CCSDS-
related Agency standards and implementations are not negated or deemed to be non-CCSDS
compatible. It is the responsibility of each Agency to determine when such standards or
implementations are to be modified. Each Agency is, however, strongly encouraged to direct
planning for its new standards and implementations towards the later version of the
Recommendation.
CCSDS 502.0-B-1 Page ii September 2004
6 © ISO 2006 – All rights reserved
---------------------- Page: 9 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
FOREWORD
This document is a technical Recommendation for Orbit Data Messages (ODMs) and has
been prepared by the Consultative Committee for Space Data Systems (CCSDS). The set of
orbit data messages described in this Recommendation is the baseline concept for trajectory
representation in data interchange applications that are cross-supported between Agencies of
the CCSDS.
This Recommendation establishes a common framework and provides a common basis for
the interchange of orbit data. It allows implementing organizations within each Agency to
proceed coherently with the development of compatible derived standards for the flight and
ground systems that are within their cognizance. Derived Agency standards may implement
only a subset of the optional features allowed by the Recommendation and may incorporate
features not addressed by this Recommendation.
Through the process of normal evolution, it is expected that expansion, deletion or
modification to this document may occur. This Recommendation is therefore subject to
CCSDS document management and change control procedures, as defined in the Procedures
Manual for the Consultative Committee for Space Data Systems. Current versions of
CCSDS documents are maintained at the CCSDS web site:
http://www.ccsds.org/
Questions relating to the contents or status of this document should be addressed to the
CCSDS Secretariat at the address indicated on page i.
CCSDS 502.0-B-1 Page iii September 2004
© ISO 2006 – All rights reserved 7
---------------------- Page: 10 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
At time of publication, the active Member and Observer Agencies of the CCSDS were:
Member Agencies
– Agenzia Spaziale Italiana (ASI)/Italy.
– British National Space Centre (BNSC)/United Kingdom.
– Canadian Space Agency (CSA)/Canada.
– Centre National d’Etudes Spatiales (CNES)/France.
– Deutsches Zentrum für Luft- und Raumfahrt e.V. (DLR)/Germany.
– European Space Agency (ESA)/Europe.
– Federal Space Agency (FSA)/Russian Federation.
– Instituto Nacional de Pesquisas Espaciais (INPE)/Brazil.
– Japan Aerospace Exploration Agency (JAXA)/Japan.
– National Aeronautics and Space Administration (NASA)/USA.
Observer Agencies
– Austrian Space Agency (ASA)/Austria.
– Central Research Institute of Machine Building (TsNIIMash)/Russian Federation.
– Centro Tecnico Aeroespacial (CTA)/Brazil.
– Chinese Academy of Space Technology (CAST)/China.
– Commonwealth Scientific and Industrial Research Organization (CSIRO)/Australia.
– Communications Research Laboratory (CRL)/Japan.
– Danish Space Research Institute (DSRI)/Denmark.
– European Organization for the Exploitation of Meteorological Satellites
(EUMETSAT)/Europe.
– European Telecommunications Satellite Organization (EUTELSAT)/Europe.
– Federal Science Policy Office (FSPO)/Belgium.
– Hellenic National Space Committee (HNSC)/Greece.
– Indian Space Research Organization (ISRO)/India.
– Institute of Space Research (IKI)/Russian Federation.
– KFKI Research Institute for Particle & Nuclear Physics (KFKI)/Hungary.
– Korea Aerospace Research Institute (KARI)/Korea.
– MIKOMTEK: CSIR (CSIR)/Republic of South Africa.
– Ministry of Communications (MOC)/Israel.
– National Oceanic & Atmospheric Administration (NOAA)/USA.
– National Space Program Office (NSPO)/Taipei.
– Space and Upper Atmosphere Research Commission (SUPARCO)/Pakistan.
– Swedish Space Corporation (SSC)/Sweden.
– United States Geological Survey (USGS)/USA.
CCSDS 502.0-B-1 Page iv September 2004
8 © ISO 2006 – All rights reserved
---------------------- Page: 11 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
DOCUMENT CONTROL
Document Title and Issue Date Status
CCSDS Orbit Data Messages, September Current Issue
502.0-B-1 Issue 1 2004
CCSDS 502.0-B-1 Page v September 2004
© ISO 2006 – All rights reserved 9
---------------------- Page: 12 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
CONTENTS
Section Page
1 INTRODUCTION.1-1
1.1 PURPOSE. 1-1
1.2 SCOPE AND APPLICABILITY.1-1
1.3 CONVENTIONS AND DEFINITIONS.1-1
1.4 STRUCTURE OF THIS DOCUMENT.1-2
1.5 REFERENCES . 1-2
2 OVERVIEW.2-1
2.1 ORBIT DATA MESSAGE TYPES. 2-1
2.2 ORBIT PARAMETER MESSAGE (OPM) . 2-1
2.3 ORBIT EPHEMERIS MESSAGE (OEM) . 2-1
2.4 EXCHANGE OF MULTIPLE MESSAGES. 2-2
2.5 DEFINITIONS. 2-2
3 ORBIT PARAMETER MESSAGE (OPM) . 3-1
3.1 OVERVIEW . 3-1
3.2 OPM CONTENT . 3-1
3.3 OPM SYNTAX. 3-7
3.4 OPM EXAMPLES. 3-11
4 ORBIT EPHEMERIS MESSAGE (OEM).4-1
4.1 OVERVIEW . 4-1
4.2 OEM CONTENT . 4-1
4.3 OEM SYNTAX . 4-6
4.4 OEM EXAMPLE. 4-11
ANNEX A RATIONALE FOR ORBIT DATA MESSAGES. A-1
ANNEX B ITEMS FOR AN INTERFACE CONTROL DOCUMENT . B-5
ANNEX C ABBREVIATIONS AND ACRONYMS. C-6
CCSDS 502.0-B-1 Page vi September 2004
10 © ISO 2006 – All rights reserved
---------------------- Page: 13 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
CONTENTS (continued)
Figure Page
3-1 OPM File Example Using Comments to Denote Updates .3-11
3-2 OPM File Example with Optional Keplerian Elements and Two Maneuvers .3-12
4-1 OEM Example .4-11
Table Page
3-1 OPM Header.3-2
3-2 OPM Metadata. 3-3
3-3 OPM Data.3-5
4-1 OEM File Layout Specifications . 4-2
4-2 OEM Header.4-3
4-3 OEM Metadata .4-4
A-1 Primary Requirements . A-2
A-2 Heritage Requirements . A-3
A-3 Desirable Characteristics . A-3
A-4 Applicability of the Criteria to Orbit Data Codes. A-4
A-5 Services Available with Orbit Data Codes. A-4
CCSDS 502.0-B-1 Page vii September 2004
© ISO 2006 – All rights reserved 11
---------------------- Page: 14 ----------------------
ISO 22644:2006(E)
(Blank page)
12 © ISO 2006 – All rights reserved
---------------------- Page: 15 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
1 INTRODUCTION
1.1 PURPOSE
This Orbit Data Message (ODM) Recommendation specifies two standard message formats
for use in transferring spacecraft orbit information between space Agencies: the Orbit
Parameter Message (OPM) and the Orbit Ephemeris Message (OEM). Such exchanges are
used for:
a) pre-flight planning for tracking or navigation support;
b) scheduling tracking support;
c) carrying out tracking operations (sometimes called metric predicts);
d) performing orbit comparisons; and
e) carrying out navigation operations such as orbit propagation.
This Recommendation includes sets of requirements and criteria that the message formats
have been designed to meet. For exchanges where these requirements do not capture the
needs of the participating Agencies another mechanism may be selected.
1.2 SCOPE AND APPLICABILITY
This document contains two orbit data messages designed for applications involving data
interchange in space data systems. The rationale behind the design of each message is
described in Annex A and may help the application engineer to select a suitable message.
Definition of the orbit accuracy underlying a particular orbit message is outside of the scope
of this Recommendation and should be specified via Interface Control Document (ICD)
between data exchange participants. Applicability information specific to each orbit data
message format appears in sections 3 and 4, as well as in subsection A3.
This Recommendation is applicable only to the message format and content, but not to its
transmission. The transmission of the message between Agencies is outside the scope of this
document and should be specified in the ICD.
Description of the message formats based on the use of eXtensible Markup Language (XML)
is under investigation. It is anticipated that an XML schema will be defined by a future
Recommendation on the XML implementation of Navigation data messages.
1.3 CONVENTIONS AND DEFINITIONS
The following conventions apply throughout this Recommendation:
a) the words ‘shall’ and ‘must’ imply a binding and verifiable specification;
CCSDS 502.0-B-1 Page 1-1 September 2004
© ISO 2006 – All rights reserved 13
---------------------- Page: 16 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
b) the word ‘should’ implies an optional, but desirable, specification;
c) the word ‘may’ implies an optional specification;
d) the words ‘is’, ‘are’, and ‘will’ imply statements of fact.
1.4 STRUCTURE OF THIS DOCUMENT
Chapter 2 provides a brief overview of the CCSDS-recommended Orbit Data Message types,
the Orbit Parameter Message (OPM) and Orbit Ephemeris Message (OEM).
Chapter 3 provides details about the structure and content of the OPM.
Chapter 4 provides details about the structure and content of the OEM.
Annex A lists a set of requirements that were taken into consideration in the design of the
OPM and OEM, along with tables and discussion regarding the applicability of the two
message types to various navigation tasks/functions.
Annex B lists a number of items that should be covered in interagency Interface Control
Documents (ICD) prior to exchanging ODMs on a regular basis. There are several
statements throughout the document that refer to the desirability or necessity of such a
document; this annex lists all the suggested ICD items in a single place in the document.
Annex C is a list of abbreviations and acronyms applicable to the ODM.
1.5 REFERENCES
The following documents contain provisions which, through reference in this text, constitute
provisions of this Recommendation. At the time of publication, the editions indicated were
valid. All documents are subject to revision, and users of this Recommendation are
encouraged to investigate the possibility of applying the most recent editions of the
documents indicated below. The CCSDS Secretariat maintains a register of currently valid
CCSDS Recommendations.
[1] Navigation Data—Definitions and Conventions. Report Concerning Space Data
System Standards, CCSDS 500.0-G-1. Green Book. Issue 1. Washington, D.C.:
CCSDS, June 2001. [http://www.ccsds.org/green_books.html]
[2] Spacewarn Bulletin. Greenbelt, MD, USA: World Data Center for Satellite
Information: WDC-SI. [ http://nssdc.gsfc.nasa.gov/spacewarn ]
[3] Standard Frequencies and Time Signals. Volume 7 of Recommendations and Reports
of the CCIR: XVth Plenary Assembly. Geneva: CCIR,1990.
CCSDS 502.0-B-1 Page 1-2 September 2004
14 © ISO 2006 – All rights reserved
---------------------- Page: 17 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
[4] Information Technology—8-Bit Single-Byte Coded Graphic Character Sets—Part 1:
Latin Alphabet No. 1. International Standard, ISO/IEC 8859-1:1998. Geneva: ISO,
1998. [ http://www.iso.ch ]
[5] Procedures Manual for the Consultative Committee for Space Data Systems. CCSDS
A00.0-Y-9. Yellow Book. Issue 9. Washington, D.C.: CCSDS, November 2003.
[6] NASA/JPL Solar System Dynamics Group [ http://ssd.jpl.nasa.gov ].
[7] XML Schema Part 2: Datatypes, W3C Recommendation 02 May 2001,
http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
[8] IEEE Standard for Binary Floating-Point Arithmetic, IEEE Standard 754-1985, IEEE,
http://grouper.ieee.org/groups/754/
CCSDS 502.0-B-1 Page 1-3 September 2004
© ISO 2006 – All rights reserved 15
---------------------- Page: 18 ----------------------
ISO 22644:2006(E)
(Blank page)
16 © ISO 2006 – All rights reserved
---------------------- Page: 19 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
2 OVERVIEW
2.1 ORBIT DATA MESSAGE TYPES
Two CCSDS-recommended Orbit Data Messages (ODMs) are described in this
Recommendation: the Orbit Parameter Message (OPM) and the Orbit Ephemeris Message
(OEM).
The recommended orbit data messages are ASCII text format. While binary-based orbit data
message formats are computer efficient and minimize overhead on uplinked/downlinked data
streams, there are ground-segment applications for which an ASCII character-based message
is more appropriate. For example, when files or data objects are created using text editors or
word processors, ASCII character-based orbit data format representations are necessary.
They are also useful in transferring text files between heterogeneous computing systems,
because the ASCII character set is nearly universally used and is interpretable by all popular
systems. In addition, direct human-readable dumps of text files or objects to displays or
printers are possible without preprocessing. The penalty for this convenience is inefficiency.
NOTE As currently specified, an OPM or OEM file is to represent orbit data for a
single vehicle. It is possible that the architecture may support multiple vehicles per
file; this could be considered in the future.
2.2 ORBIT PARAMETER MESSAGE (OPM)
An OPM specifies the position and velocity of a single object at a specified epoch. This
message is suited to inter-agency exchanges that (1) involve automated interaction and/or
human interaction, and (2) do not require high-fidelity dynamic modeling.
The OPM requires the use of a propagation technique to determine the position and velocity
at times different from the specified epoch, leading to a higher level of effort for software
implementation than for the OEM. The OPM is fully self-contained; no additional
information is required.
The code allows for modeling of any number of maneuvers (as both finite and instantaneous
events) and simple modeling of solar radiation pressure and atmospheric drag. The attributes
of this code also make it suitable for applications such as exchanges by FAX or voice, or
applications where the message is to be frequently interpreted by humans.
2.3 ORBIT EPHEMERIS MESSAGE (OEM)
An OEM specifies the position and velocity of a single object at multiple epochs contained
within a specified time range. The OEM is suited to inter-agency exchanges that (1) involve
automated interaction (e.g., computer-to-computer communication where frequent, fast
CCSDS 502.0-B-1 Page 2-1 September 2004
© ISO 2006 – All rights reserved 17
---------------------- Page: 20 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
automated time interpretation and processing is required), and (2) require higher fidelity or
higher precision dynamic modeling than is possible with the OPM.
The OEM allows for dynamic modeling of any number of gravitational and non-gravitational
accelerations. The OEM requires the use of an interpolation technique to interpret the
position and velocity at times different from the tabular epochs. The OEM is fully self-
contained; no additional information is required.
2.4 EXCHANGE OF MULTIPLE MESSAGES
For a given object, multiple OPM or OEM messages may be provided in a message exchange
session to achieve ephemeris fidelity requirements. If ephemeris information for multiple
objects is to be exchanged, then multiple OPM or OEM files must be used.
2.5 DEFINITIONS
Definitions of time systems, reference frames and planetary models are provided in reference
[1].
CCSDS 502.0-B-1 Page 2-2 September 2004
18 © ISO 2006 – All rights reserved
---------------------- Page: 21 ----------------------
ISO 22644:2006(E)
CCSDS RECOMMENDATION FOR ORBIT DATA MESSAGES
3 ORBIT PARAMETER MESSAGE (OPM)
3.1 OVERVIEW
a) Orbit information may be exchanged between two participants by sending a state
vector (see reference [1]) for a specified epoch using an Orbit Parameter Message
(OPM). The message recipient must have an orbit propagator available that is
able to propagate the OPM state vector to compute the orbit at other desired
epochs. For this propagation, additional ancillary information (spacecraft
properties such as mass, area, and maneuver planning data, if applicable) shall be
included with the message.
b) The use of the OPM shall be applicable under the following conditions:
1) an orbit propagator must be run at the receiver’s site;
2) the receiver’s modeling of gravitational forces, solar radiation pressure,
atmospheric drag and thrust phases (see reference [1]) must fulfill accuracy
requirements established between the agencies.
c) The OPM shall be a text file consisting of orbit data for a single object. It shall be
easily readable by both humans and computers.
d) The OPM file naming scheme shall be agreed to on a case-by-case basis between
the participating Agencies, and should be documented in an Interface Control
Document (ICD). The method of exchanging OPMs shall be decided on a case-
by-case basis by the participating Agencies and documented in an ICD.
3.2 OPM CONTENT
The OPM shall be represented as a combination of the following:
a) a header;
b) metadata (dat
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.