Welcome @nina.aragon, and thanks for posting your question!
You’re right to be confused by these contradictory messages! They’re the result of using granule (file) metadata to perform an initial, fast search for data prior to order/download of that data. The initial query step (
region.avail_granules()) uses summary metadata to identify granules that likely have data where you’re interested, so it often returns a few granules that might have a few border pixels within your area of interest. However, when the subsetter actually runs (as part of
region.download_granules()), it’s finding that there are no data points within your region of interest. Figure 1 on this page has a pictorial representation of this phenomena that can be helpful to understand what’s going on.
In short, what the error is telling you is that there is no ICESat-2 data available for the region (and time period) you specified. NSIDC is also working to minimize this issue (by improving the granule metadata) and provide clearer error reporting. If you have found data for the constraints you are using through another source (e.g. Earthdata or OpenAltimetry), then that points to a potential issue in icepyx that we should look into.
I’d suggest expanding either your temporal or spatial search parameters to see if you can find some data for your area. Please let us know if you continue to have this issue.