This belongs in `spectral-cube` and partly exists in `pvextractor`. @astrofrog, should we port the pvextractor viewer into spectral-cube or do something more readily compatible with glue?

On the general topic of "spectroscopic tools", it would be helpful to (1) have more specific requests and (2) split up 1D and 2D spectroscopy. A few 1D analysis tools have already been mentioned, and specutils (specutils.readthedocs.org) exists for IO operations on many 1D spectroscopic formats. What specific features are needed?

The javascript interaction is pretty cool. Have you tried using the nbagg backend for interaction within ipython?

Also, if you're interested in contributing to pyspeckit, it would be nice to have some help with the EQW method there: https://github.com/pyspeckit/pyspeckit/blob/master/pyspeckit/spectrum/fitters.py#L321

pyspeckit is largely meant to handle the splot use case. It won't ever handle the 2D spectroscopy case, which requires spectroscopic aperture extraction (e.g., apall) or regridding.

If you have any issues with pyspeckit or suggestions, you can raise issues (github.com/pyspeckit/pyspeckit/issues) or e-mail pyspeckit@gmail.com. If there are enough issues or feature requests, we could open a userecho site like this too.

Good question. Spectrum1D would be great to have in the core at some point, since it now exists in a reasonable state in specutils. SpectralCube, at least from the spectral_cube package, has a lot of components that may or may not be core-acceptable, but we can discuss whether they ought to be factored out.

I think the last time I was present for a discussion on this (maybe >1 year ago...), there were objections to having core objects like these because "generalized WCS would take care of them..." or something along those lines. Is there still any such concern, if I even perceived it correctly?

Astrometry.net is another important reference for star-based alignment. Having access to its functions as part of astropy would be a huge improvement.