Changes between Version 27 and Version 28 of PotentialDataModelTypes


Ignore:
Timestamp:
09/21/12 04:08:10 (7 years ago)
Author:
markh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • PotentialDataModelTypes

    v27 v28  
    6868  * jonathan: This type is not included in the model of ticket 68.
    6969 * !DimensionCoordinate (Coordinate):
    70   * The example ScalarField may be defined with respect to a regular horizontal grid; this Field would have:
     70  * The example !ScalarField may be defined with respect to a regular horizontal grid; this Field would have:
    7171   * !DimensionCoordinate:
    7272    * a long name name of 'easting'
     
    9090    * a 2D array of values, size:(n,m). jonathan: In the model of ticket 68, the !AuxiliaryCoordinate identifies its dimensions, but their size is part of the Dimensions constructs concerned.
    9191 * !CoordinateSystem:
    92   * The spatial Coordinates of the ScalarField may be defined with respect to a coordinate reference system:
     92  * The spatial Coordinates of the !ScalarField may be defined with respect to a coordinate reference system:
    9393   * a definition of the OSGB CRS
    9494  * jonathan: This type is not included in the model of ticket 68. We argue that coordinate systems are implicitly assembled by operations which want to use them, since they know what they are interested in, and/or implied by the Transforms of the Field. For instance, a Transform describes the OSGB CRS; it's a ''relationship'' between the map projection system and the latitude-longitude system.
    9595 * !CellMethod:
    96   * The values in the ScalarField are aggregated over time, so the Field has:
     96  * The values in the !ScalarField are aggregated over time, so the Field has:
    9797   * !CellMethod
    9898    * a coordinate label of 'time'