[
https://issues.apache.org/jira/browse/TIKA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14198059#comment-14198059
]
Martin Desruisseaux commented on TIKA-443:
------------------------------------------
A note just in case: Tika does not need to have a strong dependency to SIS if
you prefer to avoid it. The ISO 19115 metadata are defined by interfaces in a
separated JAR file, ({{geoapi-3.0.0.jar}}), which is in turn implemented by
SIS. But the Tika project could decide to implement itself a subset of the
interface considered most pertinent to Tika needs (e.g.
{{GeographicBoundingBox}}, {{DataIdentification}}, etc.), which should allow
Tika to switch between its own implementation as SIS implementation
transparently. For example Tika could have basic geographic information support
as a standalone application, and delegate to SIS only for more advanced needs
if the user wish.
I'm just mentioning that as one possible strategy.
> Geographic Information Parser
> -----------------------------
>
> Key: TIKA-443
> URL: https://issues.apache.org/jira/browse/TIKA-443
> Project: Tika
> Issue Type: New Feature
> Components: parser
> Reporter: Arturo Beltran
> Assignee: Chris A. Mattmann
> Attachments: getFDOMetadata.xml
>
>
> I'm working in the automatic description of geospatial resources, and I think
> that might be interesting to incorporate new parser/s to Tika in order to
> manage and describe some geo-formats. These geo-formats include files,
> services and databases.
> If anyone is interested in this issue or want to collaborate do not hesitate
> to contact me. Any help is welcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
