You Are Here:

Converting a Trajectory in StudioView

Trajectories can be captured in different formats, depending on how they have been generated and/or what their intended use is. GSG can read .nmea , .traj, or .tle files.

To learn more about …

The conversion of trajectories can become necessary e.g., if a trajectory had been created by …

  • … recording it using a GNSS receiver
  • … using third-party software e.g., Google Earth
  • … manually entering it into an Excel spreadsheet
  • … using other means to generate trajectories.

However, it may also be required to change or add certain settings to an .nmea trajectory e.g., to smoothen, interpolate or equalize its data. This also can be accomplished with the Trajectory Editor, see below under Converting a Trajectory in StudioView.

StudioView's Trajectory Converter can convert the following input and output file formats:

  • .nmea
  • .csv
  • .gpx
  • .kml
  • .kmz

Note: Note that the .csv format represents StudioView waypoints table from the Trajectory Editor and therefore has the same fields. Working with .csv files, StudioView assumes that for each waypoint the .csv file will have four values: Latitude, Longitude, Speed and Altitude.

Realistic Trajectories

Trajectories should always realistically reflect the dynamic capabilities of the type of vehicle in motion e.g., car, aircraft, ship. To this end, Spectracom recommends using ‘smooth’ methods to describe the movements, i.e. changes in acceleration, heading or altitude should be gradual, not sudden or ‘hard’.

When using coordinates to describe a trajectory, the data must be provided in 10 Hz format and must not contain sudden changes in speed, direction or elevation; GNSS receivers generally are very sensitive to G-force and unrealistic movements will result in the receiver losing track of the signals.