ExportDataFile
Create an external ephemeris or attitude file for a vehicle, or create an azel mask file for a Facility, Place, or Target.
Syntax
ExportDataFile <ObjectPath> {FileType} "<FilePath>" [{Options}]
Description
Use the ExportDataFile command to export an STK ephemeris (*.e), STK Binary ephemeris (*.be), attitude (*.a), or propagator (*.pg) file for a vehicle, or a terrain mask file (*.aem) for a facility, place, or target.
You can also create a Code500 ephemeris file (*.EPH), a Spice ephemeris file (*.bsp), or a CCSDS ephemeris file version 1.0 or 2.0 (*.oem) or version 2.0 (*.xml) for a vehicle.
The command format will depend on the {FileType} you specify. Valid values for {FileType} are: Ephemeris, Attitude, PropDef, and TerrainMask. This topic provides outlines for these formats.
<FilePath> can be the path to a file on your local drive or the path to a file on an SDF server. See Specifying Paths for <SDFFilePath> syntax information.
Ephemeris
The following table describes the {Options} for the Ephemeris {FileType}, including the ephemeris type(s) each {Option} is valid for.
Use the Ephemeris {FileType} to export an STK ephemeris file (*.e), an STK Binary ephemeris (*.be), a Code500 ephemeris file (*.EPH), a Spice ephemeris file (*.bsp), or a CCSDS ephemeris file (*.oem) version 1.0 (CCSDS) or version 2.0 (CCSDSv2) for a vehicle.
| {Option} | Description | Valid For Type: | Default |
|---|---|---|---|
| Type {STK | Spice | Code500 | CCSDS | CCSDSv2 | STKBinary} | Specify the type of ephemeris you are creating. You must specify Type for this Connect command. If you do not specify Type, the command will fail. | All | STK |
| CoordSys {frame} | This is the coordinate system in which you are expressing the ephemeris. The value of {frame} can be any frame owned by the central body that you are using to express the ephemeris (see CentralBody setting). This always includes Fixed, Inertial, J2000, ICRF, and TrueOfDate. STK will also accept TEMEOfDate, ITRF2020, ITRF2014, ITRF2008, ITRF2005, and ITRF2000 when the central body is Earth. STK will accept MeanEarth, PrincipalAxes_440, PrincipalAxes_430, PrincipalAxes_421, etc. when the central body is Moon. | STK, STKBinary | Fixed |
| Format {Current | 410 | 420 | 430 | 620 | 800} | Specify whether or not the ephemeris file should be compatible with a prior version of STK. If you enter 410, then Include is not a valid option for InterpBoundaries. | STK | Current |
| InterpBoundaries {Include | Exclude} | Specify whether or not to include interpolation boundaries. If Format is 410, then the default value is Exclude. | STK, STKBinary | Include |
| CentralBody {CBName} | Enter the central body for the ephemeris. | STK, Spice, STKBinary | Vehicle's Central Body |
| SatelliteID <Value> | Enter the identifying number for the satellite for which you are creating the ephemeris. Enter an integer between -999999999 and 999999999. | Spice, Code500 | -200000 |
| InterpType {Type13 | Type09} | Specify the interpolation type for the SPICE file. | Spice | Type09 |
| InterpOrder <Value> | Enter an integer between 1 and 15. | Spice | 5 |
| Covariance {Position | PosVel | None} | Choose to export position covariance (3x3), position/velocity covariance (6x6), or no covariance information. If the requested covariance information is not available from the selected object, STK will still create the ephemeris file but will display a warning in the Message Viewer window. Covariance information may be available for objects with paths defined using the HPOP or STK External propagators. The export of covariance information is not compatible with 4.1.0 version format. | STK | None |
| TimeSteps {<Value> | UseEphemerisSteps | {Time Array}} | Specify the time steps to use in the Ephemeris file.
<Value> is the step size in seconds. The value should be between 0.001 and 1000000000.0 seconds. Enter UseEphemerisSteps to use the vehicle's ephemeris steps. {Time Array} is a time array component that defines the time steps to use. See Component Specification for information on specifying a time array component. The keyword TimeSteps replaces the keyword StepSize, which was deprecated in STK 10. | All | 60.0 seconds |
| TimePeriod {TimeInterval} | Define the span of the ephemeris in the file. For valid {TimeInterval} values, see Time Options. | All | Vehicle's time period |
| Originator "<StringValue>" | Enter a string identifying the originating organization producing the data file.
This {Option} is required if Type is CCSDS. | CCSDS, CCSDSv2 | None |
| ObjectID "<StringValue>" | Enter as a string the ObjectID, using the international spacecraft designator, also known as an NSSDC identifier, which follows a YYYY-NNNA format, where YYYY is the year of the launch, NNN is the sequential launch number within that year, and A is a letter designating the specific piece from the launch.
This {Option} is required if Type is CCSDS. | CCSDS, CCSDSv2 | None |
| ObjectName "<StringValue>" | Enter a name for the object. By recommendation of the CCSDS standard, you should use the name from the SPACEWARN Bulletin. | CCSDS, CCSDSv2 | Satellite name |
| CenterName <CBName> | Enter a central body name. | CCSDS, CCSDSv2 | Satellite's central body |
| RefFrame {ICRF | EME2000 | TOD | TEMEOfDate | ITRF2020 | ITRF2014 | ITRF2008 | ITRF2005 | ITRF2000 | GCRF | Fixed | MeanEarth} | Enter the name of the reference frame.
TEMEOfDate, ITRF2020, ITRF2014, ITRF2008, ITRF2005, ITRF2000, and GCRF are valid only if CenterName is Earth. MeanEarth is valid only if CenterName is Moon. Fixed is valid only if CenterName is not Earth or Moon. | CCSDS, CCSDSv2 | ICRF |
| UseSatCenterAndFrame {Yes | No} | Use the satellite's central body and reference frame.
Setting this option to Yes will override any settings for CenterName and RefFrame. | CCSDS, CCSDSv2 | No |
| TimePrecision <Value> | Specify the number of digits past the decimal point used in the expression of seconds in the selected date format. Enter an integer between 0 and 10. | CCSDS, CCSDSv2 | 6 |
| DateFormat {YMD | YDOY} | Enter a date format. YMD format is YYYY-MM-DDT:HH:mm:SS.SSS, where YYYY is the four-digit year, MM is the two-digit month, DD is the two-digit day of the month, HH is the two-digit hour, mm is the two-digit minute, and SS.SSS is a floating point representation of seconds into the minute, with the precision specified via the time precision setting. YDOY is similar except that the day of the year, DDD, replaces the month and day of month: YYYY-DDD:THH:mm:SS.SSS. | CCSDS,CCSDSv2 | YMD |
| EphFormat {SciNotation | FloatingPoint} | Enter a format for representing the position and velocity information as either scientific notation or floating point notation. | CCSDS, CCSDSv2 | SciNotation |
| IncludeCovariance {Yes | No} | Enter Yes to include covariance data in the exported file. If you enter Yes and covariance data is not available, the command will Nack. | CCSDSv2 | No |
| IncludeAcceleration {Yes | No} | Enter Yes to include acceleration data in the exported file. | CCSDSv2 | No |
| FileFormat {KVN | XML} | Specify the format of the exported file, either KVN (Keyword Value Notation) or XML. | CCSDSv2 | KVN |
CCSDS Ephemeris
The Consultative Committee on Space Data Systems, CCSDS, orbit ephemeris message format is defined by the CCSDS Blue Book, Orbit Data Messages, CCSDS 502.0-B-1, and CCSDS 502.0-B-2. You can download these documents from https://public.ccsds.org/publications/MOIMS.aspx. The role of the CCSDS is to develop recommendations for data and information-sharing standards.
The following apply to the generation of CCSDS orbit ephemeris messages using STK:
Center names are restricted to central bodies known to STK.
STK will refer time tags to the UTC time system.
The interpolation method and degree will be those used by STK.
STK will create separate metadata and ephemeris data sections to prevent interpolation across maneuvers.
Attitude
Choose Attitude for {FileType} to create an attitude (*.a) file for a vehicle.
The following table describes the {Options} for {FileType} = Attitude.
| {Option} | Description | Default |
|---|---|---|
| Details {Quaternions | QuatAngVel} | Specify the type of data for STK to write to the file, either just quaternions or quaternions and angular velocity. | Quaternions |
| CoordAxes {Fixed | J2000 | Custom "<RefAxes>"} | Specify coordinate axes for the data. If you use Custom, you must also enter a <RefAxes>. The format for <RefAxes> is "AxesParentPath AxesName", for example, "CentralBody/Earth Fixed" or "Satellite/Satellite1 Body". | Vehicle's Coord Axes |
| Format {Current | 430 | 600} | Specify whether the attitude file should be compatible with a prior version of STK. | Current |
| TimeSteps {<Value> | UseNativeTimes | {Time Array}} | Specify the time steps for STK to use in the Attitude file.
<Value> is the step size in seconds. The value should be between 0.001 and 1000000000.0 seconds. If you enter UseNativeTimes, then the Attitude file will contain the ephemeris time steps plus any additional times where the attitude may change abruptly. {Time Array} is a time array component that defines the time steps for STK to use. See Component Specification for information on specifying a time array component. The keyword TimeSteps replaces the keyword StepSize, which was deprecated in STK 10. | 60.0 seconds |
| TimePeriod {TimeInterval} | Define the span of the attitude in the file.
For valid {TimeInterval} values, see Time Options. | Vehicle's time period |
PropDef
Choose PropDef for {FileType} to create a propagator (*.pg) file for a vehicle. This {FileType} has no additional options.
TerrainMask
Choose TerrainMask for {FileType} to create a terrain mask file (*.aem) for a facility, place, or target. This {FileType} has no additional options.
To create a terrain mask file, you must load Terrain into the scenario and set STK to use it for calculations (see the Terrain command). Also, you must set the AzElMask properties of the facility, place, or target to use Terrain; see the SetAzElMask (Facility, Place & Target) command.
Examples
To create an ephemeris file named sat1.e for the Satellite1 object in the current scenario using a J2000 coordinate system, using Earth as the central body, and including interpolation boundaries in the file:
To create an ephemeris file named sat2.e for the Satellite2 object in the current scenario that contains ephemeris using an inertial coordinate system and Jupiter as the central body saved in 4.1-compatible format:
To create a CCSDS format ephemeris file named Sat_CCSDS_118c.oem for Satellite1:
To create a SPICE file:
To create an attitude file named sat2.a that contains attitude quaternion data for the Satellite2 object in the current scenario using a fixed coordinate system:
To create an attitude file named sat2.a that contains quaternion and angular velocity data for the Satellite2 object in the current scenario using a inertial coordinate system:
To create an attitude file named sat3.a that contains attitude quaternion data for the Satellite3 object using a fixed coordinate system and including ephemeris time steps plus additional times where attitude may change, over a one-hour time period:
Create a propagator definition file for Satellite1:
Create a terrain mask file for Facility1:
Return message
Group membership
This command belongs to the following group(s):
Version
11.6