Changes between Version 4 and Version 5 of FeatureTypeRules
 Timestamp:
 26/07/06 08:54:46 (13 years ago)
Legend:
 Unmodified
 Added
 Removed
 Modified

FeatureTypeRules
v4 v5 7 7 For example in atmospheric model output one timeslice of !GridSeriesFeature will look like a !GridFeature, yet it would be wrong to model this data as a collection of !GridFeatures. It should be a (collection of) !GridSeriesFeatures. The analysis code must therefore work out whether something that looks like a !GridFeature is actually part of a larger !GridSeriesFeature. 8 8 9 == So the current* CSML feature types are: ==9 == So the current* CSML coverage feature types are: == 10 10 11 11 * Point … … 15 15 * Grid 16 16 * !GridSeries 17 * Trajectory18 17 19 18 *currently under revision 20 19 21 == So what are the defining characteristics of the se features? ==20 == So what are the defining characteristics of the domains of these features? == 22 21 23 22 === Point: === 23 The domain is a single position in space and time.So a point feature it will be a single point in a spatial reference system at a single time (which may or may not be recorded). 24 24 25 === !PointSeries: === 26 The domain for a Point Series is a trajectory, which is a series of points in space at a series of times. 27 25 28 === Profile: === 29 <come back to this> 26 30 === !ProfileSeries: === 31 <come back to this> 27 32 === Grid: === 33 The domain of a grid is defined by a set of axes in space and a single point in time. 34 28 35 === !GridSeries: === 29 === Trajectory: === 36 The domain of a !GridSeries is definied by a set of axes in space at multiple points in time. 30 37 31 38 == So can we make some rules that can be encoded? ==