Skip to main content
RACELOGIC Support Centre

05 - SatGen Importing Files

SatGen v3 allows for the import of three file formats:
 

  • Load Google Earth KML File -. Google Earth files in KML format can be loaded into the software.  The Position (x,y) and Speed profile is immediately displayed.  Date, Time, Dynamics, update rate and mask angle can bet set to users requirements.
  • Load NMEA File - NMEA Files in the $GGA format can be loaded into the software.  The Position (x,y) and Speed profile is immediately displayed. Date, Time, (not dynamics), update rate and mask angle can bet set to users requirements.
  • Load VBOX File - The VBOX product range a number of high specification GNSS data loggers from Racelogic ranging from 5Hz to 100 Hz VBOX files in the *.vbo format can be loaded into the software.  The Position (x,y) and Speed profile is immediately displayed. Date, Time, (not dynamics), update rate and mask angle can bet set to users requirements.
  • For test scenario files go to the examples sections at the rear of the manual
     

SatGen Import.png
Import File Screen
 

  • Smooth NMEA data - This must be ticked before the NMEA file is loaded, this will then apply smoothing to the data to give a more accurate representation when noise is encountered in the original data.  See figure 13:  The original data in red and the smoothed data in blue. This is displayed in the scenario details section once the file is loaded.
  • Coarse interpolation for large KML files - Very large KML files will exceed the software’s memory limits and cannot be loaded.  If this occurs tick this radio button and the software will use a coarser interpolation method reducing the size of the memory allocation required.
     

12 (2).png
 

  • Use KML height as stop time - manually change the height contained in the KML file to a number other than zero, then it will wait at this point for that many seconds. Below is an example where the KML file was manually edited and inserted a ‘5’ in the height value for the fourth co-ordinate point, telling the scenario to stop for 5s at this point.
     

                              <coordinates>

-0.9916250156269413,51.98945959664934,0 -0.9918802675743399,51.98952017642391,0
-0.9923099781755218,51.98903215409713,0 -0.9919128854165971,51.98861506602104,5
-0.9915889645878773,51.98806780389109,0 -0.9913145889074515,51.98799885812851,0
-0.9900068592684941,51.98829563659137,0 -0.9892711073382832,51.98890250954216,0

                              </coordinates>
 

7 (1).png

Including Stop Periods in a KML File

If you view the image below, you will see several pins named ‘Stop (x)’ along the defined path (red line). At the point closes to each of these pins on the path, a stop for the duration defined in the pin’s brackets will be added.
 

Satgen KML File Stops1.jpg
 

To create KML files including the stop pin, follow the steps below:

  1. Open Google Earth.
  2. Select the ‘Add Path’ icon Satgen KML File Stops2.jpg and define your route.
  3. Once you have defined the route you can add stops by selecting the ‘Add Placemark’ icon Satgen KML File Stops3.jpg and placing the pin next to the point in your route where you wish to stop. Please note these pins must be named ‘Stop(x)’ with ‘x’ being the number of seconds you wish to stop for.
  4. When you have defined both your route and all your required stops, right click on ‘Temporary Places’ and select ‘Save Place As..’. Ensure the ‘Save as type’ is set to 'KML' and save your route.
  • Was this article helpful?