Project: [SignalReach]
Mission builder and launcher for SignalReach.
Workspace Mode
Standard keeps the general workflow but strips advanced solvers, named device presets, and industry-specific radios before the mission reaches the solver.
Step 1 AOI Define the mission footprint, demand density, and terrain source.
Upload an AOI polygon KML or KMZ.
Use these areas to prevent solver placement of repeater or extender candidates, such as flood zones, access-denied terrain, or UAS flight restrictions.
Upload one or more KML/KMZ polygon layers, or draw polygons on the map and save them as solver exclusion zones.
Bring in KML/KMZ overlays like fire lines, existing towers, TAK exports, or projected hazard footprints. These are informational for now, but they travel with the run outputs.
Reference layers render in Build mode and also show up in Results outputs so you can carry the same context forward.
50 m | Area: ? | Est. points: ? | Compute: ?
Set the desired covered-demand percentage here so the mission footprint and success target are defined together.
Height Tile Source
Step 2 Assets Define the deployable inventory available to the planner.
Static and rotor assets are treated like point sites. Fixed-wing assets use the loiter radius conservatively for solve and backhaul logic, while default display heatmaps use a faster centerpoint preview unless you force the heatmap backend to match the solver.
Step 3 Anchors Add fixed sites and backhaul requirements.
Backhaul Overrides
Step 4 Priority Coverage Mark the critical locations that must receive service.
Step 5 Advanced Settings Tune solver behavior, candidate generation, and heatmap export settings.
Supported fielded protocol profiles with approved planner defaults.
Leave blank to use the selected protocol profile defaults. Receiver height is controlled separately under solver controls.
This currently applies to both access coverage and backhaul evaluation so comparisons stay apples-to-apples.
Advanced Shortlisting
Choose whether frontier pockets reorder existing candidates, inject new nearby candidates, or do both.
`Fast display` keeps recommendation and backhaul on the selected solver backend, but uses a quicker preview path for raster overlays. For fixed-wing assets that means a centerpoint display approximation instead of full loiter-ring evaluation. Choose `Match solver backend` when you want the slower strict view.
Red means weak. Yellow is the usable edge. Green means stronger confidence or more RF headroom.
Leave blank to keep the default timestamp-based run naming. Custom names are added to the saved run folder label and past-run picker.

          
Advanced: Raw Mission JSON (editable)
Schema: /kit/mission.schema.json | Validation: loading...
Build mode is for editing AOI, assets, anchors, must covers, and solver settings. Open Results to inspect overlays, logs, and prior runs.