search

NCAR / cesm-lens-aws

Examples of analysis of CESM LENS data publicly available on Amazon S3 (us-west-2 region) using xarray and dask
https://doi.org/10.26024/wt24-5j82
BSD 3-Clause "New" or "Revised" License
43 stars 23 forks source link

Intake-esm with long names #30

Closed jeffdlb closed 4 years ago

jeffdlb commented 4 years ago

I just uploaded 2 files that include CESM long names in the intake-esm catalog: https://ncar-cesm-lens.s3.us-west-2.amazonaws.com/catalogs/aws-cesm1-le-longNames.json https://ncar-cesm-lens.s3.us-west-2.amazonaws.com/catalogs/aws-cesm1-le-longNames.csv

I have not had a chance to test in a Notebook yet, but wanted to let people know in case someone wanted to try it.

-Jeff DLB

andersy005 commented 4 years ago

For better user experience, can we remove the spaces in the long_name column and use all lower case?

i.e . Net longwave flux at surface ---> net_longwave_flux_at_surface

andersy005 commented 4 years ago

Removing spaces would allow avoiding typos and other subtle errors when the user wants to use the long_name column in the search() method.

jeffdlb commented 4 years ago

Yes, but would rather in that case use the actual CF Standard Names (with underscores). Need to determine the correct mapping...

-Jeff

On Tue, Dec 10, 2019 at 10:16 AM Anderson Banihirwe < notifications@github.com> wrote:

For better user experience, can we remove the spaces in the long_name column?

i.e . Net longwave flux at surface ---> Net_longwave_flux_at_surface

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NCAR/cesm-lens-aws/issues/30?email_source=notifications&email_token=ABF4W4RRO5LAOBNSIMMRW43QX7MGXA5CNFSM4JYBQK52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGQHFRA#issuecomment-564163268, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABF4W4RU3BQYYV7PFANMF5DQX7MGXANCNFSM4JYBQK5Q .