Ecoinformatics site parent site of Partnership for Biodiversity Informatics site parent site of REAP - Home


 

 

 

O Pe NDAP/Kepler Data Model Resolution
Your trail: Feb07DevMeeting | MeetingNotesFeb07 | DevelopmentDocuments | APIDesign | UseCases | Ocean_use_case_searching | Terrestrial_usecases | SearchingUIMockUps | TerrestrialUseCaseHardware | SiteLogs

Difference between version 2 and version 1:

At line 0 added 1 line.
+ The OPeNDAP data model (aka the DAP2 data model) supports more complex data objects than the Kepler/Ptolmey data model. In particular DAP2 supports deeper hierarchies and N-imensional arrays. Although these data can find logical representations in Kepler/Ptolmey the end result is:
Line 2 was replaced by lines 3-11
- The OPeNDAP data model (aka the DAP2 data model) supports more complex data objects than the Kepler/Ptolmey data model.
+ # Poorly optimized in memory (unless the data is represented as a Ptolmey __matrix__ type)
+ # Not really available to the existing Kepler/Ptolmey actorsuite due to it's inherent complexity.
+
+
+ Ideas:
+
+
+
+

Back to O Pe NDAP/Kepler Data Model Resolution, or to the Page History.


This material is based upon work supported by the National Science Foundation under award 0619060. Any opinions, findings and conclusions or recomendations expressed in this material are those of the author(s) and do not necessarily reflect the views of the National Science Foundation (NSF).

Copyright 2007