Closed observingClouds closed 3 years ago
@observingClouds This looks terrific but I agree with all of @d70-t's comments: the naming fits better under the platform; it's better not to require non-standard libraries; and satellite data should be included separately.
I see the motivation to put these tracks to the respective platform, but I can also imagine quite some cases, where one would like to have easy access to just the tracks of all platforms. Do we have plan to connect similar variables, such that they can be searched/loaded simultaneously? A new package has been requested.
I've also had a look into the data files and am wondering about the variable
flight
. I would have expected to find something like aflight_id
in stead of an integer.
I wouldn't change this now, since I don't want to modify the provided files and new files should be made available soonish.
What about some track data? Since the data is currently on a web-server that uses compression I had to adjust the requirements a bit. The track-files I linked here are not the official released once, but they are just slightly modified (time type change, ascii characters in global attributes) to make them work with opendap. The changes are also noted in the history attribute of the specific files. An opendap compatible version is in planning and will then be published on AERIS.