Uploaded image for project: 'Hyrax-Kanban'
  1. HK-40

Renaming of shared dimensions doesn't work (and should) - Could be duplicate of renaming a variable

    Details

    • Type: Bug
    • Status: Done (View workflow)
    • Priority: Highest
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:

      Description

      Hi James,

      Our preliminary tests show that the NcML module still cannot recognize dimension name changes. I include an email below of our early correspondence with John Caron about the NcML schema, and the example for the dimension change in ncml that we desire.

      If I attempt to "remove" existing dimensions in order to redefine my own, Hyrax would issue an error saying that this version of the module only supports removal of attributes and variables.

      One consequence is that the fonc module wouldn't honor such changes in NcML either (though not recognizing, the NcML module never complained about the attempted dimension changes as long as I don't remove any existing dimension).

      I wonder if this can be implemented in the module after all? Do you have an idea of how long it'd take to do it? Perhaps I didn't emphasize but this feature would be highly important for our data service.

      I did verify that the fonc module no longer prepends "h4_", "h5_", or "ncml_" in front of the variable or attribute names when downloading in netcdf, which is good.

      -Fan

      On 06/18/11 10:24, John Caron wrote:
      On 6/17/2011 11:44 AM, Gallagher James wrote:
      John,

      We have some users of ncml that are trying to rename dimensions using ncml that looks like:

      <dimension name="latitude" length="180" />
      <dimension name="longitude" length="360" />
      
      <variable name="aerosol_opt_001" shape="latitude longitude">
         <attribute name="coordinates" type="String" value="latitude longitude" />
      </variable>
      

      where "aerosol_opt_001" is a variable in an existing file and it's dimension names in that file are some useless gibberish. When they slurp their ncml into panoply and IDV, the dimensions are renamed; our ncml code doesn't do this, however. I checked the on-line docs and it wasn't clear (but was sort of implied) that this syntax was supposed to rename dimensions. Is it?

      Thanks,
      James
      --
      James Gallagher
      jgallagher at opendap.org
      406.723.8663

      John's reply:

      I think that the above does work in NcML, because the new shared
      dimension objects are created and added to the file, then they are used
      by the variables as usual. ill make a note to improve the docs.

        Attachments

          Issue links

            Activity

              People

              • Assignee:
                skorolev Slav Korolev
                Reporter:
                jimg James Gallagher
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - 1 day
                  1d
                  Remaining:
                  Remaining Estimate - 1 day
                  1d
                  Logged:
                  Time Spent - Not Specified
                  Not Specified