the heading is typically calculated based on the moving vector. So as soon as you move a bit the receiver can calculate the heading.

Or - in machine control - you have two receivers the same time... But thats the all-in solution.

A static heading or compass reading is not available as we don't have a magnetic sensor/ magnetometer within the antenna - so nothing that can act as pure compass. We rely on the moving vector as this is the only information we have to calculate the orientation/ heading/ direction etc. On Android you could use the phone internal compass sensor - and use this for static stuff. And then switch to the calculated heading as soon as its available. Thats the only workaround that comes to my mind.

The orientation you find in the SigmaObservation describes the orientation of the error ellipsoid. This is requested quite often to draw error ellipsoids easily - but is not related to your position orientation.

the heading is typically calculated based on the moving vector. So as soon as you move a bit the receiver can calculate the heading.

Or - in machine control - you have two receivers the same time... But thats the all-in solution.

A static heading or compass reading is not available as we don't have a magnetic sensor/ magnetometer within the antenna - so nothing that can act as pure compass. We rely on the moving vector as this is the only information we have to calculate the orientation/ heading/ direction etc. On Android you could use the phone internal compass sensor - and use this for static stuff. And then switch to the calculated heading as soon as its available. Thats the only workaround that comes to my mind.

The orientation you find in the SigmaObservation describes the orientation of the error ellipsoid. This is requested quite often to draw error ellipsoids easily - but is not related to your position orientation.