1、When initVelocity type is set to SCU, the course angle is calculated incorrectly.
2、In the JSON, "speedUnit": "kph" with "speed": 741.6 (which should be ≈ 206 m/s) is directly treated as 741.6 m/s.
I wanted to analyze the error between the software receiver's positioning solution and the true trajectory. I generated a trajectory using MATLAB according to the JSON configuration, but found that the trajectory I generated seems to differ greatly from the receiver's solved trajectory, and that's how I discovered these problems.
I also added extra trajectory output to the tag file. The original course angle of 325° became 261°, which caused the latitude/longitude that should be heading northwest to become heading southwest.
The receiver's solution also confirmed this: the computed speed was 2667 km/h, which is exactly 3.6 times the value configured in the JSON.
I would also like to know what unit is assumed for the up velocity when configured this way.Although I've already worked around these two issues by modifying the code, I'm not confident that my fix is correct. Looking forward to your proper fix.
1、When initVelocity type is set to SCU, the course angle is calculated incorrectly.
2、In the JSON, "speedUnit": "kph" with "speed": 741.6 (which should be ≈ 206 m/s) is directly treated as 741.6 m/s.
I wanted to analyze the error between the software receiver's positioning solution and the true trajectory. I generated a trajectory using MATLAB according to the JSON configuration, but found that the trajectory I generated seems to differ greatly from the receiver's solved trajectory, and that's how I discovered these problems.
I also added extra trajectory output to the tag file. The original course angle of 325° became 261°, which caused the latitude/longitude that should be heading northwest to become heading southwest.
The receiver's solution also confirmed this: the computed speed was 2667 km/h, which is exactly 3.6 times the value configured in the JSON.
I would also like to know what unit is assumed for the up velocity when configured this way.Although I've already worked around these two issues by modifying the code, I'm not confident that my fix is correct. Looking forward to your proper fix.