![]() So, you want to adjust flight height based on the elevation of the takeoff point. Most flights with DJI and DroneDeploy will navigate to the flight altitude relative from takeoff, then stay there for the duration of the flight, not adjusting flight height relative to terrain. ![]() This altitude is far more accurate, but you need to do some work to get Drone2Map to adjust image altitude to these readings. There is another field in the EXIF metadata called RelativeAltitude which is given from the aircraft barometer. Sidenote: While collecting data, first calibrate the IMU through the DJI go app so that you can be sure your barometer readings are as accurate as possible given changes in weather and elevation between different work sites. After browsing some DJI forums, I found the fix. ![]() When I viewed the captured images in Drone2Map 3D view, they appeared more like 200-230 feet off of the ground and processing the images resulted in bizarre results even when running GCP's. For example, I was doing a 3D building survey and flew two loops at roughly 30 and 60 feet off the ground. This can be several hundred feet off, which is obvious in Drone2Map when you view the images in 3D view. When producing the EXIF metadata for each image, the image altitude is populated with the DJI aircrafts GPS altitude reading. ![]() Sorry if this has already been covered elsewhere. This is for those people using DJI drones. I just went through a workflow that I wanted to highlight here in case it helps anyone with post processing drone images in Drone2Map. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |