Skip to content
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

Missing measures #28

Open
visr opened this issue Dec 13, 2018 · 2 comments
Open

Missing measures #28

visr opened this issue Dec 13, 2018 · 2 comments

Comments

@visr
Copy link
Member

visr commented Dec 13, 2018

For measures, floats smaller than -1e38 are considered "no data".

Perhaps we should convert these to missing, and write missing to small floats.
This also goes for the Mmin and Mmax in the header, which will be missing if all measures are missing. If this is the right interpretation of the spec that is.

Came up in #25

@rafaqz
Copy link
Member

rafaqz commented Mar 28, 2022

Another option is to use a sentinel approach with a wrapper array type, and replace the missing values on the fly in getindex. This may have less performance cost for the cases where you don't actually use the measures data.

@visr
Copy link
Member Author

visr commented Mar 29, 2022

Yeah that could work as well. I'm not aware of anyone having needed support for this yet, I don't know how common it is. Perhaps we can even get away with just documenting it, and/or reading as NaN.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants