Opusfc

Added
- Python 3.8 builds

Removed
- Python 3.5 builds

Fixed
- Visible image extraction for files with lots of visible images
- Accept more string encodings, best effort on fail

The I can see clearly now release.

Added
- Visible images can now be extracted with `getVisImages`.

Changed
- Documentation now hosted at https://stuart-cls.github.io/python-opusfc-dist/

Removed
- Python 2.7, 3.4 builds

Fixed
- 3D-TRS (time-resolved) files without "Z Axis Label" parameter can now be loaded.
- Loading issue for some processed 3D-IMAGE files.

Added
- Python 3.7 builds

Fixed
- Fix annotated map reading for files generated by Opus 6.5

Fixed
- Fix datablock list generation for extra-large 3D Image files
*NOTE:* This filetype cannot be opened in 32-bit Windows builds
- 3D-MAP multiregion arbitrary map files (`MultiRegionDataReturn`) which contain
point groups where the points are arbitrary locations (not a grid or a linescan)
are now properly loaded
- Multiregion: handle non-standard point group ordering
- Multiregion: handle annotations for files with multiple visible images

The 3D blocks that aren't hyperspectral cubes release.

Added
- Support for 3D-MAP multiregion arbitrary map files
- Support for 3D-TRS Time-resolved spectra files

Changed
- Object returned by `.getOpusData` is now a DataReturn class specific to that
data type. This allows consumers to easily determine data structure using
`type(dataObject)` instead of guessing. Object structure for previously
supported files remains the same, so should be backwards compatible.

Fixed
- `TRARI` blocks are no longer mis-identified as `TRC` blocks by `.listContents`

First pypi.org release.

Added
- Basic test suite
- Docstrings
- Sphinx based documentation
- `.paramDict` provides natural-language translation of three-letter parameter
codes. Not inclusive of all possible codes.

Changed
- `.getOpusData` now takes a tuple(DataBlockType, Dimensions, Derivative) as
the second argument.
- `.listContents` returns a list of datablock tuples
- 3D TRC data is now return as a 3D numpy array under `.traces` with the structure
`.traces[row][column][trace]` where trace corresponds to the `.labels` index
of the trace. Individual trace maps can be accessed as `.traces[:,:,trace]`

Fixed
- Properly terminate parameter strings