Event & Route Planner

GPX — the format most GPS units and hiking/navigation apps read. Includes a waypoint for every pin (with elevation), a track line connecting them in the order you placed them, and a closed route approximating each active coverage circle as a polygon, since GPX has no native circle shape.

GeoJSON — the format most GIS and SAR mapping software (QGIS, most web-based map tools) treats natively. Same pins (as Point features, with elevation) and the same route (as a LineString), but the coverage circles come through as real Polygon geometry rather than a polygon-shaped route — cleaner for anything that reads geometry types directly, like drawing a proper filled search-area boundary.

KML — Google Earth's native format, also read directly by Avenza Maps, Garmin BaseCamp, and most phone-based field/SAR apps. Same content as GeoJSON (pins, route line, coverage polygons), styled to match the map's colours — red for node coverage, blue for antenna coverage.

All three only include a coverage-radius area if that toggle is switched on in the Coverage & Line-of-Sight tab — what you export always matches what's currently visible on the map.

Two pins are marked "Linked" when the straight-line distance between them is no more than twice the coverage radius — i.e. their circles physically overlap on the map. This is a flat-plane approximation: it doesn't account for terrain blocking the path between them, which is exactly what the line-of-sight check below is for. Use Coverage overlap for a quick first pass across many pins, then confirm any specific link you're relying on with a line-of-sight check.

Elevation is sampled at 91 points along the straight-line path between your two pins from real bare-earth terrain data. We correct for Earth's curvature using the standard 4/3-effective-radius rule used in RF planning, then compute the first Fresnel zone radius at each point (17.31 × √(d1·d2 / (f·d)) metres, with d1/d2/d in km and f in GHz). "Blocked" means the direct line touches terrain; "Marginal" means the direct line is clear but the zone needed for a full-strength 868MHz link isn't; "Clear" means both are unobstructed. None of this accounts for vegetation, structures, rain fade, or antenna quality — treat every result as a starting point for an on-site check, not a substitute for one.

Defaults are typical figures for an SX1262-based LoRa module (like the T1000-E) at SF12/125kHz — adjust to match your actual hardware and antennas. This link budget only accounts for free-space path loss; it doesn't add the terrain/Fresnel obstruction above, so read both together.

GPX — the format most GPS units and hiking/navigation apps read. Includes a waypoint for every pin (with elevation), a track line connecting them in the order you placed them, and a closed route approximating each active coverage circle as a polygon, since GPX has no native circle shape.

GeoJSON — the format most GIS and SAR mapping software (QGIS, most web-based map tools) treats natively. Same pins (as Point features, with elevation) and the same route (as a LineString), but the coverage circles come through as real Polygon geometry rather than a polygon-shaped route — cleaner for anything that reads geometry types directly, like drawing a proper filled search-area boundary.

KML — Google Earth's native format, also read directly by Avenza Maps, Garmin BaseCamp, and most phone-based field/SAR apps. Same content as GeoJSON (pins, route line, coverage polygons), styled to match the map's colours — red for node coverage, blue for antenna coverage.

All three only include a coverage-radius area if that toggle is switched on in the Coverage & Line-of-Sight tab — what you export always matches what's currently visible on the map.