Changes between Version 4 and Version 5 of FeatureTypeRules


Ignore:
Timestamp:
26/07/06 08:54:46 (13 years ago)
Author:
domlowe
Comment:

minor edits

Legend:

Unmodified
Added
Removed
Modified
  • FeatureTypeRules

    v4 v5  
    77For 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. 
    88 
    9  == So the current* CSML feature types are: == 
     9 == So the current* CSML coverage feature types are: == 
    1010 
    1111 * Point 
     
    1515 * Grid 
    1616 * !GridSeries 
    17  * Trajectory 
    1817 
    1918*currently under revision 
    2019 
    21  == So what are the defining characteristics of these features? ==  
     20 == So what are the defining characteristics of the domains of these features? ==  
    2221 
    2322 === Point: ===  
     23The 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 
    2425 === !PointSeries: ===  
     26The domain for a Point Series is a trajectory, which is a series of points in space at a series of times. 
     27 
    2528 === Profile: ===  
     29<come back to this> 
    2630 === !ProfileSeries: ===  
     31<come back to this> 
    2732 === Grid: ===  
     33The domain of a grid is defined by a set of axes in space and a single point in time. 
     34 
    2835 === !GridSeries: ===  
    29  === Trajectory: ===  
     36The domain of a !GridSeries is definied by a set of axes in space at multiple points in time. 
    3037 
    3138 == So can we make some rules that can be encoded? ==