Ground speed reporting bug?

[thobson88]

I just noticed a possible bug in the reporting of ground speed in the POS endpoint.

If I create an aircraft with the following parameters:

"acid": "TST001",
"type": "B744",
"lat": "0",
"lon": "0",
"hdg": "0",
"alt": "FL360",
"spd": "250"

and then request position I get something like:

"TST001": {
"actype": "B744",
"alt": 10972,
"gs": 232,
"lat": 0.0479,
"lon": 0,
"vs": 0
},
"sim_t": 23

but using the POS command in the BlueSky client returns these speeds:

TAS/CAS/GS: 262/453/453 kts M: 0.789

So there's a big discrepancy in the ground speed figures. I also noticed that Bluebird reports a fixed ground speed of around 232 when the aircraft speed is changing in the client, so it almost looks like there's an upper bound on ground speed reported by Bluebird.

[rkm]

Looks like BS reports the CAS/TAS/GS in m/s but converts them to kts for display in the GUI. I've corrected the API documentation to reflect that the ground speed is in m/s.

I'm not sure I can currently reproduce the situation where the ground speed reaches an upper bound. Do you have a scenario or a log file you could send me which shows this? Thanks.