Changes between Initial Version and Version 1 of Ticket #285


Ignore:
Timestamp:
02/28/09 19:27:07 (16 years ago)
Author:
arango
Comment:

Yes, thank you. I added the positive attribute to h. I also added the standard_name to lon_rho and lat_rho. That's a good suggestion.

I also modified various enumeration attributes with flag_values and flag_meanings.

Already, ROMS has the coordinates attribute. We never have problems in the past when using various post-processing NetCDF packages. I rechecked again compliace with the web ​interface. ROMS output files passes compliance for CF 1.0 to 1.4. However, I left the global attribute as CF 1.0.

I think that the problem is in Ferret and it should be fixed to be CF compliant. I have never used Ferret before so I don't know what are the problems. I don't think that adding a CPP option in ROMS to remove compliance is a good idea. Nowadays, the CF compliance is ROMS is strict. This was done to facilitate parallel I/O.

I alsp corrected a typo in metrics.F and normalization.F.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #285

    • Property Resolution → Done
    • Property Status new → closed

  • Ticket #285 – Description

    initial v1  
    1 Some visualization softwares are only able to handle ROMS' netcdf output files, when attributes for some variables are added. These attributes describe the relations between real world and model model coordinate systems and are in compliance with the CF-1.0 standard.
     1Some visualization softwares are only able to handle ROMS netcdf output files, when attributes for some variables are added. These attributes describe the relations between real world and model model coordinate systems and are in compliance with the '''CF-1.0''' standard.
    22
    3 I suggest to introduce the ''coordinate'' attribute, like
     3I suggest to introduce the ''coordinates'' attribute, like
    44
    55''h:coordinates   = "lon_rho lat_rho" ;''[[BR]]
    … …  
    2020This attribute allows to interpret the orientation of an axis. In the example the software might realize, that the deep is getting deeper for higher numbers. Unfortunately, some software packets do not evaluated this attribute.
    2121
    22 To prevent problems by introducing the additional parameters, I suggest to introduce a ''FLAG'', which is not set in the standard case. Since ferret, for example, gives a warning message when data containing the  ''coordinate'' attribute are loaded, these might cause a flood of trouble tickets and long discussions in the wiki. This might be preventable by setting ''undef FLAG''.
     22To prevent problems by introducing the additional parameters, I suggest to introduce a ''FLAG'', which is not set in the standard case. Since ferret, for example, gives a warning message when data containing the  ''coordinates'' attribute are loaded, these might cause a flood of trouble tickets and long discussions in the wiki. This might be preventable by setting ''undef FLAG''.
    2323
    2424