Hi-
Here is more information:
This is what I'm getting from Tika from *.fits file:
Content-Length: 40968000 Content-Type: application/fits X-Parsed-By:
org.apache.tika.parser.DefaultParser X-Parsed-By:
org.apache.tika.parser.gdal.GDALParser X-TIKA:digest:MD5:
cce03f62a68c09ec562f9e8e05b54b40 X-TIKA:digest:SHA256:
b3f0c61409cbd7f2c9aeb8bdfa0798d529383db699c1055b8a12a68267b948dd
resourceName: mirc0000.fits

I'm hoping to see something more like this (from the header extracted with
astropy.py):
SIMPLE = T / file does conform to FITS standard BITPIX = 16 / number of
bits per data pixel NAXIS = 3 / number of data axes NAXIS1 = 1280 / length
of data axis 1 NAXIS2 = 16 / length of data axis 2 NAXIS3 = 1000 / length
of data axis 3 EXTEND = T / FITS dataset may contain extensions COMMENT
FITS (Flexible Image Transport System) format is defined in
'AstronomyCOMMENT and Astrophysics', volume 376, page 359; bibcode:
2001A&A...376..359H BZERO = 32768 / offset data range to that of unsigned
short BSCALE = 1 / default scaling factor DATE = '2006-09-01T04:01:02' /
File creation date (YYYY-MM-DDThh:mm:ss UTC) TELESCOP= 'CHARA array 330m
max baseline, 6dishes' / Telescope

Thanks,
susan

On 2018/06/26 15:28:24, Susan Borda <[email protected]> wrote:
> Hi-
> I'm working with NetCDF and FITS files and I have Tika working for
> extracting the header text in NetCDF files but I can only get basic file
> metadata for FITS files. Does header text extraction not work on FITS
> files?
>
> Followed this for FITS:
> https://wiki.apache.org/tika/TikaGDAL
> And am only seeing the basic file metadata not the actual text from the
> header.
>
> This is what I'm using for NetCDF files (also used tika --gui to see the
> header text):
> curl -X -PUT --data-binary @age4_timeseries.nc http://localhost:9998/tika
> --header "Content-type: text/-t"
> curl -T age4_timeseries.nc http://localhost:9998/tika --header "Accept:
> text/plain"
>
> I've looked through the Tika Jira and found a reference from 2012:
> https://issues.apache.org/jira/browse/TIKA-874
>
> Any advice would be appreciated.
>
> Thanks,
> susan
>

Reply via email to