ouault wrote:Jason,It looks like
something in the code asks a float64 field to be returned as a int32,
and thus NaN has to be turned into something else. That's perhaps
fine in the context where that happens with your file and could
potentially be silenced, but access to the file would be need
s why I was
suggesting that the warning be removed.
Jason
On 5/8/25 17:51, Even Rouault wrote:
Jason,
It looks like something in the code asks a float64 field to be
returned as a int32, and thus NaN has to be turned into something
else. That's perhaps fine in the context where that happen
/2025 à 23:01, Jason Roberts via gdal-dev a écrit :
Hi GDAL team,
I'm working with the GDAL Python API. I have some HFA (.img) files
that are float32 and that use nan as their NoData value. As far as I
can tell, using nan is allowed but I could be wrong. When I open
them, I get "
Hi GDAL team,
I'm working with the GDAL Python API. I have some HFA (.img) files that
are float32 and that use nan as their NoData value. As far as I can
tell, using nan is allowed but I could be wrong. When I open them, I get
"Warning 1: NaN converted to INT_MAX." Everything seems to work fin
