Uploaded image for project: 'JASMIN CIS'
  1. JASMIN CIS
  2. JASCIS-175

collocation creates lon/lat field (unwanted)

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not yet addressed
    • Affects Version/s: None
    • Fix Version/s: DummyVersion
    • Component/s: None
    • Labels:
      None

      Description

      I will use the following data:
      /group_workspaces/jasmin/cis/data/aeronet/AOT/LEV20/ALL_POINTS/920801_121229_Yakutsk.lev20

      and

      /group_workspaces/jasmin/cis/data/ECHAM_fixed/2007_2D_3hr/od550aer.nc

      I first aggregate the AERONET data:
      cis aggregate AOT_440:yakutsk.lev20 t=[2007-01-01T00,2008-01-01T00,PT6H] -o yakutsk2007_aggregated

      I then linearly colocate the ECHAM data with the aggregated AERONET data:
      cis col od550aer:od550aer.nc yakutsk2007_aggregated.nc:colocator=lin -o od550_at_yakutsk_aggregated

      ncdump -h on the resulting file shows:
      netcdf od550_at_yakutsk_aggregated {
      dimensions:
      time = UNLIMITED ; // (1460 currently)
      lat = 96 ;
      lon = 192 ;

      so suddenly a single AERONET site (one lon/lat pair) has led to a global field??

      Consequently data cannot be used for further processing (plot, stats)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              schutgens@atm.ox.ac.uk Nick Schutgens
              Participants:
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: