Changes between Version 7 and Version 8 of MolesDiscussion


Ignore:
Timestamp:
17/07/06 16:56:44 (13 years ago)
Author:
lawrence
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MolesDiscussion

    v7 v8  
    7373 * The other elements are rather obvious, but ... 
    7474   * Note that we would expect to use the dgStdParameterMeasured variable to encode both the phenomenon name and the cell bounds (so we get the averaging information  here). ''Can we promote something useful from the CF cell methods? Ticket Needed'' 
    75  * I suppose we imagine a granule of consisting of multiple phenomena with multiple feature types, but we would expect that any one phenomenon in one granule to have one feature type (''Andrew/Dominic?''). In which case the feature type name and the feature type catalogue from which it is governed should also be encoded per parameter. However, one might argue that the assumption might be violated, and in any case, at this point the user might be pointed to the WFS level. ''It would certainly be simpler, and possibly more useful to generate a list of feature types present in the granule (along with their FTC 
    76 antecedents).'' ''Yes/No? Ticket Needed?!'' 
     75 * I suppose we imagine a granule of consisting of multiple phenomena with multiple feature types, but we would expect that any one phenomenon in one granule to have one feature type (''Andrew/Dominic?''). In which case the feature type name and the feature type catalogue from which it is governed should also be encoded per parameter. However, one might argue that the assumption might be violated, and in any case, at this point the user might be pointed to the WFS level. ''It would certainly be simpler, and possibly more useful to generate a list of feature types present in the granule (along with their FTC antecedents).'' ''Yes/No? Ticket Needed?!'' 
    7776 
    7877Now we have this information at the granule level, how much of it should be summarised up at the data entity level by the moles creator? (''Ticket: We would need tools to do this!'') 
     
    9291[[Image(DataEntityGeneral1.jpg)]] 
    9392 
    94  * The dgDataSet Type should allow 'Mixed' (as for example both model and obs may be included in a dataset). ''One assumes these are effectively booleans?''''Ticket!'' 
     93 * The dgDataSet Type should allow 'Mixed' (as for example both model and obs may be included in a dataset). ''One assumes these are effectively booleans? Ticket!'' 
    9594 * I don't really understand dbBasicData and dgDerivedData. In particular, the basic data context is really about listing the feature types, but we think we have that elsewhere, and we have in the dgDataSet information as to whether the data is simulated or an analysis. The only other option is that the data has been processed (derived) in someway, in which case there is utility in providing links to underlying datasets ''but these ought to be DataEntities not data granules'' ... assuming that the detailsof teh derivation/processing are in the dpt, the links are all that are really needed. The choice of timeseries, integration etc is redundant as that information exists in the feature type and phenomenon information. ''Remove most of this section in the schema?'' 
    9695