No: there is also a bug if you type in your localities that corrupts them: lots of people dont notice this corruption.
Among regular users they have had to resourt to copy pasting the longitude - simply typing the digits corrupts the data.
The corruption kicks in at 2 decimal points and further typing is impossible. One has to type a digit, then delete the ca15 digits added, then type another digit then delete the ca15 digits added, then type another digit then etc. until you are finished. HIDEOUS. And now still operative 3 months later.
All data for longitude, no matter how they are inputted are apparently snapped to a grid at consequently get 15 significant digits even if only four are entered, thereby SCREWING UP THE LOCALITY RESOLUTION.
- does it with the default location
- does it with data from exif from pictures
- does it with copy pasting the data
- it totally messes up trying to type longitude
- I cannot test it with the "Use an existing locality" because that functionality has been lost.
Only clicking on the map seems immune to this, but the map has a bug of not recording the resolution and records everything to 15 decimal places even if the resolution is in fact 1000km!
The old site had this working! This is thus a bug, and one that the Open University vowed to honour as a condition of Southern Africa joining iSpot because they did not want to explicitly record locality resolution.
Please get this fixed!