100% Client-Side Privacy
Adawaty Pro • adawaty-pro.com
48+ Offline Client-Side Converters & Technical Guides
Home / GPS & GIS Maps / NMEA to GPX / CSV
Read Technical Guides →

NMEA to GPX / CSV

Parse raw $GPGGA / $GPRMC satellite logs into GPX tracks or CSV — 100% private client-side processing.

100% Client-Side JS

Active Converter

Smart Auto-Fix:
1. Source File(s) or Paste Input: No file selected
2. Live Output (Editable):
Marine & Embedded GNSS Serial Logs (NMEA 0183)

NMEA to GPX / CSV: Decoding $GPGGA & $GPRMC Serial GPS Sentences

Technical Anatomy of NMEA 0183 ASCII Sentences

Defined by the National Marine Electronics Association, NMEA 0183 is the universal 4800/9600-baud ASCII serial protocol emitted by GPS/GNSS modules. Each line begins with $, followed by a 2-letter talker ID (GP for GPS, GN for multi-GNSS, GL for GLONASS), a 3-letter sentence type (GGA for 3D fix & altitude, RMC for position, speed, and date), comma-separated fields, and a trailing *XX XOR checksum.

Crucially, NMEA does not output standard decimal degrees: latitude 3401.2540,N encodes DDMM.MMMM (34° 01.2540' North), and longitude 00500.6240,W encodes DDDMM.MMMM (5° 00.6240' West). Converting .nmea to GPX or CSV applies the exact deg + (min / 60) trigonometric formula with hemisphere sign inversion so your serial log plots accurately on modern maps.

Raw $GPGGA Serial Sentence vs. Decimal-Degree CSV / GPX Output

# Input: u-blox NEO-6M / Dashcam Serial Log (gps_capture.nmea)
$GPGGA,123519,3401.2540,N,00500.6240,W,1,08,0.9,410.4,M,46.9,M,,*47

# Converted .CSV Output (Decimal Degrees):
UTC_Time,Latitude,Longitude,Altitude_m
123519,34.020900,-5.010400,410.4

Real-World Software & Hardware Ecosystem

Drone builders, marine navigators, and embedded IoT engineers capture .nmea logs from u-blox NEO-6M / M8N / F9P modules, Arduino / ESP32 TinyGPS++ projects, Viofo / Nextbase dashcams, ArduPilot / PX4 telemetry, and Raymarine / Furuno marine chartplotters.

Troubleshooting & Edge Cases

  • No-Fix Sentences (Fix Quality = 0 or Status = V): Before a cold-start GPS locks onto 4+ satellites, it emits empty coordinate fields like $GPRMC,,V,,,,,,,,,,N*53. Our parser skips invalid/empty fix lines so zero-island (0, 0) spikes do not ruin your GPX track.
  • Mixed $GPGSV / $GPGSA Noise Lines: Satellite-in-view (GSV) and dilution-of-precision (GSA) sentences contain no coordinates and are cleanly ignored during GPX/CSV extraction.
  • Time-Only $GPGGA Without Calendar Date: Unlike $GPRMC, $GPGGA carries UTC time (HHMMSS) without a calendar date; keep $GPRMC enabled in your receiver if you need full date timestamps.

Key NMEA 0183 Sentence Types & Field Positions

Sentence IDPayload FieldsWhy It Matters
$GPGGA / $GNGGAUTC, Lat, N/S, Lon, E/W, Fix, Sats, HDOP, AltPrimary 3D position & MSL altitude sentence
$GPRMC / $GNRMCUTC, Status (A/V), Lat, Lon, Knots, Track, DateAdds ground speed (knots) and DDMMYY calendar date
$GPGSA / $GPGSVSatellite PRNs, SNR signal strengthDiagnostic telemetry (cleanly skipped during track export)

Validating NMEA XOR Checksums in Embedded C / Python

# Quick Python XOR checksum check for any NMEA 0183 line:
body, cs = line[1:].split('*')
valid = (eval('^'.join(str(ord(c)) for c in body)) == int(cs[:2], 16))

Frequently Asked Questions

How are NMEA 0183 DDMM.MMMM coordinates (like 3401.2540,N) converted into decimal degrees?

NMEA sentences pack degrees and decimal minutes together: 3401.2540 means 34 degrees and 01.2540 minutes. The converter computes 34 + (1.2540 / 60) = 34.020900° and negates the value automatically for South (S) and West (W) hemispheres.

Which NMEA 0183 sentences ($GPGGA, $GPRMC, $GNGGA) does this parser extract?

It parses standard GPS ($GP), GLONASS ($GL), and multi-constellation GNSS ($GN) GGA (Fix Data + Altitude) and RMC (Recommended Minimum Position + Speed/Date) sentences while validating comma-delimited fields.

What does the trailing *XX hexadecimal checksum at the end of every NMEA sentence mean?

Every NMEA 0183 line ends with an asterisk (*) followed by a two-digit hex XOR checksum computed across all ASCII characters between '$' and '*'. It detects serial UART noise from u-blox, SiRF, or marine GPS receivers.

Can I convert dashcam or marine chartplotter .NMEA / .LOG files into Google Earth tracks?

Yes. Export your NMEA capture to .GPX here so you can immediately open your vehicle route, drone flight, or boat voyage in Google Earth, QGIS, or Strava.