[ 
https://issues.apache.org/jira/browse/TIKA-862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209788#comment-13209788
 ] 

Chris A. Mattmann commented on TIKA-862:
----------------------------------------

Hi Richard, thanks. Do you know why the other file wouldn't work with h5dump? 
Do you think it's related to Tika not parsing it too? Tika uses the NetCDF Java 
library, so I'm wondering if they are related....
                
> JPSS HDF5 files not being detected appropriately
> ------------------------------------------------
>
>                 Key: TIKA-862
>                 URL: https://issues.apache.org/jira/browse/TIKA-862
>             Project: Tika
>          Issue Type: Bug
>          Components: parser
>    Affects Versions: 1.0
>            Reporter: Richard Yu
>            Assignee: Chris A. Mattmann
>         Attachments: 
> RNSCA-ROLPS_npp_d20120202_t1841338_e1842112_b01382_c20120202203730692328_noaa_ops.h5,
>  
> RNSCA-ROLPS_npp_d20120202_t1841338_e1842112_b01382_c20120202203730692328_noaa_ops.h5,
>  
> RNSCA_npp_d20111121_t1935200_e1935400_b00346_c20111122203300301515_noaa_ops.h5
>
>
> As commented in TIKA-614, JPSS HDF 5 files are not being properly detected by 
> Tika. See this:
> from [~minfing]:
> {quote}
> We were trying to extract metadata from our h5 file (i.e. with JPSS 
> extension). We ran the following command line:
> {noformat}
> [ryu@localhost hdf5extractor]$ java -jar tika-app-1.0.jar -m \
> > /usr/local/staging/products/h5/SVM13_npp_d20120122_t1659139_e1700381_b01225_c20120123000312144174_noaa_ops.h5
> Content-Encoding: windows-1252
> Content-Length: 22187952
> Content-Type: text/plain
> resourceName: 
> SVM13_npp_d20120122_t1659139_e1700381_b01225_c20120123000312144174_noaa_ops.h5
> [ryu@localhost hdf5extractor]$
> {noformat}
> We noticed that the content type in text/plain and only 4 lines of output 
> (i.e. we expected al lots of metadata).
> Let me know if more information is needed. Thanks!
> Richard
> {quote}

--
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

        

Reply via email to