dborupandClaude Sonnet 5 f244f27a63 fix: View Path treats (0,0) node coordinates as no fix, not the Gulf of Guinea ...

GetPacketPath's node-position lookups (relay-hop points and observer
positioning) read raw lat/lon straight off the nodes row, so a node
with (0,0) stored literally instead of NULL -- MeshCore's "never
actually reported a GPS position" case in practice -- rendered as a
real point off the coast of Ghana instead of no position at all.

Excludes (0,0) the same way GetNodesForScopeAdoption and
geofilter.PassesFilter already do; the node's name is kept, just not
the bogus position.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-07-24 16:43:53 +02:00

..

decrypt

feat: CLI tool to decrypt and export hashtag channel messages (#724)

2026-04-12 22:07:41 -07:00

ingestor

fix: exclude 1-byte hops from interior neighbor-edge creation

2026-07-24 15:57:27 +02:00

migrate

refactor(db): finish #1283 — Option 4: ingestor owns neighbor-graph + schema migrations; server is read-only (fixes #1287) (#1289)

2026-05-19 23:53:41 -07:00

server

fix: View Path treats (0,0) node coordinates as no fix, not the Gulf of Guinea

2026-07-24 16:43:53 +02:00