![]() That should be improved in Pro 2.3 (available soon) to consider the terrain, but it sounds like you have some relatively consistent errors (footprint "always too large to the front of the drone") - have you tried adjusting the FOV values and/or sensor elevation (pitch) angle? I've used ArcMap to multiplex your CSV file using a random video on this end, and the footprint looks fine to me, but you're indicating it is not in the right location. Mervyn, I'm curious if you could tell us more, or share your video. For example, should Platform Heading Angle and Sensor Relative Azimuth Angle not be in the range of 0-360? I include the minimum and maximum values recorded for the above flight in case anything stands out. The Cirruas app records the below metadata which should be adequate in calculating video image footprints. I tried looking at this in a scene view and the multiplexed video correctly shows a 'leader-line' or video image center line that is centered in the actual video footprint (not the calculated one). The calculated video footprint is always displaying a much larger area to the front of the drone. In fact they almost never overlap with the actual footprint. The problem I have is that my video frame footprints are not being accurately located in GIS. ![]() I hope someone can advise me how to fix it? I have tried both methods and I still have the same problem. In ArcMap one only has the option of specifying the flight altitude while for Pro one can also use an imagery service. ![]() In order to create the video frame footprint (frame outline), one needs to include elevation values for the ground surface (or height of drone above ground).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |