Changes between Initial Version and Version 1 of DataModel1.5Draft


Ignore:
Timestamp:
01/10/13 10:04:02 (6 years ago)
Author:
markh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • DataModel1.5Draft

    v1 v1  
     1= Draft of the CF Data Model 1.5 =
     2
     3This page is the working draft of the CF data model for CF 1.5, under the terms of reference of ticket 88.  The original discussion in ticket 68 have been closed and a new ticket opened to move adapt this draft model to a community accepted model.
     4
     5
     6== UML Sketch ==
     7
     8This sketch represents the model in its draft state, illustrating the relationships between types.
     9
     10== Constructs, Types ==
     11
     12These construct names have been agreed in principle and the detail of their specification is being worked upon.
     13
     14=== Field ===
     15
     16The Field is the atomic unit within the CF data model.  Fields are independent entities containing data and metadata.
     17
     18The Field defines a domain and one phenomenon described over that domain.  It contains a multi-dimensional array of data values, which may include missing data, and the metadata which define the domain.
     19
     20=== Coordinate ===
     21
     22A Field may contain one or zero Coordinates per dimension of the Field's data array.
     23
     24The Coordinate defines a phenomenon and data values for nominal points.  Optionally bounds may be defined.
     25
     26The Coordinate defines a domain_axis for the Fields domain.
     27
     28Coordinates are one-dimensional and strictly monotonic.
     29
     30=== !AuxiliaryCoordinate ===
     31
     32A Field may contain !AuxiliaryCoordinates referenced by dimensions of the Field's data array.
     33
     34A Field may contain many !AuxiliaryCoordinates per dimension of the Field's data array.
     35
     36!AuxiliaryCoordinates may be multi-dimensional and not definitively sortable.
     37
     38!AuxiliaryCoordinates further describe the Field's domain.
     39
     40=== !CellMeasure ===
     41
     42A Field may contain !CellMeasure referenced by dimensions of the Field's data array.
     43
     44A Field may contain many !CellMeasure per dimension of the Field's data array.
     45
     46!CellMeasures may be multi-dimensional and not definitively sortable.
     47
     48!CellMeasures quantify aspects of the Field's domain (where this is not derivable)
     49
     50=== !CellMethod ===
     51
     52A !CellMethod defines a process the data has undergone, qualifying the definition of the Field's phenomenon.
     53
     54A !CellMethod may contain a !CellMethod, forming an ordered list of !CellMethods.
     55
     56=== Transform ===
     57
     58A Transform defines a process which produces a defined result from a set of metadata inputs: Coordinates, !AuxiliaryCoordinates, !CellMeasures.
     59
     60e.g. A pair of !AuxiliaryCoordinates: latitude and longitude, from a projected spatial coordinate pair.
     61
     62 
     63==== Notes ====
     64
     65Wherever it is used for a Type, 'attributes' is a collection of key:value pairs: particular keys are banned from use for each type
     66
     67== Potential Constructs: Under Discussion ==
     68
     69
     70
     71=== Domain Axis ===
     72
     73=== !CoordinateReferenceSystem ===
     74 
     75
     76== Notes ==
     77
     78=== Qualified Associations ===
     79
     80The associations between the Field and its Coordinates and !CellMeasures are qualified associations.  These are UML concepts which denote a managed association without mandating how this association is managed; only the constraints of the relationship are detailed.
     81
     82E.g. a Field may have One or Zero Coordinates for each dimension which exists on the Field's Data Array.