pydata / pydata/xarray

Expected an integer or an iterable of integers. Got None instead.

Open
#10,675 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs triage topic-zarr
Dominant language
Python
Stars
4.2k
Forks
1.4k
Avg merge
2d 15h
Merged PRs (30d)
14

Description

What is your issue?

I have the following xarray dataset

<xarray.Dataset> Size: 225kB
Dimensions:    (time: 1, lat: 78, lon: 143)
Coordinates:
    satellite  <U6 24B 'NOAA20'
  * time       (time) datetime64[ns] 8B 2025-01-24T01:17:04
  * lat        (lat) float64 624B 48.52 48.52 48.53 48.53 ... 48.89 48.9 48.9
  * lon        (lon) float64 1kB 4.142 4.147 4.152 4.157 ... 4.842 4.847 4.852
Data variables:
    values_i1  (time, lat, lon) float32 45kB -999.0 -999.0 ... -6.548e+07 -999.0
    values_i2  (time, lat, lon) float32 45kB -999.0 -999.0 ... -6.548e+07 -999.0
    values_i3  (time, lat, lon) float32 45kB -999.0 -999.0 ... -6.548e+07 -999.0
    values_i4  (time, lat, lon) float32 45kB -999.0 -999.0 ... 261.5 -999.0
    values_i5  (time, lat, lon) float32 45kB -999.0 -999.0 ... 254.4 -999.0
Attributes:
    regrid_method:  bilinear

I would like to save it as a zarr file.
Unfortunately when I try dr_out.load().to_zarr("regridded.zarr", mode="w") I get TypeError: Expected an integer or an iterable of integers. Got None instead.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the reported dr_out.load().to_zarr("regridded.zarr", mode="w") call from the issue. Trace the to_zarr entry point and the resulting TypeError, then verify that the same dataset can be written successfully and add coverage for this reported case if the project’s existing tests provide a suitable location.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.