GATEMAN project -- Wide-bandwidth, high-precision GNSS and jammer raw data

Open data API in a single place

Provided by Zenodo

Get early access to GATEMAN project -- Wide-bandwidth, high-precision GNSS and jammer raw data API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2021.01.30 00:00
Created
2019.01.01
Available languages
English
Keywords
GNSS, interference, jamming, detection, direction finding/localization
Quality scoring

Dataset description

This dataset contains high quality GNSS and jammer raw data generated during the in-lab validation activities of jamming detection and localization performed in the frame of the GATEMAN project. These files are grouped for each type of validation scenario defined. The scenarios are combinations of three different GNSS and three different jamming signals. Content: The archive contains a folder for each validation scenario. Each folder contains two files. One contains the GNSS data and the second file contains jamming data. A function to read the data with GNU Octave/Matlab is also included. ├── GALE1+AMtone │   ├── AMtone@20MSps.bin │   └── GALE1@20MSps.bin ├── GALE1+Chirp10MHz │   ├── Chirp10MHz@20MSps.bin │   └── GALE1@20MSps.bin ├── GALE1+Chirp20MHz │   ├── Chirp20MHz@20MSps.bin │   └── GALE1@20MSps.bin ├── GPSL1+AMtone │   ├── AMtone@20MSps.bin │   └── GPSL1@20MSps.bin ├── GPSL1+Chirp10MHz │   ├── Chirp10MHz@20MSps.bin │   └── GPSL1@20MSps.bin ├── GPSL1+Chirp20MHz │   ├── Chirp20MHz@20MSps.bin │   └── GPSL1@20MSps.bin ├── GPSL5+AMtone │   ├── AMtone@20MSps.bin │   └── GPSL5@20MSps.bin ├── GPSL5+Chirp10MHz │   ├── Chirp10MHz@20MSps.bin │   └── GPSL5@20MSps.bin ├── GPSL5+Chirp20MHz │   ├── Chirp20MHz@20MSps.bin │   └── GPSL5@20MSps.bin └── readBinData.m   Data format: Each file stores the received baseband samples as an array of complex, 16-bit signed integer data (range -32,768 to 32,767) of the corresponding signal. The data is stored in Big-endian, network order format, i.e. the most-significant byte occupies the lowest memory address. The real and imaginary components of the data correspond to the in-phase (I) and quadrature-phase (Q) data, respectively. I and Q-samples are interleaved [I, Q, I, Q, ...] in the array.   Data: The recorded data of each validation scenario consists of two files, one containing the GNSS signal (L1, L5 or E1 band), the other one containing the jamming signal (tone, chirp 10 & 20 MHz bandwidth). The RF GNSS signal was generated with a GNSS signal generator, it contains only a single spreading sequence. The RF jamming signal was generated with a Vector Signal Transceiver. Both signals of a scenario were recorded synchronously with an USRP at an I\Q rate of 20 MS/s. GNSS signals: Startime:          30.05.2018 at 12:00 (approximately) Latitude:           N 50 deg, 50.4864 min Longitude:        E 4 deg, 21.3499 min Altitude:            50m Trajectory:        Static Ephemeris file: brdc1500.18.n       GNSS band     PRN     Elevation (deg)   Azimuth (deg)  Power (dBm)          GPS L1          4               85                        187                -70          GPS L5          4               85                        193                -70          Galileo E1     E14           66                        274                -68.5 Jamming signals: The tone is simple a sinosoidal waveform in the centre of the GNSS bands. The chirps are linear frequency modulated waveforms (sawtooth) in the centre of the GNSS bands with sweep range of 10 MHz and 20 MHz and sweep period of 8.64 µs.     The data uploaded here are a truncated samples. Longer samples of data are available upon request.
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks