-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0 used as missing data placeholder #6
Comments
This is a good point. The 0 values are rooted in the databases, and I have passed this issue on to the developing teams. Hopefully, we can eliminate these annoying 0s in future versions. |
For placeholders in the MySQL database, it is appropriate to replace
Unknown lat/long values are most accurately My understanding is Mindat's aim is to be a repository of mineral properties / attributes / etc first. Under "Open Geoscience Data", there are tools for "GeoCODES and "DataONE" for locality data. Cleansing data is a key part of the data science and data handling; there are many memes regarding the subject. For now, users can script out solutions: "if lat = 0, assign NULL to lat". Source: MySQL Reference Manual, Section B.3.4.3 Problems with NULL Values |
Noted, thank you for the advice and reference. I will forward your message to the Mindat database administrators. |
I've noticed that, for many fields, 0 is being used as a missing data representation. For latitude and longitude, however, this is particularly problematic, since 0N0E is a real place! (https://en.wikipedia.org/wiki/Null_Island). Testing for zero equality is also troublesome, since equality is ill-defined over floating point values (such as latitude and longitude).
Can the API return None or some other marker for these missing values instead of 0, or does the underlying data have the same ambiguity?
The text was updated successfully, but these errors were encountered: