Skip to content

Latitude and Longitude on CPLHIST files have time dimension and shouldn't #709

Description

@ekluzek

I noticed this with the daily averaged CPLHIST data for ATM. The lat/lon variables are output with a time dimension and they shouldn't be.

So for example...

ncdump -h /glade/derecho/scratch/hannay/archive/b.e30_alpha09e_m.B1850C_MTso_Gris_Marbl.ne30_t233_wgx3.397/cpl/hist/b.e30_alpha09e_m.B1850C_MTso_Gris_Marbl.ne30_t233_wgx3.397.cpl.hx.atm.24h.avrg.0101-12-31-00000.nc
dimensions:
        time = UNLIMITED ; // (1 currently)
        ntb = 2 ;
        atmImp_nx = 48600 ;
        atmImp_ny = 1 ;
variables:
        double time(time) ;
                time:units = "days since 0001-01-01 00:00:00" ;
                time:calendar = "noleap" ;
        double time_bnds(time, ntb) ;
                time_bnds:bounds = "time_bnds" ;
        float atmImp_Faxa_bcph1(time, atmImp_ny, atmImp_nx) ;
.
.
.
         float atmImp_lon(time, atmImp_ny, atmImp_nx) ;
                atmImp_lon:long_name = "longitude" ;
                atmImp_lon:units = "degrees_E" ;
                atmImp_lon:standard_name = "longitude" ;
        float atmImp_lat(time, atmImp_ny, atmImp_nx) ;
                atmImp_lat:long_name = "latitude" ;
                atmImp_lat:units = "degrees_N" ;
                atmImp_lat:standard_name = "latitude" ;

// global attributes:
                :file_version = "cmeps0" ;
                :model_doi_url = "unset" ;
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions