v1.8.3 - Earth Curvature LOS Fixes and Config Cleanup
This release fixes the LOS tool so it no longer ignores Earth curvature, and it cleans up the related configuration and documentation.
LOS Fixes
- Fixed issue #53: the LOS tool now accounts for Earth curvature instead of using a purely straight terrain-versus-line check
- Applied the same curvature-aware LOS math to both the frontend realtime LOS path and the backend
/losfallback so live interaction and server responses stay consistent - Updated LOS blockage and elevation-profile calculations to use curvature-adjusted terrain samples, which can now correctly mark longer paths as blocked where the previous LOS tool showed clear
New LOS Environment Controls
- Added
LOS_CURVATURE_ENABLED - Added
LOS_CURVATURE_FACTOR
Defaults when unset:
LOS_CURVATURE_ENABLED=trueLOS_CURVATURE_FACTOR=1.333333
Config and Runtime Fixes
- Fixed
docker-compose.yamlso all LOS-related environment variables are actually passed into the container:LOS_ELEVATION_URLLOS_ELEVATION_PROXY_URLLOS_SAMPLE_MINLOS_SAMPLE_MAXLOS_SAMPLE_STEP_METERSELEVATION_CACHE_TTLLOS_CURVATURE_ENABLEDLOS_CURVATURE_FACTORLOS_PEAKS_MAX
Docs
- Updated
.env.examplewith the new LOS curvature environment variables - Clarified MQTT authentication docs for
meshcore-mqtt-broker: the live map normally uses a brokerSUBSCRIBER_Nusername/password pair, not node-style signed publisher auth - Updated version, docs, and changelog for
v1.8.3
Validation
pytest -q→92 passed, 2 skippednode --check backend/static/app.jspython3 -m py_compile backend/*.py