Thomas Boggs

For 32-bit floating point values and 2048x2048 pixels, there should only be a single band of data in the image. Unfortunately, there isn't exactly enough space since there are a...

".bip" isn't a recognized image file extension so try to open it explicitly like this: ``` img = spy.envi.open('/path_to_file/Frgrnd.hdr', image='/path_to_file/Frgrnd.bip') ```

If the file extension is ".bip", you should stick with BIP, though in the case of a single band, it doesn't even matter which interleave you choose. An offset of...

I've never processed complex images with SPy but it seems like it should be possible. What happens if you modify your code to replace `img.load()` with `img.load(dtype=np.csingle)`?

Great. I'll update the code so the correct dtype is automatically used for complex data types.

No, it has not been implemented. If I had access to the `pci_read_spatial` and `pci_read_spectral` routines referenced in issue #72, I could probably implement it. In the mean time, you...

I'm not immediately aware of a solution that is both clean/elegant and simple, particularly if you are new to both python (and Spectral Python) and hyperspectral imaging. One solution would...

The .hdr extension is the name of the file you are *creating* with the `spectral.envi.save_image` function. Presumably, you are loading the numpy array and band metadata from the .mat file....

I agree it would be rather difficult using the memmap interface. I suppose another option is to disable the memmap interface and use the `SpyFile` interface whenever a nonzero value...

@ohspite, that is odd. The keywords were there earlier, hence the change I made to protect against headers with nonzero offsets. I notice the parameters referenced [here](http://www.harrisgeospatial.com/Company/PressRoom/Blogs/IDLDataPoint/TabId/838/PID/2923/CategoryID/15/CategoryName/ENVI/Default.aspx) (search the page...