Geospatial issue is null in hbase after interpretation - should never be null

12956
Reporter: omeyn
Assignee: omeyn
Type: Bug
Summary: Geospatial issue is null in hbase after interpretation - should never be null
Description: [~trobertson] will comment on whether null is acceptable when lat or lng are also null. If null is not acceptable, should it be 0 when lat and/or lng are null?
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-03-06 09:27:33.783
Updated: 2013-12-17 15:16:50.989
Resolved: 2013-03-06 15:52:46.777

Author: omeyn@gbif.org
Comment: This is a function of the interpreters which don't write a geospatial issue (so "null") when lat or lng are null. The question is whether this is desired behaviour.
Created: 2013-03-06 09:35:23.268
Updated: 2013-03-06 09:35:23.268

Author: trobertson@gbif.org
Created: 2013-03-06 09:52:07.635
Updated: 2013-03-06 09:52:07.635
        
Propose this is sensible:

NULL: no coordinates, so issue can't exist
0: coordinates exist with assertion that there are zero issues
XXX: bitwise encoded issue
    

Author: omeyn@gbif.org
Comment: UDFs were already behaving this way, now occurrence-interpreters does this too.
Created: 2013-03-06 15:52:46.805
Updated: 2013-03-06 15:52:46.805