Custom Query (124 matches)
Results (7 - 9 of 124)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#8 | fixed | Identifying horizontal coordinate variables using the axis attribute | cf-conventions@… | jonathan |
Description |
1. TitleIdentifying horizontal coordinate variables using the axis attribute 2. ModeratorRuss Rew 3. RequirementA method is needed to identify which are the horizontal coordinate axes of a data variable 4. Initial Statement of Technical ProposalThe axis attribute of coordinate variables (1D, in the Unidata sense) is optional. The value axis="X" can be used on a longitude coordinate variable (CF 4.2), and axis="Y" on a latitude coordinate variable (CF 4.1) (case-insensitive). CF is ambiguous about its use on other coordinate variables. The introduction of CF 4 states that the axis attribute is recommended for other kinds of spatial coordinate, but without giving an interpretation to its values. However in CF 4.1 and 4.2 it is prohibited for coordinate variables of rotated latitude and longitude. This proposal aims to clarify the use of the axis attribute for horizontal coordinate variables. The proposal is
5. BenefitsThe axis attribute, thus redefined, provides a clear way to identify horizontal coordinate variables and horizontal auxiliary coordinate variables. As an example, we can modify the one in CF 5.2: dimensions: xc = 128 ; yc = 64 ; lev = 18 ; variables: float T(lev,yc,xc) ; T:long_name = "temperature" ; T:units = "K" ; T:coordinates = "lon lat" ; float xc(xc) ; xc:axis="X"; xc:long_name = "x-coordinate in Cartesian system" ; xc:units = "m" ; float yc(yc) ; yc:axis="Y"; yc:long_name = "y-coordinate in Cartesian system" ; yc:units = "m" ; float lev(lev) ; lev:long_name = "pressure level" ; lev:units = "hPa" ; float lon(yc,xc) ; lon:long_name = "longitude" ; lon:units = "degrees_east" ; float lat(yc,xc) ; lat:long_name = "latitude" ; lat:units = "degrees_north" ; The axis attributes identify xc and yc as horizontal dimensions, and indicate that xc-yc-up is right-handed. Because xc and yc are the dimensions of lon and lat, these auxiliary coordinate variables are also implied to be horizontal. In this case, we can also deduce that from the fact that they are identifiable as longitude and latitude, but for a general 2D coordinate variable it might not be obvious. There is no backward incompatibility because the redefinition permits the axis attribute in cases where it was formerly not allowed, but does not change its meaning in existing cases. 6. Status QuoWith the CF standard as it is, latitude and longitude coordinate variables can be identified by their units or standard_name, and they are well known to be horizontal. Other horizontal coordinate variables can be identified only by recognising specific standard_names e.g. those in Appendix F on map projections. The axis attribute is a more general solution that works without any knowledge of the possible choices of horizontal grid. |
|||
#9 | wontfix | Extensions to CF grid mapping attributes to support coordinate reference system properties | cf-conventions@… | pbentley |
Description |
1. TitleProposed Extensions to CF Grid Mapping Attributes to support CRS Properties 2. ModeratorJonathan Gregory 3. RequirementPrevious posts to the CF mailing list have identified the requirement for additional attributes that could be used to provide a fuller definition of the characteristics of the coordinate reference system (CRS) used by spatial coordinates within a netCDF file. This proposal attempts to define attributes for several commonly used CRS properties. 4. Initial Statement of Technical ProposalOwing to the length of this proposal, the full specification text is included in the attached PDF document. (NB: If it is considered more convenient, e.g. for discussion purposes, to upload the full text of this proposal into this Trac ticket, then the author is happy to do so.) 5. BenefitsScope: potentially all producers and end-users of netCDF datasets could exploit the proposed new attributes. New capabilities: the proposed new attributes would enable data producers to more accurately record the specific characteristics of the coordinate reference system (or systems) used to define spatial coordinates within netCDF files. Example use-case 1: A data producer has collected meteorological observations using a sensor platform which uses, for example, a particular geodetic datum (e.g. WGS 84, NAD 83, OSGB 36) to record spatial coordinates. It is desirable for this piece of CRS metadata, and others like it, to be recorded in appropriate netCDF CF attributes. Example use-case 2: A climate data center wishes to convert a legacy dataset to netCDF format and make it available over the internet. The legacy dataset is based upon an unusual or customised coordinate reference system (e.g. transverse mercator projection using, say, the Clarke 1880 ellipsoid). As before, these CRS details need to be encoded in agreed, standardised CF attributes. 6. Status QuoThe author is not aware of alternative CF attributes or mechanisms that could be used to encode the desired additional CRS properties. |
|||
#11 | duplicate | A standard for CF variable names ("short names") should be added. | cf-conventions@… | balaji |
Description |
1. Title
2. Moderator
3. Requirement
This name is not currently included in the standard, though some de facto standards exist. In the absence of a standard, users cannot write scripts or methods that are general enough to apply across datasets from many sources. For instance, a typical user request from GFDL is to make our internal variables names match what PCMDI (via the CMOR program) required for IPCC AR4: this would enable users who have developed new scientific analyses on their own data to apply them instantly to any model in the IPCC archive. The CF standard_name attribute does not satisfy this need. Shortcomings include:
4. Initial Statement of Technical ProposalWe propose a list of "CF short names".
5. BenefitsBenefits and use cases are coverd in some slides prepared for GO-ESSP are attached here, and also available from Balaji's home page. 6. Status Quo
|