I’m trying to get aircraft data within geographic and time boundaries using “SearchBirdseyeInFlight” and I could use some extra information/explanation of some of the returned data and query functions. I expect some of my problems are just a misunderstanding on my part. I know I asked a lot of questions so partial responses are welcome!
What’s the difference between “clock” and “lastPositionTime” keys?
How do either of these relate to “timestamp” in the result? For example, when I query clock >= 2017-04-28 15:30:44
, I get timestamps ranging from 15:31:07 to 15:15:23.
I expected the Unix timestamps to be UTC+0, but queries against “clock” don’t return results until I set to times to local. I double checked this against a tracklog from the website.
When I match timestamps from my results to track log data on the website, ground speed never matches up. All other geo parameters seem to be OK
I can run incremental queries and get results that are identical or sometimes identical with the exception of latitude, longitude, and waypoints. E.g. below.
At 15:51:00: Query clock >= 15:50:30 (409 results)
At 15:51:30: Query clock >= 15:51:00 (437 results, 4 completely identical results, 3 w/ identical timestamps but modified lat/lon/waypoints)
- Lastly, if I change my query spacing, it effects the returned data. In the above I query every 30 seconds. If I query every 15 seconds, I get about 1/3 of the results. I suspect this has something to do with “the time the data was captured” vs “the time the data was put in the database” but that isn’t clear from the API docs
Thanks in advance!