The ISS uses the zebra datastore currently, so data are written in a sequence of netcdf files over the course of months rather than a single netcdf file for a whole flight. To be useful to ISS, the HIAPER display needs to support that kind of a datasource, at least for a transition period. In the future the ISS may be able to take advantage of the SQL database approach. Likely the netcdf directory access would be a distinct class of a datasource though it could share some implementation with the single-file datasource. As long as the backend implementation of a DataSource is isolated from the users of the API, and the API sufficiently encapsulates all the functionality required for accessing directories of files, then the aeros display could be adapted to ISS.