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
Add note about datatype in custom reader documentation #1130
Conversation
mraspaud
commented
Apr 2, 2020
•
edited
edited
- Fully documented
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this include a simple of example of how a user can preserve this? Something like a .where
example but using a 32-bit float NaN or something like that? Or mention astype
?
@@ -506,6 +506,18 @@ a convenience and are not required to read these formats. In many cases using | |||
the :func:`xarray.open_dataset` function in a custom file handler is a much | |||
better idea. | |||
|
|||
.. note:: | |||
Be careful about the data types of the datasets your reader is returning. | |||
It is easy to let the data being coerced into double precision floats. At the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
being
-> be
Codecov Report
@@ Coverage Diff @@
## master #1130 +/- ##
==========================================
+ Coverage 89.53% 89.53% +<.01%
==========================================
Files 200 200
Lines 29356 29384 +28
==========================================
+ Hits 26284 26310 +26
- Misses 3072 3074 +2
Continue to review full report at Codecov.
|
Congratulations 🎉. DeepCode analyzed your code in 0.011 seconds and we found no issues. Enjoy a moment of no bugs ☀️. 👉 View analysis in DeepCode’s Dashboard |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. This is reminding me though that I (we?) should more completely document how to handle integer category products and the use of _FillValue
. That can be done in a separate PR.
FYI I removed the |