[
https://issues.apache.org/jira/browse/TIKA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883171#action_12883171
]
Nick Burch commented on TIKA-443:
---------------------------------
I was thinking that making sure you put in the right matching pairs, and remove
them again is a little fiddly, but that's nothing that a little wrapper library
wouldn't fix for you. With that in mind, I think your proposed solution is
likely to be much better than changing tika to support composite values, with
the problems that that would bring
Any objections to creating a new Metadata keyspace of Geographic, with to start
with LATITUDE = geo:latitude & LONGITUDE = geo:longitude ? I can think of a few
others we might want in future (height, bearing etc), which makes me think its
own space might make sense
> 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
> 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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
