When doing reverse geocode in interpreters, consider using less precision to help with caching

13101
Reporter: omeyn
Assignee: omeyn
Type: Improvement
Summary: When doing reverse geocode in interpreters, consider using less precision to help with caching
Priority: Major
Resolution: Fixed
Status: Closed
Created: 2013-04-05 10:48:58.504
Updated: 2013-12-18 15:27:15.915
Resolved: 2013-04-08 15:34:46.591
        
Description: Many of the lat lng we see in modern datasets (e.g. ebird) have lat lng to 7 decimal points of precision. This corresponds to about 1cm [1], which apart from being highly unlikely (bleeding edge gps under perfect conditions can only get to about 1m) it's also unnecessary for our country lookups. If we can round or truncate to 4 or 5 decimal places we should increase our cache hits significantly, thereby speeding up the interpreter.

[1] http://en.wikipedia.org/wiki/Decimal_degrees
]]>
    

Author: omeyn@gbif.org
Comment: In discussion with [~trobertson@gbif.org] we've decided to round to 5 decimal places when presented with more than 5 as part of interpretation - not just the geo lookup.
Created: 2013-04-08 13:10:19.198
Updated: 2013-04-08 13:10:19.198

Author: omeyn@gbif.org
Comment: committed to occurrence-interp
Created: 2013-04-08 15:34:46.616
Updated: 2013-04-08 15:34:46.616