[
https://issues.apache.org/jira/browse/TIKA-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14538330#comment-14538330
]
Rishi Verma commented on TIKA-1577:
-----------------------------------
That being said, fully nested tables, where a <td> contains an entire table
structure within it seems to be okay. This might make sense to do so that the
XHTHL output is on par with the Tika Excel structured output (which is limited
to being 2-D I believe).
I'm going to think about this a bit and see what may work.
> NetCDF Data Extraction
> ----------------------
>
> Key: TIKA-1577
> URL: https://issues.apache.org/jira/browse/TIKA-1577
> Project: Tika
> Issue Type: Improvement
> Components: handler, parser
> Affects Versions: 1.7
> Reporter: Ann Burgess
> Assignee: Ann Burgess
> Labels: features, handler
> Fix For: 1.9
>
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> A netCDF classic or 64-bit offset dataset is stored as a single file
> comprising two parts:
> - a header, containing all the information about dimensions, attributes, and
> variables except for the variable data;
> - a data part, comprising fixed-size data, containing the data for variables
> that don't have an unlimited dimension; and variable-size data, containing
> the data for variables that have an unlimited dimension.
> The NetCDFparser currently extracts the "header part".
> -- text extracts file Dimensions and Variables
> -- metadata extracts Global Attributes
> We want the option to extract the "data part" of NetCDF files.
> Lets use the NetCDF test file for our dev testing:
> tika/tika-parsers/src/test/resources/test-documents/sresa1b_ncar_ccsm3_0_run1_200001.nc
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
