API Stability¶
HyPlan uses stability levels to set expectations about which modules have settled APIs and which may still change.
What the levels mean¶
Stable — The public API (function signatures, return types, class constructors) will not change in backward-incompatible ways within a major version (1.x). Bug fixes and new optional parameters are permitted. If a breaking change becomes necessary, the old interface will be deprecated for at least one minor release before removal.
Experimental — The module works and is tested, but the API may change between minor releases based on user feedback. Pin to a specific version if you depend on exact signatures.
Module stability levels¶
Stable¶
Module |
Description |
|---|---|
|
Flight line creation, splitting, clipping, offsetting |
|
Navigation waypoints with heading, altitude, speed |
|
|
|
Wind-aware reachability boundaries ( |
|
DEM download, elevation lookup, ray-terrain intersection |
|
Swath polygon generation and gap/overlap analysis |
|
Wind field abstractions, MERRA-2, GMAO, GFS providers |
|
Aircraft base class and pre-configured models |
|
ISA model and airspeed conversions (CAS/TAS/Mach) |
|
Flight plan output formats (Excel, CSV, KML, GPX, FMS, ICARTT) |
|
Airport database lookup and nearest-airport search |
|
Flight box generation from center lines and polygons |
|
Graph-based flight line ordering |
|
Solar position and illumination windows |
|
Specular reflection (sun glint) prediction |
|
Cloud fraction climatology and forecasts |
|
Vegetation phenology from MODIS |
|
Satellite overpass prediction |
|
Airspace conflict detection (OpenAIP, FAA TFR/NASR) |
|
3D minimum-turn path planning |
|
Pattern generators (racetrack, rosette, spiral, etc.) |
|
Folium maps, altitude profiles, terrain cross-sections |
|
Geodesic math and coordinate utilities |
|
Pint unit registry and conversion helpers |
Note
Stable means the public API will not break within 1.x. Algorithms, defaults, datasets, and edge-case behavior may still be improved. Aircraft parameters (cruise speed, climb rate, endurance) will continue to be refined as ADS-B calibration data becomes available.
Experimental¶
Module |
Description |
|---|---|
|
Full-waveform lidar sensor model |
|
Scanning-mirror topographic lidar sensor model + RIEGL VQ-480 II reference instance; locked public API on nominal-density semantics, contiguity, MTA envelope, inverse solvers, and LVIS-parity terrain-aware methods |
|
Multi-lidar rig (G-LiHT dual VQ-480i reference); pitch/roll-tilt mount geometry, combined swath/density, multi-angle pair detection |
|
SAR sensor model (UAVSAR variants) |
|
Frame camera and multi-camera rig |
|
Campaign management and airspace conflict detection |
|
NASA C-20A class — |
|
NASA G-IV — |
|
NASA B-777 — |
|
King Air A-90 — |
|
King Air 350 / 350i — |
|
FAAM BAe-146-301 (G-LUXE) — |
|
SAFIRE ATR-42-320 (F-HMTO) — |
|
DLR HALO Gulfstream G550 (D-ADLR) — |
|
BAS DHC-6 Twin Otter (MASIN) — |
|
NERC ARSF Dornier 228 (D-CALM) — |
Deprecation policy¶
When a stable API must change:
The old interface is preserved and emits a
DeprecationWarningfor at least one minor release.The deprecation message names the replacement.
The old interface is removed in the next major version.
Experimental modules may change without a deprecation cycle, but changes will be documented in the release notes.