TE_AdditionalData
Import Additional Data
Syntax
TE_AdditionalData <ScenarioPath> Add File "<FileName>" Ownship "<OwnshipName>"
TE_AdditionalData <ScenarioPath> Delete SourcePath "<FilePath>"
Related Commands
Description
The T&E Toolkit Plugin must be installed in order to use this command.
The TE_AdditionalData command will import Additional Data.
The following table describes the parameters for the TE_AdditionalData Add command.
| Parameter | Description |
|---|---|
| File "<FilePath>" | Enter a file path to additional data. |
| UnitsFile "<FilePath>" | Enter the full path to the units definition file. This parameter is optional. |
| Ownship "<OwnshipName>" | Enter the name of the loaded Ownship. |
| TimeColumn | Enter the name of the time column. A time data mapping for this file type must contain a time column of this name. This parameter, while recommended, is optional. |
| UnitsFile "<FilePath>" | Enter the full path to the units definition file. This parameter is optional. |
| TimeEpoch | Enter the relative start time for the data.
This must be defined if you use the TimeUnits parameter. A daysecond or HMS TimeUnit requires a timeEpoch of midnight. |
| TimeUnits | Enter the time units. Valid options are Day, hour, minute, second, millisecond, microsecond, nanosecond, daysecond, and HMS. Second is the default.
This parameter is optional; if used, the TimeEpoch parameter is required. |
The TE_AdditionalData Delete command only uses the SourcePath "<FilePath>" parameter.
Example
To import Additional Data:
TE_AdditionalData * Add File "C:\data\Drone_TSPI_Mission.csv" Ownship "My_Ctdf_Aircraft"
To import a file that uses a unit definition file and a different data epoch:
TE_AdditionalData * Add File "C:\data\foo.csv" Ownship "trek" TimeColumn "Time" UnitsFile "C:\data\unitsdef.def" TimeEpoch "25 May 2019 14:15:16.17" TimeUnits "second"
To delete additional data
TE_AdditionalData * Delete SourcePath "\\\agi\common\Dev\TnE_Toolkit\Data\Tracks\AF3_0385_MeasuredTracks_ID.csv"
ReturnMessage
Group Membership
This command belongs to the following group(s):
You can use TETK Connect commands in TETK scenarios for pre-flight planning, post-flight analysis, and to support analysis workflows.
You should not use TETK Connect commands when real-time propagators are creating STK vehicles and using STK features instantaneously. The use of Connect commands in a real-time application requires more computational power than STK can support.
TETK functionality that is commonly referred to as "real-time" is actually an offline analysis mode. In this mode, an STK/TETK scenario is prepared with data that is streamed to a particular time in a mission. The post-flight analysis can be prepared again on demand throughout the mission for the data for each time of request. You can use TETK Connect commands in these scenarios.
Version
11.7