8000 Add FAQ entries for to_netcdf int64 error and ee.Geometry conversion by jdbcode · Pull Request #309 · google/Xee · GitHub
[go: up one dir, main page]

Skip to content

Add FAQ entries for to_netcdf int64 error and ee.Geometry conversion - #309

Merged
jdbcode merged 1 commit into
mainfrom
docs-faq-netcdf-int64
Apr 21, 2026
Merged

jdbcode merged 1 commit into
mainfrom
docs-faq-netcdf-int64

Conversation

@jdbcode
@jdbcode jdbcode commented Apr 21, 2026
Copy link
Copy Markdown
Member

Adds two new FAQ entries to docs/faq.md:

  1. ds.to_netcdf() fails with int64 cast error — Explains that Xee time coordinates use int64, which the scipy netCDF writer cannot handle (netCDF3 is limited to int32). Documents that Xarray selects backends in order netcdf4 → h5netcdf → scipy, so the error only occurs when neither netcdf4 nor h5netcdf is installed. Provides three fixes: install netCDF4, install h5netcdf, or pass engine= explicitly to .to_netcdf(). Also mentions .to_zarr() as an alternative. Relates to issue Writing NetCDF file fails with ValueError #194.

  2. Shapely geometry conversion — Updates the existing shapely entry to include the concrete conversion snippet shapely.geometry.shape(ee_geom.getInfo()) for users passing an ee.Geometry to fit_geometry.

@jdbcode
jdbcode force-pushed the docs-faq-netcdf-int64 branch from 625cb46 to ee80032 Compare April 21, 2026 23:40
@jdbcode
jdbcode merged commit ee1e779 into main Apr 21, 2026
6 checks passed
@jdbcode
jdbcode deleted the docs-faq-netcdf-int64 branch May 5, 2026 23:28
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

Successfully merging this pull request may close these issues.

1 participant

0