Amy Steiker

icon indicating a website link https://nsidc.org

icon company National Snow and Ice Data Center icon location Boulder, CO icon location Data Services Engineer at the National Snow and Ice Data Center, University of Colorado at Boulder

Results 55 comments of Amy Steiker

Define a common `read_h5` function for _h5py + pandas_ and _dask array_

I _think_ your Issue was originally filed in reference to IceFlow. So perhaps this is better left under their backlog versus an addition to our Tutorials repo itself?

Define a common `read_h5` function for _h5py + pandas_ and _dask array_

[CRYO-199] [CRYO-199]: https://nsidc.atlassian.net/browse/CRYO-199?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

Integrate data-access-notebook

Test comment.

Add some error handling before processing results from CMR in "Customize and Access NSIDC Data" notebook

[CRYO-200] [CRYO-200]: https://nsidc.atlassian.net/browse/CRYO-200?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

New access patterns for NOAA@NSIDC data

[CRYO-195] [CRYO-195]: https://nsidc.atlassian.net/browse/CRYO-195?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

Break out h5coro notebook into separate tutorial folder

[CRYO-196] [CRYO-196]: https://nsidc.atlassian.net/browse/CRYO-196?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

Suggest using xarray and cartopy for SMAP tutorial 2

[CRYO-203] [CRYO-203]: https://nsidc.atlassian.net/browse/CRYO-203?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

NameError: name 'Boundingshape' is not defined

[CRYO-201] [CRYO-201]: https://nsidc.atlassian.net/browse/CRYO-201?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

Error messages when user hasn't accepted dataset EULA can be confusing

The UMM-C (CMR Collection) schema was updated to include EULA information, so this can now be determined programmatically by a client in order to provide better error handling: https://bugs.earthdata.nasa.gov/browse/SDRT-1236. I...

Error messages when user hasn't accepted dataset EULA can be confusing

@mfisher87 I believe there is indeed data in the 403 response that tells a client whether or not the EULA was accepted. The EULA response was utilized in the Harmony...