As part of the launch into production we found that people are adding observations to the project using other methods like the official Android iNat app or the iNat website. The problem with them using these other methods is the user might not set the geoprivacy to "obscured".
We have no power to automatically fix this* but we can help identify and manually fix the situation in the app. When we read the observations on iNat, we need to check if the geoprivacy is set to "open". If it is then warn the user and give them a button to fix it.
Actually we could but it'd be tricky to code it up, it's not what the user expects and automatically changing user data is questionable.
As part of the launch into production we found that people are adding observations to the project using other methods like the official Android iNat app or the iNat website. The problem with them using these other methods is the user might not set the geoprivacy to "obscured".
We have no power to automatically fix this* but we can help identify and manually fix the situation in the app. When we read the observations on iNat, we need to check if the geoprivacy is set to "open". If it is then warn the user and give them a button to fix it.