[jira] [Comment Edited] (TIKA-1577) NetCDF Data Extraction

["Chris A. Mattmann (JIRA)" <ji...@apache.org>]

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

Chris A. Mattmann edited comment on TIKA-1577 at 5/8/15 11:23 PM:
------------------------------------------------------------------

Rishi:

Please see:
https://wiki.apache.org/tika/ScientificDataFormatTextRepresentation

Comments inline:
bq. Chris - what do you mean by "tabular"? Were you thinking about an HTML table representation instead? If so, what are your ideas on representing three-dimensional (and higher) arrays using HTML tables?

You can represent an N dimensional matrix as a table, easily, just have that many <td>s, each one representing the cols, and <tr>s each one representing the rows. [~gostep] and I even prototyped this.

bq. I was leaning on UL/LI because it was the approach already being utilized by the existing Tika netCDF variable content extraction code (i.e. for attribute extraction) and because a two-tag list structure is much easier think about than a three-tag table structure when applied to n-dimensional arrays. For example, UL/LI's are often nested (and developers expect them to be) whereas HTML tables are often used with a maximum of two-dimensions.

See above.



was (Author: chrismattmann):
Rishi:

Please see:
https://wiki.apache.org/tika/ScientificDataFormatTextRepresentation

Comments inline:
{blockquote}
Chris - what do you mean by "tabular"? Were you thinking about an HTML table representation instead? If so, what are your ideas on representing three-dimensional (and higher) arrays using HTML tables?
{blockquote}

You can represent an N dimensional matrix as a table, easily, just have that many <td>s, each one representing the cols, and <tr>s each one representing the rows. [~gostep] and I even prototyped this.

{blockquote}
I was leaning on UL/LI because it was the approach already being utilized by the existing Tika netCDF variable content extraction code (i.e. for attribute extraction) and because a two-tag list structure is much easier think about than a three-tag table structure when applied to n-dimensional arrays. For example, UL/LI's are often nested (and developers expect them to be) whereas HTML tables are often used with a maximum of two-dimensions.
{blockquote}

See above.


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