DanRyanIrish

Thanks so much for this inventory, @dhomeier. #### NDCube Following on from the changes you've suggested in #453, I think your suggestion of displaying the unit and data type are...

> I suggest trying the first option while making it clear what the values are, e.g. having a table in the `__str__` with column names something like > > ```...

My thought was to take the minimum and maximum values of each coordinate from the set of all corners. And the point of only running the corners through `pixel_to_world` was...

> But is there a complete list of the different coordinate types `wcs.celestial` might represent, e.g. when to use `min(bbox_c.ra), min(bbox_c.dec)` instead, and how to best check the type –...

> Yes, I thought that was already the goal, giving just two values for each coordinate separately? Given the generality of what we're dealing with I think that is the...

Yep, I agree.

> Extracting all corners in addition should not be that much effort (they are already there from the bounding box transformation), but the question seems more how to display them...

As an example, say we have a spectral, space, space cube. Would this feature slice the cube at an arbitrary point along the spectral axis and then drop the spectral...

The second option is an elaboration on `explode_along_axis`.

@nabobalis Could you give this PR a review? It should be very similar if not the same as what's in your sunraster PR.