Developer

Hi,

Can someone point a formula or tell me how to calculate an area in km2 or ha that a UAV can cover? Lets suppose I'm using a 24mpixel camera with 6000 x 4000 resolution. Mission planner is telling me that with this camera + 18mm focal lengh and 200 meters altitude I get a FOV of 261 x 173 and 4,33 cm/pixel resolution. Is this right? 60% overlap x 30% sidelap 

And if I flight at 60km/h and for 1 hour, how can I calculate the total expected area it can cover (a standard retangle) not considering wind.

Thanks 

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • T3

    ok, thats an easy one!

    1. For photogrammetry i would suggest 60% x 60% overlap

    2. You cant realy calc the distance, because its depended from the side lap (more legs) so..

       2.1 Measure first the Amps to maintain 60km/h ground speed(0 air)  (lets say 5A)

    3. Go to mission planner/flight planning.  Right click/map/Grid.  Select your desired area, insert the height and the sidelap. MP planner will create the pattern. Its very easy so you can make 5-6 fake missions to take an idea of area vs mission length

    4. On the upper left corner you will see the total lenght of the mission in km (lets say 12000m). Devide the km with Km/h and you will have the Hours of your mission.

    5. Now take into consideration  the Battery you have, the Amps that you A/C draws.  If you have 5000mah battery and your system draws 5amp, then you have 1 hour flight time with a complete destroyed batt. 

    To the example: 12km mission distance and 60km/h speed = 0,1h = 12mins (again its theory because we dont calc the turns).   Vise versa.

    Yoy have 5000mah bat = 1 hour flight time= 60km/h speed = 60km mission distance.. multiply that with 70% to give you a safety margin for the battery = 42km!      So when you are design the mission, keep in mind that it must not exceed 42km.

    happy planning

    James

This reply was deleted.

Activity

DIY Robocars via Twitter
RT @chr1sa: Our next @DIYRobocars virtual AI car race is next Saturday. Compete from home using the @donkey_car simulator -- no physical ca…
14 hours ago
DIY Robocars via Twitter
RT @RoboticMasters: Students from @Sydney_Uni working hard on improvements and changes to @donkey_car simulator. @diyrobocars @adafruit…
14 hours ago
DIY Robocars via Twitter
Practice virtual race this Saturday; the real thing will be on Oct 3 https://www.meetup.com/DIYRobocars/
Wednesday
DIY Robocars via Twitter
Wednesday
Derrick Davies liked lisa TDrones's profile
Wednesday
DIY Robocars via Twitter
Sep 21
DIY Robocars via Twitter
RT @SahikaGenc: AWS DeepRacer & Hot Wheels Track https://youtu.be/4H0Ei07RdR4 via @YouTube
Sep 14
DIY Robocars via Twitter
Sep 8
DIY Robocars via Twitter
RT @davsca1: We are releasing the code of our Fisher Information Field, the first dedicated map for perception-aware planning that is >10x…
Sep 8
DIY Robocars via Twitter
RT @SmallpixelCar: How this works: 1)object detection to find cones in single camera image, 30 frames/sec on @NVIDIAEmbedded Xavier. 2)comp…
Sep 8
DIY Robocars via Twitter
RT @SmallpixelCar: Use two color cones to guide the robocar. No map needed, on onsite training needed. Just place the cones and it will fol…
Sep 7
DIY Robocars via Twitter
Sep 7
DIY Robocars via Twitter
RT @roboton_io: Great to see http://roboton.io running at 60fps on the cheapest #chromebook we could find! #edtech #robotics #educat…
Sep 3
DIY Robocars via Twitter
RT @openmvcam: Crazy in-depth article about using the OpenMV Cam for Astrophotography: https://github.com/frank26080115/OpemMV-Astrophotography-Gear https://t.co/BPoK9QDEwS
Sep 3
DIY Robocars via Twitter
RT @openmvcam: Hi folks, it's finally here! Our first draft of our Arduino Interface Library is out! It works over SoftwareSerial, Hardware…
Sep 3
DIY Robocars via Twitter
RT @chr1sa: Please let them have an open API. This would be perfect for @DIYRobocars races https://twitter.com/NintendoAmerica/status/1301513099707658246
Sep 3
More…