Replies: 2 comments 2 replies
-
|
I don't see anything in the code explicitly casting to This might be helpful: https://github.com/pyproj4/pyproj/blob/8f0e1f7ddc5ba5a1992f939f91bb9ea023316219/pyproj/utils.py#L34-L52 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @snowman2. This class is helpful, but the JSON encoding is called by rioxarray/rioxarray/rioxarray.py Line 874 in a0322e9 The "issue" is in the _chached_transform() function: rioxarray/rioxarray/rioxarray.py Line 503 in a0322e9 When calling Affine.from_gdal() and passing the np.fromstring as argument. From this point, all computations will be in numpy.float64 dtype... |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Hi Guys,
Any reason for the methods .bounds() and .transform() return the values in
numpy.float64instead of standard python float?This error was being raised when creating a STAC catalog and using
rioxarrayto get footprint, bounds, etc. and the code was working fine when using plainrasterio. Debugging was tricky as the representation of these values is the same in the dictionary and a manual type casting was necessary for each single value. :(Beta Was this translation helpful? Give feedback.
All reactions