# File formats

# Custom File Formats

# Position File (.pos)

This file contains simulated receiver positions for each epoch. The file is comma-separated (; is the delimiter) containing the following data:

Column	Data	Description
1	Epoch	Simulated epoch as Modified Julian Date (MJD) [days].
2	Latitude	Geographic Latitude in WGS-84 frame [°].
3	Longitude	Geographic Longitude in WGS-84 frame [°].
4	Height	Height above WGS-84 ellipsoid [m].

# Skyplot File (.sky)

This file contains information on satellite visibility as well as direction of signal arrival for each satellite. The file is comma-separated (; is the delimiter) containing the following data:

Column	Data	Description
1	Epoch	Simulated epoch as Modified Julian Date (MJD) [days].
2	Satellite	Identifier of GNSS type and satellite number.
3	Azimuth	Azimuth in which the satellite is visible [rad].
4	Elevation	Elevation in which the satellite is visible [rad] – negative value means satellite is below horizon.

# Signal File (.bin)

This file contains the simulated digital IF signal in a binary form. The file format is depending on the chosen output configuration within the scenario settings. In case the output is complex the real and imaginary values of each sample are consecutively written to the file (I1, Q1, I2, Q2, …). The number of bytes used for one sample in this file can be set within the scenario settings and determines how the file must be read when processed.

# Level File (.lvl)

This file contains information on the amplitudes within the IF signal. The file format is proprietary and defined as well as reserved to use by IZT GmbH (Innovationszentrum für Telekommunikationstechnik GmbH IZT, Erlangen).

# Fake Acquisition File (.facq)

This file contains information on acquisition value for each satellite. The file contains a header that is marked with a leading asterisk (*) in each header line. The data section is space-separated (blank as delimiter) containing the following data:

Column	Data	Description
1	GNSS Code	Identifier of GNSS, carrier frequency and code type.
2	Satellite Number	Identifier of GNSS type and satellite number.
3	Code Phase	Current phase of primary code [chips] at given sample.
4	Doppler	Doppler frequency shift [Hz].
5	Carrier Phase	Current phase of carrier wave [rad] at given sample.
6	Sample Index	Index of given sample to which the other values relate.

# Spoofer File (.spf)

This file contains spoofer settings (position, simulated receiver position, code offset) for each epoch and spoofer. The file is comma-separated (; is the delimiter) containing the following data:

Column	Data	Description
1	Epoch MJD	Simulated epoch as Modified Julian Date (MJD) [days].
2	Epoch	Simulated epoch in UTC.
3	Spoofer Index	Index of spoofing signal.
4	Spoofer Latitude	Geographic Latitude in WGS-84 frame [°].
5	Spoofer Longitude	Geographic Longitude in WGS-84 frame [°].
6	Spoofer Height	Height above WGS-84 ellipsoid [m].
7	Spoofer X	Cartesian WGS-84 X coordinate [m].
8	Spoofer Y	Cartesian WGS-84 Y coordinate [m].
9	Spoofer Z	Cartesian WGS-84 Z coordinate [m].
10	Fictional Latitude	Geographic Latitude in WGS-84 frame [°].
11	Fictional Longitude	Geographic Longitude in WGS-84 frame [°].
12	Fictional Height	Height above WGS-84 ellipsoid [m].
13	Fictional X	Cartesian WGS-84 X coordinate [m].
14	Fictional Y	Cartesian WGS-84 Y coordinate [m].
15	Fictional Z	Cartesian WGS-84 Z coordinate [m].
16	Code Offset	Additional code offset (pseudorange offset) of signal.

# Spoofer Power File (.spfp)

This file contains received spoofer power for each epoch at each receiver. The file is comma-separated (; is the delimiter) containing the following data:

Column	Data	Description
1	Epoch MJD	Simulated epoch as Modified Julian Date (MJD) [days].
2	Epoch	Simulated epoch in UTC.
3	Spoofer Index	Index of spoofing signal.
4	Receiver Index	Index of receiver.
5	Channel	Simulated channel (e.g. GPSL1CA).
6	Power	Received power (relative to authentic power) [dB].

# Standardized File Formats

# KML

KML files can be used as input for the receiver path, where each receiver position must be specified as a <Placemark> according to the examples below. One KML file can only correspond to one receiver.

# Static Position

The tags <TimeStamp> as well as <Point> must be specified to set the time and coordinates of the receiver. The <altitudeMode> must be absolute (i.e. will be ignored if different).

<Placemark>
    <TimeStamp>
        <when>2016-01-01T14:00:01.00Z</when>
    </TimeStamp>
    <Point>
        <altitudeMode>absolute</altitudeMode>
        <coordinates> 47.456839951,45.454539995,479.988</coordinates>
    </Point>
</Placemark>

Note

The specified time of the receiver position must be given in UTC and the coordinates are reference to the WGS-84 ellipsoid, where the height is the ellipsoidal height and latitude and longitude are given in decimal degrees. The first time-stamp of the imported receiver path will be used as receiver position at the start time of the simulation and the time-steps between two consecutive positions are kept as they are in the input file. A <Placemark> without a <TimeStamp> is ignored by the KML reader by definition.

# Receiver Path

A path in a KML file has to be represented by sequential Placemarks, each containing the tags <TimeStamp> as well as <Point>. The <altitudeMode> must be absolute.

<Placemark>
    <TimeStamp>
        <when>2016-01-01T14:00:01.00Z</when>
    </TimeStamp>
    <Point>
        <altitudeMode>absolute</altitudeMode>
        <coordinates> 47.456839951,45.454539995,479.988</coordinates>
    </Point>
</Placemark>
<Placemark>
    <TimeStamp>
        <when>2016-01-01T14:00:10.00Z</when>
    </TimeStamp>
    <Point>
        <altitudeMode>absolute</altitudeMode>
        <coordinates> 47.4568400941,45.454639995,481.078</coordinates>
    </Point>
</Placemark>

Note

← Simulation Results Run-time API →