Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTK latitude and longitude output issues - loss of precision due to double #121

Closed
SkyJerms opened this issue Apr 27, 2017 · 2 comments
Closed

Comments

@SkyJerms
Copy link

Hello DJI Developers & Community,

I've integrated the D-RTK module with an M600 and can successfully read and record data onto a Linux-based computer. I purchased the ~$5000 D-RTK module because of it's outstanding sensor specs (2-3cm accuracy), however the OSDK Documentation Appendix says that it saves as a double (as opposed to int32 for regular GPS, which oddly enough, is less accurate) when used with the A3 flight controller! Double only gives four decimal places on the latitude and longitude coordinates, which is +/-10m or so in real life.

How can I change the output so it records into an int32? Alternatively, are the RTK outputs actually stored in the regular GPS variables?

Jeremy

@Ray-Airdog
Copy link

Double has 15 decimal places. I suppose it is a formatting issue on your side that rounds it down to 4 when converting to a string (printing to stdout, log etc.)

@hummelslei
Copy link

Close this issue now. If you still have more issues related to DJI SDK, please help to fill in this form:
https://formcrafts.com/a/dji-developer-feedback-en to report them to DJI Developer Support. Thanks for your understanding and cooperation.

pcler pushed a commit that referenced this issue May 7, 2020
…d to develop

* commit '01ec45034e64f817d9d4ffe50145cdb4fcc26251':
  feat:adapting stereo camera sample to M300
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants