Thank you! I'm really glad to help and have more features coming to make life easier

Do you use GCPs to increase your accuracy of images positions?? Or you have ppk kits ?

Thanks Mary! check out something like Open Drone Map to generate orthomosaics etc. There are also resources online to help compensate for rolling shutter distortion etc if necessary for your end product.

@@flopasen Thank you James - Yes I have just come across Open Drone Map which looks good also, which I am investigating outcomes thanks for your feedback, will let you know how I go with your product you have introduced us to, again many thanks for your efforts!!

Cheers, I'm working hard on updates now to cover more use cases

Thanks I will probably do this for geojson and shapefile if it's not too difficult!

How did it go?

@@rogoflap it failed miserably. Got to the first point hovered there and didn't do a thing.

Glad to help! More things to come

Thanks! Yeah search and 'hybrid' map has been suggested strongly and it would make life much easier for the user. I'm exploring options at the moment.

Address search added :)

@@flopasen Awesome! I've bought the Webodm ebook (OpenDroneMap: The Missing Guide), let me know if you're interested to receive a copy.

It's nearly ready!

It's ready now :)

Unfortunately it is not automatic. You can continue the mission by selecting which waypoint to start from, but you must remember the number of the waypoint when you return the drone for a battery swap.

@@flopasen thank for you

I have seen this change on your tools. Thank you so much.

Thanks Jeff! Please plan a small and safe mission first to assess whether the tool is working correctly for the model you're using. I've been working with other pilots to support all different modes/ways of flying due to different hardware capabilities. You can find the thread on Litchi's forum where people are discussing issues/suggestions

I encountered the same issue. This seems (my guess) to occur if the map mission area is too small. Here's primarily how I solved it (after setting the target area). Click on settings in the lower left corner. Decrease GSD value (in my case to 0.3) Increase Front overlap [Frontlap] Increase Side overlap [Sidelap]

Thank you! I used a geometry library called turf.js to help me with intersect functions. Yes you're right, Z-check sets 'photo_distinterval' to the same distance as a waypoint would have been. Waypoints are then generated by Z-check * frontlap distance and graphics are indicated. It's versatile for many considerations. I agree about the battery swap RTH safety issue, I'll add something in the description. It's excellent that you're developing an alternate solution to flying missions. I hope you can help many people!

Thanks. Having an easy cross-hatch function for SFM would be a good addition, I'll experiment with it and see if my geometry pipeline will cater to it. As a workaround, users can simply export 1 file, then rotate the flight 90 degrees and export again, performing each mission separately. Concatenating the csv files together would make 1 large mission so you needn't fly two missions, but I understand that's more complex than what others are providing. Lots of people have asked for external JSON/KML/Shapefile interpreting so I think that's definitely something that needs to be implemented. Please try the P3 at 50% sidelap and frontlap and let me know if there's any issues with the camera specs used!

@@flopasen I just concatenated the csv files and it looks good! Thanks for the suggestion. It looks as though the camera specs for the P3 and P3P are pretty similar with the eP3P having 0.4 more effective megapixels. I'll try it out and let you know what I find!

@@flopasen Howdy. So I tried many different configurations and ran into a substantial issue. I don''t know if it's just my Phantom 3 Pro, but the firmware build doesn't allow the drone to take photos at a set distance interval. It can hover in place and take a shot, it can take photos at a set time interval, but not at a set distance interval. So ultimately, the exported mission from here didn't work.

@@aharams811 Sorry to hear! I had no idea the P3 worked that way. I'll try work on having an option to switch between photos by distance and photos by time. In the mean time you can see what speed you've set and how much distance there is between each photo. If you want to fly that mission you could do a quick calculation of how many seconds it takes to travel (photo dist/metres per sec) that distance and batch adjust the CSV file. I think the column is time_interval (I'm not at my computer right now). Hopeful to have it operating soon!

Figured it out. in mission settings in Litchi mission planner. "Path mode" needs to be set to "Straight lines", not "Curved Turns". The camera action will not play otherwise

Thanks! Apologies for the UI issue, it definitely needs improvement especially for multiple browsers. Have you tried a flight with Z-Check of 1? This means a waypoint is generated at every photo. I hope the movement at the waypoint is slow enough not to introduce rolling shutter, but others have suggested I include a 'Stay For:' feature. If Z-Check of 1 isn't still enough for you, let me know, otherwise before importing to Litchi, you can open up the csv file. - Look for the actiontype column with value of 1 and actionparam of 0. That's the photo command. Shift those values over to the next two columns and replace the original values with action type of 0 and actionparam value of milliseconds. That means the drone will stay there until taking its photo. If Z-Check is more than 1, intermediary photos are always taken on the move. Let me know if that wasn't clear enough but I'm happy to implement the 'Stay For' slider and maybe generalise the UI

@@flopasen Oh okay cool! I haven't used Litchi that much yet, so I am not so familiar with the mission waypoint process. Haven't tried flying with your plan yet, but will definitely try with a Z-Check of 1. Do you know what the standard settings for waypoints are? Like wait time etc.? Considering I use Z = 1 of course.

Thanks! I hope you can give it a try and maybe speed up your workflow.

For sure! I will let you know 😉

if you ran out of battery, pause the flight, change battery, continue mission 👍

I'll bump it up to 500m now, wow that's high!

@@flopasen Wonderful job ! Please, set for DJI Air 2s have same high (500m) too. I just check it is 303m.

@@thaivuvan4554 I am deploying the change now. I hope you can fly this high without getting in trouble with the law or affecting nearby planes! 😅 Here the limit is 120m. Also you are right about details for the polygon, I'll add area of polygon and maybe when I'm smart enough I will add distances to each line. Thanks for suggestions.

Be careful of the mission time when you are this high also. My mission times are horizontal distance only and are too optimistic. You should make the missions much shorter to allow for ascent and descent.

@@flopasen Thank you for your wonderful changes. I am completely convinced by your tool. One small point I want to be concerned about is the parameter of GSD, I mean 450, 500, ... instead of 498, 501, 505. Finally, I still hope the function to import regions from geojson files soon. is displayed and if possible please add a function to erase the drawn area instead of having to refresh the current page. Thanks again for your helpful tool.

Having the same issue - flat flightplan and Litchi won't export 3d file. presumably coz it's flat? How did you get it to work?

Yes absolutely. I was a bit reluctant to go that low but if people need it I can do it. Do you think even 12-15ft would be useful? Possibly for modelling things like cars/trucks

Hey Corey I just pushed the update which allows you to go even lower ;) Be careful and thanks for suggesting! By the way if the app misbehaves with small polygons just reduce the Nudge value back to 0 and go from there.

you can do this in litchi 👍