[OASIS Issue Tracker] (COEL-65) Add what3words capability to where field

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/COEL-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63092#comment-63092 ] 

Joss Langford commented on COEL-65:
-----------------------------------

I have spoken to the team at what3words:
- The reverse transfer from lat/long to what3words is open & RF - this allows anyone to find the the what3words code for their location and use it in a request for services. There is web API for anyone to access.
- The forward transfer from what3words to lat/long is open & RF when using the web API on a fair usage basis. The use of the off-line SDK has a royalty attached to it for commerical usage although this would be low (~£100pa) for non-profits.

Essentially, a Data Engine can receive and pass on what3words location codes in an open & RF way. If a Service Provide wants their Data Engine (or themselves) to convert what3words then for small volumes using the web API there is no cost but in large volumes using the off-line SDK there is a royalty to negotiate.

My take is that we can use the codes in the standard but Data Engines can not be obliged to convert them to lat/long.



> Add what3words capability to where field
> ----------------------------------------
>
>                 Key: COEL-65
>                 URL: https://issues.oasis-open.org/browse/COEL-65
>             Project: OASIS Classification of Everyday Living (COEL) TC
>          Issue Type: New Feature
>            Reporter: Joss Langford
>            Assignee: Joss Langford
>
> http://what3words.com/
> Allows the surface of the earth to be described down to a 3m grid. It has some interesting developing market mapping potential.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)