Changes between Version 27 and Version 28 of PotentialDataModelTypes
 Timestamp:
 09/21/12 04:08:10 (7 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

PotentialDataModelTypes
v27 v28 68 68 * jonathan: This type is not included in the model of ticket 68. 69 69 * !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: 71 71 * !DimensionCoordinate: 72 72 * a long name name of 'easting' … … 90 90 * 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. 91 91 * !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: 93 93 * a definition of the OSGB CRS 94 94 * 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 latitudelongitude system. 95 95 * !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: 97 97 * !CellMethod 98 98 * a coordinate label of 'time'