NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
My conclusion from this is that _FillValue should never be used to indicate a default value for valid data, because it will be treated exactly as if it were missing, or never written, by most applications.OK, you have convinced me this would be a very confusing & stupid thing to do. But I suspect John Caron still wants a rule to handle this case if it does occur. I think it would be reasonable in this case to treat the _FillValue as valid.
thanks for thinking of my problem. right now im working on an implementation that would follow brian's rules as default, but still allows a user to implement confusing and stupid things if they want :^}
"the great thing about standards is that there's so many to choose from!"
netcdfgroup archives: