[
https://issues.apache.org/jira/browse/TIKA-443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12883159#action_12883159
]
Chris A. Mattmann commented on TIKA-443:
----------------------------------------
Hey Nick,
I think we need to support both cases (single lat/lon per document as well as
many lat/lon pairs per document). In the case of the former, it's easy, we have:
key: Metadata.LATITUDE
val: some lat
key: Metadata.LONGITUDE
val: some lon
And, in the case of the latter, we have:
key: Metadata.LATITUDE
val: some lat, some lat2, some lat3, some lat n...
key: Metadata.LONGITUDE
val: some lon, some lon2, some lon3, some lon n...
Because the keys are ordered in the Metadata object, I think that we can make
sure they match up and treat single points the same as for multiple points.
It's great to have support for both on a per Metadata object basis too since
many scientific data formats have both scenarios in them (e.g., NetCDF and HDF
typically have arrays of lats and lons, and sometimes, singe point values as
well).
The reason we need to support both is that distance computation (point/radius,
bounding box, and polygon) would require both scenarios to be supported. I've
been thinking that once this work is prototyped, to integrate Tika with the
work in SIS to build out a computational spatial library. I think Tika could be
used to feed in lats/lons into SIS.
Cheers,
Chris
> 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.
