fix(adif): export/import coordinates as standard ADIF LAT/LON

[patrickrb]

Problem

Nextlog round-tripped contact coordinates through non-standard lat_n / lon_w fields carrying raw decimal degrees. This is broken interop on two fronts:

• No other software uses those field names. LoTW/TQSL, Cloudlog, N1MM, and GridTracker all read/write the standard ADIF LAT / LON fields. Importing an ADIF file from any of them left latitude/longitude null, so those contacts never got coordinates (breaking mapping).
• Decimal degrees aren't valid ADIF anyway. The ADIF "Location" data type is XDDD MM.MMM (hemisphere letter, 3-digit degrees, decimal minutes), e.g. N040 26.500. Nextlog's exported coordinates were unreadable by external tools even where the field name matched.

Solution

Emit and parse the spec-correct LAT / LON fields, converting to/from signed decimal degrees:

• New pure helper adifCoordToDecimal('N040 26.500') → 40.44167 (S/W hemispheres negative; rejects malformed input and minutes ≥ 60).
• New pure helper decimalToAdifCoord(40.44167, 'lat') → 'N040 26.500' (zero-padded degrees/minutes, correct hemisphere per axis).
• Export now writes <lat:11>N040 26.500 / <lon:11>W073 58.000 instead of the old decimal lat_n/lon_w. An exact 0 (equator / prime meridian) is now emitted too.
• Import reads standard lat/lon, and still accepts the legacy lat_n/lon_w decimal fields as a fallback so files previously exported by Nextlog keep round-tripping (backwards compatible).

No schema change — contacts.latitude/longitude remain decimal degrees; only the ADIF wire format changed.

Testing

• npm run typecheck — clean
• npm run lint — clean
• npm run build — compiles successfully
• npx playwright test tests/adif-generate.spec.ts — 19 passed, including new coverage:
  • adifCoordToDecimal: four hemispheres, origin, case/whitespace tolerance, malformed-input rejection
  • decimalToAdifCoord: padded formatting + decimal→ADIF→decimal round-trip within ~1 m
  • generateAdif: emits standard LAT/LON, drops the legacy field names, omits coordinates when absent

Future follow-up

• The DB-touching import path (insertAdifRecord) is covered indirectly via the pure helpers; a full integration test would need the Playwright DB fixture.
• The LAT/LON precision is MM.MMM (~1 m), matching ADIF's canonical example — sufficient for grid-derived coordinates.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nodelog	Ready	Preview, Comment	Jul 24, 2026 12:06am