Issue 14420

Geocode reverse lookup needs improvement

14420
Reporter: omeyn
Assignee: mblissett
Type: Improvement
Summary: Geocode reverse lookup needs improvement
Description: The geo lookup ws used by coord interp is showing some flaws. Part of the problem is not honouring source projections of coords, and part of it is the ws base layers not matching up perfectly. PF-1354 shows one example where it looks like the land layer and eez leave a gap. This can be improved by fuzzying the lookup (maybe reduce precision) or improving the base layers, or both.
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-11-28 15:37:16.673
Updated: 2017-08-21 19:31:37.859
Resolved: 2017-08-21 19:30:32.469


Author: trobertson@gbif.org
Created: 2015-11-20 09:50:08.291
Updated: 2015-11-20 09:50:08.291
        
Here is a good example of a "border case".  A record with ISO, country and coordinates is incorrectly receiving a flag of "country coordinate mismatch"
http://www.gbif.org/occurrence/217745359

    


Author: cgendreau
Created: 2015-11-20 09:58:20.744
Updated: 2015-11-20 10:32:11.74
        
geocode-ws returns Spain : http://api.gbif.org/v1/geocode/reverse?lat=41.038795231273376&lng=-6.921280251735951
Ideally, it should probably return Spain and Portugal.

But, if we query the latest version from http://www.marineregions.org/eezsearch.php, we get Portugal so this case might be solved by updating the EEZ database.
    


Author: mblissett
Created: 2016-02-05 16:38:14.972
Updated: 2016-02-05 16:38:14.972
        
The updated database is still returning Spain: http://api.gbif-dev.org/v1/geocode/reverse?lat=41.038795231273376&lng=-6.921280251735951

So I need to look into this further, maybe check the shape file resolution we are using is appropriate for our coordinate accuracy.

Google also says it's in Portugal, about 200m from the Spanish border.
https://www.google.dk/maps/place/41%C2%B002'19.7%22N+6%C2%B055'16.6%22W/@41.0375008,-6.9244476,16z/


    


Author: mblissett
Created: 2016-04-21 12:24:14.12
Updated: 2016-04-21 12:24:14.12
        
Extra examples:

http://www.gbif.org/occurrence/1212484753
http://www.gbif-uat.org/occurrence/1212486039
http://www.gbif-uat.org/occurrence/1212407933

And more linked to PF-2249

    


Author: cgendreau
Comment: Moved to https://github.com/gbif/geocode/issues/1
Created: 2017-04-19 14:01:38.437
Updated: 2017-04-19 14:01:38.437


Author: mblissett
Comment: Fixed, allowing more tolerance (5km, 25km) from geocoder.
Created: 2017-08-21 19:30:32.521
Updated: 2017-08-21 19:30:32.521