Display UAV Heading in App

Much like the GPS Coordinates are displayed OSD, it would be extremely helpful to see which way the UAV is pointed (in degrees) while flying. A good spot might be in the Status Bar at the top of the screen, as it’s only 3 digits max.

Same request was posted from @aerovisao on Feb. 7 2022, but doesn’t look like it was addressed.

Please like/vote for this, thank you!

I find that seeing the visual heading as displayed in the map (see #5 below) to be much more useful than seeing a numerical heading value displayed in the OSD. I also configure one of the C1/C2 buttons to quickly swap between the camera view and map view.

Hi @wesbarris, Thanks for your thoughts, but I’m looking for the digital readout so that I can plug it in to Waypoints in the Mission Hub on my desktop between flights. I photograph and video buildings and construction sites, and it’s nice to have building lines even with the image frame. Right now it’s a guessing game when I review the footage to refine the waypoint headings. If the heading were displayed in the App, it would save a lot of review time (and battery) when flying over & over again just to figure out the best [looking] heading in Mission Hub for any given waypoint.

Ahhh. I see. Have you looked into the EXIF data in your images? I have not tried but I’m pretty sure all of that data in stored in each photo. If you want to pursue this you can check out either ExifTool or Picture Information Extractor.

1 Like

Good idea. I looked at an image with ExifTool [thanks for the suggestion] and was able to determine a good looking heading from a photo I manually lined up. However, that would require a preliminary mission with stopping at each waypoint to manually choose an optimal heading, then going back to the desktop to review each photo with the ExifTool, then enter that data into a revised mission, and flying again… hoping I got it right. It would be much easier to just make a note of exactly what the App sees while in the air, so if there are any discrepancies, the data entered into the Mission Hub would correspond to what the camera saw during flight. But for now, I think that’s a good workaround.

1 Like

I’m still not really understanding your workflow but that’s ok. I just wanted to make one more suggestion.

Did you know that you can configure your C1/C2 buttons to place a waypoint at the drone’s current location? By doing so, you can fly your drone, frame your subject, press the C1 (or C2) button to store the waypoint, then repeat. This will eliminate the need for writing anything down (if that’s what you do).

I just thought I’d throw this out there in case it might help.

It’s too cumbersome to modify missions with the App while on site and so I choose to make any corrections in the Mission Hub while at my computer desktop, then go out and fly the mission to see if it needs any changes. Marking a waypoint with a C1/C2 button is another great suggestion. That would probably solve the whole heading issue too I suppose! :smiley: Thank you!

Hi there,

I am having the same problem as you. I already have a route plan to monitor restoration in a mine. As I am having more areas restored, I want to add new waypoints to my route plan. I have firstly compared the app data of the firsts waypoints with its exifdata and, surprise, always headind parameter is not very precise as it varies +/- 2º (exifdata compared with app data). I wanted to know what is the exact heading to add new waypoints defininng, among other parameters, this one.
Do you have any idea?