Hello, I'm listening to SensorEvents for an application that I'm writing and I noticed a problem with the documentation located here:
http://developer.android.com/reference/android/hardware/SensorEvent.html The documentation describes an East (+x) - North (+y) - Up (+z) coordinate system which the phone orientation sensor adopts for providing Euler rotation angles when laying face up, on a flat surface: "The origin is in the lower-left corner with respect to the screen, with the X axis horizontal and pointing right, the Y axis vertical and pointing up and the Z axis pointing outside the front face of the screen." Later, the documentation defines Azimuth as: "Azimuth, angle between the magnetic north direction and the Y axis, around the Z axis (0 to 359). 0=North, 90=East, 180=South, 270=West" However, following a right-handed rule, positive Azimuth should be in a *COUNTER-CLOCKWISE* direction. Meaning, West = 90 and East = 270. Anyone else notice this? Google goes on to note: "Note: This definition is different from yaw, pitch and roll used in aviation where the X axis is along the long side of the plane (tail to nose).". Correct aviation yaw, pitch and roll is defined in a North (+x), East (+y), Down (+z) coordinate system where positive yaw is in the CLOCKWISE direction (right-hand rule). Looks like the documentation may have confused the ENU with the NED definition of Azimuth / Yaw. -C --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
