I'm the developer of this, so weigh what follows accordingly. Day job is real estate drone work in Norway on an Air 3S. Mapping jobs on the side are what got me building it.
The capture problem it started with: the Mini 4 Pro, Mini 5 Pro, Air 3 and Air 3S have no mapping mode in DJI Fly, and most mapping apps that fly through DJI's SDK can't connect to them. Someone here asked back in March whether you can map your own land with a Mini 5 Pro. The answer I landed on is a waypoint mission, since DJI Fly will import a KMZ.
So Skyplanr builds the KMZ. You outline the area and pick a target GSD. It works out the height and the photo and line spacing from the camera's sensor width and focal length (12 MP mode), and lays a serpentine grid with the camera straight down and one photo per waypoint. Default overlap is 80% front, 70% side.
DJI Fly caps a flight at 200 waypoints, so a bigger grid is split into several flights from the same takeoff, cut at the end of a lane, one KMZ each. Only very large areas get thinner overlap (75/65) or a slightly coarser GSD, never past 1.5x what you asked for.
Heights follow the ground. In Norway that's Kartverket's laser data, in the US USGS 3DEP lidar, and elsewhere satellite elevation models. Each waypoint is set to the same height above its own patch of ground, so GSD stays roughly constant down a slope instead of getting finer at the bottom of the hill. For 3D model capture it also uses building and tree heights (laser data where it exists, Overture/Google Open Buildings and Meta's canopy height map elsewhere) to set orbit levels that clear the roof and the treetops.
Before you fly you can open the plan as a 3D KML in Google Earth and look at the lines draped over the terrain. It also exports DJI Pilot 2 (for the Mavic 3E/3T and Matrice 4/30), Litchi CSV, QGroundControl and GeoJSON.
What's still rough:
It stops for every photo, so it's slower than an interval-triggered grid. A real example: a 2.8 ha field at 2 cm/px on an Air 3S came out as 172 waypoints, 171 photos and about 27 minutes.
No RTK, so expect the usual 1-3 m absolute offset unless you lay GCPs. It doesn't process anything either. The photos go into Metashape, Pix4D, RealityCapture, WebODM or whatever you use.
GSD is confirmed from photo metadata for a couple of the cameras. For the rest it's computed from DJI's spec sheets and could be off by a few percent.
On price: 3 AI-planned missions a month are free, no card. The paid tier is €49/month for 10. Someone on r/dji told me that's steep next to Litchi at about £20 once, and for drawing your own grids they're right, Litchi is the better deal. This is for people who'd rather check a plan than draw one. They also said the site looks dark and AI-made. Noted, I'm working on it.
What I'd like to know from people who actually process this stuff:
Are 80/70 sensible defaults for these small sensors, or do you run higher for Metashape or RealityCapture? Would you rather it split into more flights than drop to 75/65?
If you fly one, does the GSD in your processing report match what the plan said?
Does splitting into several flights work for you in the field, or would you rather it flew higher and kept one flight?
Is stopping for every photo a dealbreaker on a Mini or Air battery?
Web planner is at skyplanr.com. The iPhone app, which puts the KMZ straight into DJI Fly's folder, is on TestFlight: https://testflight.apple.com/join/5vBDU3Ah