CoordinateUncertaintyInMeters is lost in the interpreted view

17708
Reporter: trobertson
Assignee: cgendreau
Type: Improvement
Summary: CoordinateUncertaintyInMeters is lost in the interpreted view
Priority: Critical
Resolution: Fixed
Status: Closed
Created: 2015-07-21 18:56:18.064
Updated: 2016-04-27 08:52:26.103
Resolved: 2016-04-27 08:52:26.011
        
Description: Records with coordinateUncertaintyInMeters in the verbatim view such as
http://api.gbif.org/v1/occurrence/1088909149/verbatim do not return this in the interpreted view (even passing through the value unchanged) http://api.gbif.org/v1/occurrence/1088909149

This should be propogated as a decimal type.]]>
    

Author: mdoering@gbif.org
Created: 2015-07-21 21:11:31.837
Updated: 2015-07-21 21:12:36.852
        
It is lost in the interpreted view cause we did not properly finish the coordinateAccurracy interpretation, see POR-2374.

For all interpreted properties we remove the underlying verbatim terms as they potentially contradict our interpretations. These can be several like country and countryCode. In this case we excluded  coordinateUncertaintyInMeters already but do not interpret it. Quick fix would be to remove the term from the interpreted term set. Proper fix would be to solve issue POR-2374

See here for the currently removed terms which we (claim to) interpret:
https://github.com/gbif/occurrence/blob/master/occurrence-common/src/main/java/org/gbif/occurrence/common/TermUtils.java#L87
    

Author: peterdesmet
Comment: I also vote for interpreting rather than removing this kind of information. It is an encouragement for publishers to populate this kind of information. It's also a good indicator for fitness for use.
Created: 2015-11-17 13:45:47.167
Updated: 2015-11-17 13:45:47.167

Author: cgendreau
Created: 2016-04-01 15:17:46.527
Updated: 2016-04-01 15:17:46.527
        
coordinateUncertaintyInMeters and coordinatePrecision will be provided in the API response for the interpreted view.

First try was to provide it as BigDecimal: https://github.com/gbif/gbif-api/commit/9c1d7a2cde62bddbc2b752822ca0e4b464b34649


    

Author: cgendreau
Created: 2016-04-01 15:37:30.083
Updated: 2016-04-01 15:38:29.64
        
This will be reverted to use double due to interoperability issue between HBase and Hive.

Hive (with column type DECIMAL) will throw the following exception when trying to read BigDecimal stored in HBase:
{code:none}
Hive Internal Error: no LazyObject for org.apache.hadoop.hive.serde2.lazy.objectinspector.primitive.LazyHiveDecimalObjectInspector
{code}

Probably linked to https://issues.apache.org/jira/browse/HIVE-12378
This would require to update Hive to 1.3 or 2.0.