tika-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Giovanni Usai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TIKA-1843) Tika parser for SEG-Y files and new MIME type application/segy
Date Mon, 01 Feb 2016 14:03:39 GMT

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

Giovanni Usai commented on TIKA-1843:

Hi Nick,
Sigrun owner has merged my modifications, so we can go on with the integration.

Do I have to perform the steps as per guide (http://central.sonatype.org/pages/ossrh-guide.html)
or they will be done by you?


> Tika parser for SEG-Y files and new MIME type application/segy
> --------------------------------------------------------------
>                 Key: TIKA-1843
>                 URL: https://issues.apache.org/jira/browse/TIKA-1843
>             Project: Tika
>          Issue Type: New Feature
>          Components: mime, parser
>            Reporter: Giovanni Usai
>            Priority: Minor
> This ticket refers to the parsing of SEG-Y files (extensions .seg, .segy and .sgy). 
> The SEG-Y format is used to store seismic data, you can find more information here http://pubs.usgs.gov/of/2001/of01-326/HTML/FILEFORM.HTM.
> I have:
> - added a new MIME type application/segy matching the file name extensions .segy, .seg
and .sgy.
> - created a new SEGYParser, matching that MIME type.
> In order to parse the SEG-Y files, I am using a modified version of the sigrun code (available
under Apache license, here https://github.com/mikhail-aksenov/sigrun). Notably I have done
a fix and changed some method signatures to be able to read from a ReadableByteChannel instead
of FileChannel.
> For the moment I have put it directly into the new Tika's segy package. Is this the right
thing to do or should I reference it as external library thus modifying the pom.xml?
> Thanks and best regards,
> Giovanni

This message was sent by Atlassian JIRA

View raw message