Grid Survey Pattern Generator, Quickly See Heading and RTH Icons along with new Keyboard Navigation

[GenCodeInc]

Add a lawnmower/grid survey pattern generator that allows users to define a polygon area on the map and automatically generate survey waypoints within it.

Features:

• Grid survey button in Action Menu with polygon drawing interaction
• Sidebar settings card with line spacing, altitude, speed, sweep angle, overshoot, and End with RTH checkbox
• Live auto-preview: polygon outline, dashed survey path, and numbered waypoint dots update as parameters change
• Lawnmower pattern algorithm with configurable sweep angle and overshoot
• RTH waypoint automatically appended when End with RTH is checked
• Waypoint count display with remaining capacity
• Ctrl+G keyboard shortcut to activate grid draw mode
• Full i18n support for all UI strings

Draw complex surveys in seconds

Preview and Edit Before you generate the survey,

Generate mission with clear makings on where the RTH will activate

Create large surveys with multiple POI in seconds

Clearly see RTH and Heading Settings

These missions can be made in seconds.

[GenCodeInc]

@b14ckyy I think people will like this survey option. If you have any issues let me know.

[GenCodeInc]

I dont own an inav plane so someone may want to test in a safe location or with the simulator on a fixed wing and vtol.

[GenCodeInc]

@b14ckyy

Use the arrow keys its fun!! ;)

You can now use your keyboard to step thru the waypoints using arrow right and left, you can also use your delete key to delete a waypoint, this makes checking the waypoints faster than ever.

I also added a small RTH tag to clearly let the operator know that the last point will initiate a RTH as it was not visible before unless you clicked on the waypoint, I think these are great additions to inav. Hope you guys like them.

Oh yea and a +add waypoint when hovering over the line so its clear that option is available to the planner.

[b14ckyy]

Man you are on fire! I love it. Great addition. Lets tag that into the 9.1 Target here already. The other PR we will check. Great work.

[GenCodeInc]

Man you are on fire! I love it. Great addition. Lets tag that into the 9.1 Target here already. The other PR we will check. Great work.

Thanks just give me credit somewhere when 9.1 if you can, so I can brag at the office ;)

[b14ckyy]

With so big (visible) feature changes you will certainly be named in the "Highlights of this version" section :D

[GenCodeInc]

With so big (visible) feature changes you will certainly be named in the "Highlights of this version" section :D

@b14ckyy

Heading now shows a small compass so you know where the drone will point to without clicking on every waypoint.

[sonarqubecloud]

Quality Gate passed

Issues
63 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.6% Duplication on New Code

See analysis details on SonarQube Cloud

[Jetrell]

I dont own an inav plane so someone may want to test in a safe location or with the simulator on a fixed wing and vtol.

@GenCodeInc Nice feature. Saves time when setting up a survey .
It appears to write the mission fine.

The main limitation to account for using a fixedwing aircraft, is the default LINE SPACING.
25m is too tight to make two right angle turns within that distance.. It ended up being a hairpin turn in my case.

Due to fixedwing turn accuracy being determined a lot by the airplanes speed. And that not being slower than 60km/h for most airplanes.
User don't always adjust the default settings to start with. So It might be beneficial to set the default Line Spacing to a more practical 100m. And if the user is flying with a multicopter; or an airplane that can fly much slower, they could reduce the Line Spacing to suit their requirements.

[sensei-hacker]

The main limitation to account for using a fixedwing aircraft, is the default LINE SPACING.
25m is too tight to make two right angle turns within that distance.. It ended up being a hairpin turn in my case.

Due to fixedwing turn accuracy being determined a lot by the airplanes speed. And that not being slower than 60km/h for most airplanes.
User don't always adjust the default settings to start with. So It might be beneficial to set the default Line > Spacing to a more practical 100m.

Agreed. Defaults should be safe. At 50 MPH - 80 km/h, a double-rate turn has a diameter of 212 meters.
At 25 MPH - 40 km/h, 106 meters.
(A standard rate turn would be twice that, but RC aircraft can generally handle a double-rate turn safely.)

Also perhaps interesting, at 100 meters altitude, a 90 degree fov camera will cover a 200 meter strip of ground.
Or, at 50 meters it will cover 100 meter strip.

If one wanted closer spacing with safe turns, one could use an interlace pattern. Fly rows 1, 3, 5, 7 ... then at the end go back and cover the even numbers.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[GenCodeInc]

The main limitation to account for using a fixedwing aircraft, is the default LINE SPACING.
25m is too tight to make two right angle turns within that distance.. It ended up being a hairpin turn in my case.

Due to fixedwing turn accuracy being determined a lot by the airplanes speed. And that not being slower than 60km/h for most airplanes.
User don't always adjust the default settings to start with. So It might be beneficial to set the default Line > Spacing to a more practical 100m.

Agreed. Defaults should be safe. At 50 MPH - 80 km/h, a double-rate turn has a diameter of 212 meters. At 25 MPH - 40 km/h, 106 meters. (A standard rate turn would be twice that, but RC aircraft can generally handle a double-rate turn safely.)

Also perhaps interesting, at 100 meters altitude, a 90 degree fov camera will cover a 200 meter strip of ground. Or, at 50 meters it will cover 100 meter strip.

If one wanted closer spacing with safe turns, one could use an interlace pattern. Fly rows 1, 3, 5, 7 ... then at the end go back and cover the even numbers.

I changed it to 100 meters for the default

[sensei-hacker]

I think this is close to ready for merge?

At 4186, is this correct?:

spacing: Number.parseFloat($('#gridSpacing').val()) || 25,

Also I see "missionGridPreview" in messages.json; is that used somewhere?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[GenCodeInc]

I think this is close to ready for merge?

At 4186, is this correct?:

spacing: Number.parseFloat($('#gridSpacing').val()) || 25,

Also I see "missionGridPreview" in messages.json; is that used somewhere?

@sensei-hacker

Sorry for the delay I just noticed this today,

I’ve updated the grid survey patch:

changed the fallback for #gridSpacing to 100 when the input is invalid
removed the unused missionGridPreview locale key
The branch is pushed and the existing PR #2593 is up to date.

yes its ready to merge

[GenCodeInc]

@b14ckyy @sensei-hacker This should be good to merge now.

[sensei-hacker]

To resolve the merge conflicts, I opened #2698

Qodo had some questions, though.

[sensei-hacker]

Closing — this PR had a merge conflict against maintenance-10.x. The developer resolved it and opened it as #2698 (couldn't push directly to this branch, got a 403), which carries the same milestone/label. Please continue any further discussion there. Thanks for the great feature work!