NMEA 0183 — Mixed GGA/RMC/GSA/GSV/VTG Log
A twelve-fix receiver log with the five sentence types a GPS unit normally interleaves, including three-part GSV satellite-in-view sets. Every checksum is correct, so a parser that verifies them should accept the whole file.
$GPGGA,120000.00,4703.8414,N,01228.9205,W,1,08,0.9,12.1,M,49.0,M,,*4D
$GPRMC,120000.00,A,4703.8414,N,01228.9205,W,3.20,41.0,010126,,,A*41
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,41.0,T,,M,3.20,N,5.93,K,A*36
$GPGSV,3,1,11,03,72,132,42,07,45,215,39,11,33,058,35,18,25,301,31*74
$GPGSV,3,2,11,22,64,275,44,25,18,142,28,29,52,047,40,31,11,320,22*71
$GPGSV,3,3,11,08,07,198,19,,,,,,,,*4E
$GPGGA,120015.00,4703.9709,N,01228.6852,W,1,08,0.9,18.9,M,49.0,M,,*42
$GPRMC,120015.00,A,4703.9709,N,01228.6852,W,3.25,41.4,010126,,,A*4D
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,41.4,T,,M,3.25,N,6.02,K,A*3C
$GPGGA,120030.00,4704.0978,N,01228.4512,W,1,08,0.9,24.8,M,49.0,M,,*46
$GPRMC,120030.00,A,4704.0978,N,01228.4512,W,3.30,41.8,010126,,,A*4F
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,41.8,T,,M,3.30,N,6.11,K,A*36
$GPGGA,120045.00,4704.2323,N,01228.2161,W,1,08,0.9,30.5,M,49.0,M,,*4C
$GPRMC,120045.00,A,4704.2323,N,01228.2161,W,3.35,42.2,010126,,,A*41
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,42.2,T,,M,3.35,N,6.20,K,A*38
$GPGGA,120100.00,4704.3588,N,01227.9857,W,1,08,0.9,36.7,M,49.0,M,,*46
$GPRMC,120100.00,A,4704.3588,N,01227.9857,W,3.40,42.6,010126,,,A*49
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,42.6,T,,M,3.40,N,6.30,K,A*3F
$GPGSV,3,1,11,03,72,132,42,07,45,215,39,11,33,058,35,18,25,301,31*74
$GPGSV,3,2,11,22,64,275,44,25,18,142,28,29,52,047,40,31,11,320,22*71
$GPGSV,3,3,11,08,07,198,19,,,,,,,,*4E
$GPGGA,120115.00,4704.4911,N,01227.7493,W,1,08,0.9,41.5,M,49.0,M,,*41
$GPRMC,120115.00,A,4704.4911,N,01227.7493,W,3.45,43.0,010126,,,A*4E
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,43.0,T,,M,3.45,N,6.39,K,A*34
$GPGGA,120130.00,4704.6222,N,01227.5152,W,1,08,0.9,46.1,M,49.0,M,,*46
$GPRMC,120130.00,A,4704.6222,N,01227.5152,W,3.50,43.4,010126,,,A*4A
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,43.4,T,,M,3.50,N,6.48,K,A*32
$GPGGA,120145.00,4704.7483,N,01227.2808,W,1,08,0.9,49.4,M,49.0,M,,*43
$GPRMC,120145.00,A,4704.7483,N,01227.2808,W,3.55,43.8,010126,,,A*4C
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,43.8,T,,M,3.55,N,6.57,K,A*35
$GPGGA,120200.00,4704.8790,N,01227.0474,W,1,08,0.9,53.1,M,49.0,M,,*44
$GPRMC,120200.00,A,4704.8790,N,01227.0474,W,3.60,44.2,010126,,,A*4E
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,44.2,T,,M,3.60,N,6.67,K,A*3D
$GPGSV,3,1,11,03,72,132,42,07,45,215,39,11,33,058,35,18,25,301,31*74
$GPGSV,3,2,11,22,64,275,44,25,18,142,28,29,52,047,40,31,11,320,22*71
$GPGSV,3,3,11,08,07,198,19,,,,,,,,*4E
$GPGGA,120215.00,4705.0135,N,01226.8165,W,1,08,0.9,56.3,M,49.0,M,,*4B
$GPRMC,120215.00,A,4705.0135,N,01226.8165,W,3.65,44.6,010126,,,A*47
$GPGSA,A,3,03,07,11,18,22,25,29,31,,,,,1.8,0.9,1.5*35
$GPVTG,44.6,T,,M,3.65,N,6.76,K,A*3C
$GPGGA,120230.00,4705.1541,N,01226.5888,W,1,08,0.9,57.9,M,49.0,M,,*46Specifications
- Format
- NMEA 0183
- Talker
- GP (GPS)
- Crs
- WGS 84 (EPSG:4326)
- Encoding
- ASCII
- Checksum Algorithm
- XOR of bytes between $ and *
- Date
- 2026-01-01
- Seed
- 20260807
- Sentences
- 57
- Sentence Types
- GGA, RMC, GSA, GSV, VTG
- Fix Quality
- 1
- Satellites In View
- 11
- Satellites Used
- 8
- Duration Seconds
- 165
- Line Endings
- CRLF (per NMEA 0183)
- All Checksums Valid
- true
Testing contract
Reference control- Scenario
- Parse the log and reconstruct the track from the GGA and RMC sentences.
- Expected result
- Twelve positions are recovered along the Coast Road with fix quality 1 and eight satellites used; all checksums verify and the multi-part GSV sets reassemble into 11 satellites in view.
What is a .nmea file?
An .nmea file is a log of NMEA 0183 sentences, the ASCII protocol GPS and marine electronics use. Each line begins with `$` and a five-character talker-and-type identifier such as GPGGA, GPRMC, or GPGSV, carries comma-separated fields, and ends with `*` and a two-digit XOR checksum. Positions are encoded as degrees-and-decimal-minutes with a separate hemisphere field, not as decimal degrees.
How to use this file
Use an example .nmea file to test GPS log parsers and track converters, verifying checksum validation, correct degrees-minutes-to-decimal conversion, and sensible handling of sentences emitted before a fix is acquired.
How to use this file for testing
“NMEA 0183 — Mixed GGA/RMC/GSA/GSV/VTG Log” is a deterministic Novus Examples fixture for Geospatial, Time-series data, Data import. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks — for testing map tools, route parsers, and geo importers.
Documented properties for this file: seed 20260807 · ASCII · CRLF (per NMEA 0183). Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.
Related files
- gpkgGeoPackage — Aspatial Attributes Table (no geometry column)A GeoPackage holding an `attributes` table with no geometry at all — the standard's own answer to a lookup table you want to ship alongside your layers. Its gpkg_contents row has null bounds and a null SRS, which is what readers that assume every row is spatial trip over.

- gpkgGeoPackage — Three Feature Layers in One SQLite ContainerThe territory as an OGC GeoPackage: an ordinary SQLite database with the three required metadata tables and three feature layers whose geometry columns hold GeoPackage binary blobs. Unlike a shapefile it carries several geometry types, long column names and real typed columns in one file.

- gpxGPX — Garmin TrackPointExtension (heart rate, cadence, temperature)Eight trackpoints each carrying a Garmin TrackPointExtension with heart rate, cadence and air temperature. The GPX schema deliberately leaves `extensions` open, so this is the fixture for checking that a reader surfaces vendor data instead of discarding it on export.

- gpxGPX — Out-of-Order and Duplicated TimestampsSeven trackpoints whose timestamps go forwards, backwards, and then repeat — the pattern a receiver produces after a clock correction or a buffered replay. Naive speed calculations divide by a negative or zero time delta and emit impossible values.

- gpxGPX — Route (rte) Rather Than a TrackA `rte` element: an ordered list of waypoints describing a planned route, with no timestamps because it has not been travelled yet. Many importers only look for `trk` and report this perfectly valid file as empty.

- gpxGPX — Single-Segment Track (24 points)The baseline GPS trace for this category: 24 timestamped, elevated trackpoints in a single segment, walking the Coast Road of the invented territory. Every other GPX fixture here is this file with one thing changed.

Generated by generation/geospatial.py. Free for any use, no attribution required — license.