[jira] [Updated] (TIKA-874) Identify FITS (Flexible Image Transport System) files

["Peter May (Updated) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TIKA-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter May updated TIKA-874:
---------------------------

    Attachment: fits_support.patch

This patch identifies FITS files, based on the signature used by the file(1) command and also specified in RFC4047 (http://fits.gsfc.nasa.gov/rfc4047.txt).

It includes a simple unit test (added to TestMimeTypes) using a FITS file available at http://fits.gsfc.nasa.gov/nrao_data/tests/nost_headers/good.fits 

I cannot see any noticeable license restrictions on these sample FITS files; there is a contact email address shown on http://fits.gsfc.nasa.gov/fits_nraodata.html where we might be able to get further advice.

Advice/comments welcome on the best approach forward, especially regarding the unit test sample file.
                
> Identify FITS (Flexible Image Transport System) files
> -----------------------------------------------------
>
>                 Key: TIKA-874
>                 URL: https://issues.apache.org/jira/browse/TIKA-874
>             Project: Tika
>          Issue Type: Improvement
>          Components: mime
>    Affects Versions: 1.1, 1.2
>            Reporter: Peter May
>            Priority: Minor
>         Attachments: fits_support.patch
>
>
> Tika does not have a defined signature for application/fits files.  I have created a patch (based on file(1) magic) to address identification of such files, including a simple unit test.
> This patch only handles identification, not parsing of FITS files.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira