v0.4.3
- NaN values in data are now not rendered (no need to add NaN as noDataValue)
Notice: The way of handling NaN in the shader is not clearly defined so different browser implementation could have different visualization results.
I would recommend converting NaN to a know noDataValue and using that value in the configuration (such as Number.MIN_VALUE)