[
https://issues.apache.org/jira/browse/TIKA-3974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17689795#comment-17689795
]
Tim Allison commented on TIKA-3974:
-----------------------------------
Looks like there are a number of other namespaces that include "...:latitude":
"event:location:latitude", OpenGraph og:latitude and og:longitude
"og:longitude":"-74.00076130000002"
"og:latitude":"40.7207559"
playfoursquare:
"playfoursquare:location:latitude":"-22.99775416607306"
"playfoursquare:location:longitude":"6.447639"
Should probably be fairly general?
> Normalize location coordinates in html metadata
> -----------------------------------------------
>
> Key: TIKA-3974
> URL: https://issues.apache.org/jira/browse/TIKA-3974
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Minor
>
> In grepping for latitude in our regression corpus, I've noticed quite a few
> html pages with geo.position fields
> {{"geo.position":"-38.3350080000;175.1659500000"}} and/or
> {{"place:location:latitude":"-38.3350080000}} and
> {{"place:location:longitude":"175.1659500000"}}. We recently started
> normalizing dublin core elements. We should do the same for geo location.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
