I’ve submitted a YTEP for consideration to create a FITS data standard for yt:
yt handles FITS data in two ways:
1. It can take slices, projections, or covering grids and write them to FITS files using the FITSImageData class and its subclasses:
2. There is a FITS frontend to read in FITS images as datasets:
The FITSDataset class is subclassed also to handle things like spectral cubes and 2D images with sky coordinates, but generic image files can be read in also, though without metadata it will be difficult to set things like units and the like.
The new FITS data standard would be for FITS files written by yt _only_ and would enable slices, projections, etc to be more self-describing in terms of coordinates and units. This metadata would be stored in FITS headers. Then there would be a subclass of FITSDataset, YTFITSDataset, which would look for this metadata and use it to define the dataset in yt.
Please have a look at the YTEP and let me know if you have any comments. Once the YTEP is merged, I’ll be advancing consideration on the corresponding yt PR: