Changes between Version 1 and Version 2 of onScalarCoordinates


Ignore:
Timestamp:
07/03/13 07:33:02 (6 years ago)
Author:
markh
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • onScalarCoordinates

    v1 v2  
    33This page illustrates differences between tickets #104 and #105 for data creators using Scalar Coordinate Variables.
    44
    5 
    6 
    75In the examples, all variables are linked to a data variable, either as a coordinate variable or via the coordinates attribute, I have omitted this encoding to keep the table clearer.
    86
    9 The right hand column shows a number of current uses of scalar coordinates we have encountered in software creating CF NetCDF datasets.  All of these examples become invalid if #104 is implemented but remain valid if #105 is implemented.
     7The right hand column shows a number of current uses of scalar coordinates we have encountered in software creating CF NetCDF datasets.  All of these examples become invalid if #104 is implemented but remain valid if #105 is implemented. 
    108
    119The left hand column indicates how we would have to change the current operations and output if #104 is accepted as a change to CF. In many cases decisions have to be made about which structure to encode which are currently not deemed necessary.  In particular, these decisions are not currently made when the data set is written.  The choice of appropriate structure is very case dependent.
    1210
    13 The proposed change #104 adds significant complexity to the data writing process, imposing decisions on data creators which they are not currently making as they are not deemed necessary in the cases illustrated below.
    14 
    15 In all these cases #104 is driving a change in my behaviour as a data creator, where as #105 is enabling me to carry on as I currently work, whilst clarifying the interpretation.
     11The proposed change #104 adds significant complexity to the data writing process, imposing decisions on data creators which they are not currently making as they are not deemed necessary in the cases illustrated below.  For #104 we will have extensive need to re-engineer code and revisit data writing and reading capabilities, whilst retaining backwards compatibility with pre 1.7 CF data sets.
     12
     13In all these cases #104 is driving a change in my behaviour as a data creator, where as #105 is enabling me to carry on as I currently work, whilst clarifying the interpretation of my data for consumers.
    1614
    1715{{{