Informējam, ka Sistēma pielāgota darbam ar interneta pārlūkprogrammu Internet Explorer (8. un jaunākām versijām) un Mozilla Firefox (3.6 un jaunākām versijām).
Izmantojot citu interneta pārlūkprogrammu, brīdinām, ka Sistēmas funkcionalitāte var tikt traucēta.
<p class="MsoNormal">This document specifies four standard message formats for use in transferring spacecraft orbit information between space agencies and <span style="color: black;">commercial or governmental spacecraft operators</span>:<span style="mso-spacerun: yes;"> </span>The Orbit Parameter Message (OPM), the Orbit Mean-Elements Message (OMM), the Orbit Ephemeris Message (OEM), and the Orbit Comprehensive Message (OCM).<span style="mso-spacerun: yes;"> </span>Such exchanges are used for:</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">a)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->pre-flight planning for tracking or navigation support;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">b)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->scheduling tracking support;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">c)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->carrying out tracking operations (sometimes called metric predicts);</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">d)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->performing orbit comparisons;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">e)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->carrying out navigation operations such as orbit propagation and orbit reconstruction;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">f)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->assessing mutual physical and electromagnetic interference among satellites orbiting the same celestial body (primarily Earth, Moon, and Mars at present);</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">g)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->performing orbit conjunction (collision avoidance) studies; and</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">h)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->developing and executing collaborative maneuvers to mitigate interference or enhance mutual operations.</p>
<p class="MsoNormal">This document includes sets of requirements and criteria that the message formats have been designed to meet.<span style="mso-spacerun: yes;"> </span>For exchanges in which these requirements do not capture the needs of the participating agencies and satellite operators, another mechanism may be selected.</p>
<p class="MsoNormal">This document is an international standard published under the auspices of CCSDS and International Standards Organization (ISO) Technical Committee 20, Subcommittee 13, developed jointly and in concert with the ISO TC20/SC14.<span style="mso-spacerun: yes;"> </span>As such, this CCSDS standard is also properly labeled as ISO 26900.</p>
<p class="MsoNormal">The recommended Orbit Data Message format is ASCII (reference <!-- [if supportFields]><span style='mso-element:field-begin'></span><span
style='mso-spacerun:yes'> </span>REF R_ISO_IEC_8859_1_1998 \h <span
style='mso-element:field-separator'></span><![endif]-->[<span style="mso-no-proof: yes;">4</span>]<!-- [if gte mso 9]><xml>
<w:data>08D0C9EA79F9BACE118C8200AA004BA90B02000000080000001600000052005F00490053004F005F004900450043005F0038003800350039005F0031005F0031003900390038000000</w:data>
</xml><![endif]--><!-- [if supportFields]><span style='mso-element:field-end'></span><![endif]-->).</p>
<p class="MsoNormal">This document describes both ‘Keyword = Value Notation’ (KVN) as well as Extensible Markup Language (XML) (reference <!-- [if supportFields]><span
style='mso-element:field-begin'></span>REF
R_505x0b3XMLSpecificationforNavigationDa \h<span style='mso-element:field-separator'></span><![endif]-->[<span style="mso-no-proof: yes;">5</span>]<!-- [if gte mso 9]><xml>
<w:data>08D0C9EA79F9BACE118C8200AA004BA90B02000000080000002800000052005F00350030003500780030006200330058004D004C00530070006500630069006600690063006100740069006F006E0066006F0072004E0061007600690067006100740069006F006E0044000000</w:data>
</xml><![endif]--><!-- [if supportFields]><span style='mso-element:field-end'></span><![endif]-->) formatted messages.<span style="mso-spacerun: yes;"> </span>Selection of KVN or XML format should be mutually agreed between message exchange partners.</p>
<p class="Notelevel1"><span style="mso-ansi-language: EN-US;">NOTE<span style="mso-tab-count: 1;"> </span>–<span style="mso-tab-count: 1;"> </span>As currently specified, an OPM, OMM, or OEM file is to represent orbit data for a single spacecraft, and the OCM is to represent orbit data for either a single spacecraft or single parent spacecraft of a parent/child spacecraft deployment scenario.<span style="mso-spacerun: yes;"> </span>It is possible that the architecture may support multiple spacecraft per file; this could be considered in the future.</span></p>
Reģistrācijas numurs (WIID)
85529
Darbības sfēra
<p class="MsoNormal">This document specifies four standard message formats for use in transferring spacecraft orbit information between space agencies and <span style="color: black;">commercial or governmental spacecraft operators</span>:<span style="mso-spacerun: yes;"> </span>The Orbit Parameter Message (OPM), the Orbit Mean-Elements Message (OMM), the Orbit Ephemeris Message (OEM), and the Orbit Comprehensive Message (OCM).<span style="mso-spacerun: yes;"> </span>Such exchanges are used for:</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">a)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->pre-flight planning for tracking or navigation support;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">b)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->scheduling tracking support;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">c)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->carrying out tracking operations (sometimes called metric predicts);</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">d)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->performing orbit comparisons;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">e)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->carrying out navigation operations such as orbit propagation and orbit reconstruction;</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">f)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->assessing mutual physical and electromagnetic interference among satellites orbiting the same celestial body (primarily Earth, Moon, and Mars at present);</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">g)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->performing orbit conjunction (collision avoidance) studies; and</p>
<p class="MsoList" style="mso-list: l0 level1 lfo1; tab-stops: list 36.0pt;"><!-- [if !supportLists]--><span style="mso-list: Ignore;">h)<span style="font: 7.0pt 'Times New Roman';"> </span></span><!--[endif]-->developing and executing collaborative maneuvers to mitigate interference or enhance mutual operations.</p>
<p class="MsoNormal">This document includes sets of requirements and criteria that the message formats have been designed to meet.<span style="mso-spacerun: yes;"> </span>For exchanges in which these requirements do not capture the needs of the participating agencies and satellite operators, another mechanism may be selected.</p>
<p class="MsoNormal">This document is an international standard published under the auspices of CCSDS and International Standards Organization (ISO) Technical Committee 20, Subcommittee 13, developed jointly and in concert with the ISO TC20/SC14.<span style="mso-spacerun: yes;"> </span>As such, this CCSDS standard is also properly labeled as ISO 26900.</p>
<p class="MsoNormal">The recommended Orbit Data Message format is ASCII (reference <!-- [if supportFields]><span style='mso-element:field-begin'></span><span
style='mso-spacerun:yes'> </span>REF R_ISO_IEC_8859_1_1998 \h <span
style='mso-element:field-separator'></span><![endif]-->[<span style="mso-no-proof: yes;">4</span>]<!-- [if gte mso 9]><xml>
<w:data>08D0C9EA79F9BACE118C8200AA004BA90B02000000080000001600000052005F00490053004F005F004900450043005F0038003800350039005F0031005F0031003900390038000000</w:data>
</xml><![endif]--><!-- [if supportFields]><span style='mso-element:field-end'></span><![endif]-->).</p>
<p class="MsoNormal">This document describes both ‘Keyword = Value Notation’ (KVN) as well as Extensible Markup Language (XML) (reference <!-- [if supportFields]><span
style='mso-element:field-begin'></span>REF
R_505x0b3XMLSpecificationforNavigationDa \h<span style='mso-element:field-separator'></span><![endif]-->[<span style="mso-no-proof: yes;">5</span>]<!-- [if gte mso 9]><xml>
<w:data>08D0C9EA79F9BACE118C8200AA004BA90B02000000080000002800000052005F00350030003500780030006200330058004D004C00530070006500630069006600690063006100740069006F006E0066006F0072004E0061007600690067006100740069006F006E0044000000</w:data>
</xml><![endif]--><!-- [if supportFields]><span style='mso-element:field-end'></span><![endif]-->) formatted messages.<span style="mso-spacerun: yes;"> </span>Selection of KVN or XML format should be mutually agreed between message exchange partners.</p>
<p class="Notelevel1"><span style="mso-ansi-language: EN-US;">NOTE<span style="mso-tab-count: 1;"> </span>–<span style="mso-tab-count: 1;"> </span>As currently specified, an OPM, OMM, or OEM file is to represent orbit data for a single spacecraft, and the OCM is to represent orbit data for either a single spacecraft or single parent spacecraft of a parent/child spacecraft deployment scenario.<span style="mso-spacerun: yes;"> </span>It is possible that the architecture may support multiple spacecraft per file; this could be considered in the future.</span></p>
