Summary
Once vector data replaces raster tiles (see companion issue), individual chart layers should be toggleable at runtime so pilots can reduce clutter for their phase of flight.
Proposed Layers
| Layer |
Default |
Notes |
| Terrain base (hillshade/topo) |
On |
SRTM or OSM |
| Class B airspace |
On |
Blue shading + ceiling/floor labels |
| Class C airspace |
On |
Magenta |
| Class D airspace |
On |
Blue dashed |
| Class E (surface) |
On |
Magenta dashed |
| Special Use Airspace (MOA, Restricted, Prohibited) |
On |
Per FAA colour coding |
| Airports (towered) |
On |
Blue circle + identifier |
| Airports (non-towered) |
On |
Magenta circle |
| VORs / NDBs |
On |
Standard symbology |
| Airways (Victor/Jet) |
Off |
Clutters at low zoom |
| Obstacles (DOF) |
Off |
Show near terrain/approach |
| NEXRAD weather |
Off |
Toggled separately |
| TFRs |
On |
Red boundary when active |
| Traffic (ADS-B) |
On |
When receiver present |
UI Mechanism
The existing HMI uses rotary encoder + button menu (F1/F2/F3 keys). Layer control fits naturally as a sub-menu:
MainMenu → Layers → [list of toggleable layers with checkmarks]
Config file should also support default layer visibility so panels can be pre-configured for the mission (VFR cross-country vs. local pattern work vs. IFR).
Related
- Depends on vector chart rendering issue
🤖 Generated with Claude Code
Summary
Once vector data replaces raster tiles (see companion issue), individual chart layers should be toggleable at runtime so pilots can reduce clutter for their phase of flight.
Proposed Layers
UI Mechanism
The existing HMI uses rotary encoder + button menu (F1/F2/F3 keys). Layer control fits naturally as a sub-menu:
Config file should also support default layer visibility so panels can be pre-configured for the mission (VFR cross-country vs. local pattern work vs. IFR).
Related
🤖 Generated with Claude Code