Compiled from two meeting reports. Goal: identify everything needed to achieve full boat support in Cockpit.
- System-wide support for imperial units
- Auto center map to vehicle location
- Change map provider (Google Maps support needed — currently unclear if supported)
- Turnaround distance setting for surveys
- Ability to change survey entrance
- Return to home function
- Opening the mission planning page is very slow when a mission with waypoints already exists (~100 waypoints causes noticeable delay)
- Add a "center on current mission" button in both the mission planning view and the map widget
- Home location set in flight mode doesn't appear in mission planning mode until the mission is manually downloaded from the vehicle
- Allow the user to select where in the mission element list to insert the next element (currently always appended to the end)
- The survey should appear as an element in the mission list until the user explicitly generates waypoints (generate should happen once, ideally at upload time — similar to QGC behavior)
- (Maybe) Always add a Loiter command to the last waypoint so the vehicle holds position
- Make cruise speed part of the mission checklist
- Users typically plan missions without a vehicle connected — ensure this workflow is fully supported
- Mission is unnecessarily re-downloaded in multiple scenarios: on every vehicle reconnect, and when returning to planning mode after switching to flight mode post-upload — should check if mission is unchanged and skip (confirmed behavior is to NOT auto-download, but edge cases remain)
- Vehicle trail/path disappears when entering mission planning mode — path should remain visible as a positional reference for planning
- Show waypoint heading/direction alongside distance in the mission planning view
- Fix bug: acute angles being incorrectly generated in survey paths
- Fix: "Clear survey" tooltip sometimes stays open and overlaps the spacing input field
- Fix: Triangulated polygons are not accepted as survey polygons; error message when waypoint generation fails is not clear enough
- Fix: "Click on survey to edit it" functionality is broken (no longer works)
- Fix: Survey polygon is deleted when the user navigates to flight mode and back — user cannot edit the polygon after returning from flight mode
- No way to go back and edit a survey after it has been created
- Mission planning page and Map widget should open at the last known vehicle location; if no location data is available, fall back to the last area visited
- Cockpit should remember the last map option used (OpenStreetMap vs. ESRI) — should be a configurable setting
- Offline tile save dialog should display how much storage the download will use — the word "Tiles" alone is not descriptive enough for users
- When no map tiles are available (e.g. offshore, no offline tiles downloaded), the repeated "no tiles" pattern makes map icons hard to see — should fall back to a solid color
- Add a North arrow indicator on the map (as a widget or map overlay) — standard map practice
- Being partially addressed by PR #2506 (adds map rotation + tap-to-reset-north button)
- Show GCS (operator) location on the map via USB GPS (NMEA/UBlox) — already works in QGC with USB GPS connected to the base station
- Measurement tool: click and drag on the map to draw a line showing distance and heading between two points
- Being fixed by PR #2465
- Allow users to get coordinates of any point on the map by clicking or via right-click context menu, with copy-paste support — #2369
- POI (Point of Interest) editing on the map is not user-friendly
- Cockpit launch splash screen is shown for too long — users habitually cancel it; logic should be reviewed and improved
- Cannot expand waypoint commands panel after collapsing it
- Waypoints remain stuck on screen (do not clear properly)
- Maps chooser disappears in map view when approaching it with the mouse — likely caused by widgets being positioned too close together
- Large missions cause Cockpit to hang
- Odd/incorrect path generated between certain waypoints (diagonal shortcuts observed in survey grid — see meeting screenshots)
- Persistent vehicle trail causes severe lag and disconnects when left running too long — clearing it restores normal behavior
- Enabling the persistent trail setting requires a Cockpit restart to take effect
- Vehicle disarms when Cockpit window loses focus (regression) — failsafe set to "continue" in auto mode but vehicle goes to hold from guided/loiter
- On Mac, low-power mode causes Cockpit framerate to drop below 30fps
- Switching video streams between WebRTC and RTSP requires a Cockpit restart
- WebRTC streams can appear listed in Cockpit but never actually play
- Single-waypoint missions don't display correctly on the map