Hi everyone,
we are currently working with survey grids in Mission Planner and have run into a couple of limitations that we’d love to see addressed in a future release.
1. Altitude: No decimal input in the flight planning window
When setting up a survey grid, the altitude field in the planning window only accepts integer values. If you enter a decimal value (e.g. 3.5 m), the system automatically rounds it to the nearest integer. For our use case, being able to set precise altitudes with one decimal place is essential – for example, flying at exactly 3.5 m above ground.
Our current workaround is to manually export the waypoint file and edit the altitude values directly in a text editor. While this works, it is time-consuming and error-prone, especially when making frequent adjustments.
2. Grid spacing (Distance Between Lines): Minimum value too large
The minimum value for the distance between scan lines appears to be limited to 0.3 m. We would like to fly grids with a line spacing of 0.25 m, which is currently not possible through the UI.
Again, we are working around this by manually editing the waypoint file, but this is far from ideal.
Feature Request:
Could the following improvements be considered for an upcoming release?
- Allow decimal (floating-point) input for altitude in the survey grid planning window
- Extend the minimum value for grid line spacing to allow values below 0.3 m (e.g. down to 0.1 m)
These changes would significantly improve workflow efficiency, especially for close-range inspection and precision mapping missions.
Thanks for the great work on Mission Planner – we really appreciate it!
Best regards