Investigate sensitive data display options

[peggynewman]

A number of issues in the past have revealed that when sensitive data is obfuscated and displayed as a random dot on a map, users have no visual indication that the dot has been obfuscated, and the obfuscation often lands us in a bit of hot water, eg recent examples of deer ending up in the ocean, or platypus ending up in a dam instead of a nearby waterway. These can be particularly problematic when the problem area is somebody's private property and becomes the target of management actions, or illegal hunters, or some other unwelcome attention.

This issue is to propose that we seek a solution to representing obfuscated data as something other than undifferentiated points on a map. One such solution may be to present the location as a shaded grid with the inference that the data is somewhere within the grid.

There is a paper on best practice for representing sensitive species that I recommend we review against our own SDS: https://docs.gbif.org/sensitive-species-best-practices/master/en/

Looping in @mjwestgate @elywallis @pbrenton for comment

[adam-collins]

• There is a mapping option driven by coordinateUncertaintyInMeters. When enabled, a circle is draw around points on the map at their uncertainty distance. This is suitable for generalised, already generalised and ordinary occurrences. Zoom level will determine if the uncertainty circle is visible.
• Rendering 2 map layers on top of each other, one with ungeneralised occurrences, another with the existing grid mapping option.
• Defaulting the biocache and BIE to display the occurrence grid instead of points is an option.