Missing pynio / Nio on AWS deployment - https://aws-uswest2.pangeo.io/

[chiaral]

I have been trying to install it locally (conda install -c conda-forge pynio) with no luck.

I know about cfgrib as an alternative engine to read grib files, but cfgrib does not like my grib files - pynio does (I tested it on another machine).

I tried to follow the instructions on https://github.com/pangeo-data/pangeo-docker-images but I think I opened the PR in the wrong repo chiaral/pangeo-docker-images#1 )

Can someone help me figure out how to do it properly?

pinging @scottyhq since it's for the AWS deployment :)

[scottyhq]

@chiaral looks like you almost got the PR submitted. Just make sure you're pointing at the "upstream" pangeo-docker-images repository (github's instructions here), but see this screenshot below:

[chiaral]

Thanks - I realized that. I am doing from the github page because I thought it was going to be easier than clone it and do it from my computer. However given that I know little about github I should have stuck to the 4 things I know how to do.

I don't know how and why (I haven't really done anything different!) but this time it worked!

[scottyhq]

no worries, it's easy to accidentally point to the wrong repo or branch, happens all the time.

FYI - the pangeo-docker-images are shared on all hubs (GCP too), and the fact that conda install pynio is hanging to find a solution makes me worried it has complicated dependencies. in case incorporating into the shared docker images does not work, you can try: mamba install pynio . I've noticed mamba succeeds where conda fails for adding some of these complex geospatial libraries into our existing environment.