download as a pdf - Southern California Coastal Ocean Observing ...

Part II. Phased Implementation Plan for DMAC4.8. The DT shall support data manipulation, including (but not limited to) such manipulations as4.8.1. Re-projection—for example, Platte-Care to Mercator4.8.2. Re-gridding—for example, same projection, different resolution4.8.3. Averaging4.8.4. Summing4.8.5. Scaling of values such that they are delivered in a consistent system of units—for example,# specimens/m 3 , m/s, °C4.8.6. Conversion of time to different representations4.8.7. Conversion of latitude and longitude4.8.8. Conversion of depth4.8.9. Conversion of missing values4.9. The DT shall support access-restricted, secure transmission of data.4.10. The DT shall support fault detection and localization within the DMAC.4.11. The DT shall support the gathering of performance and usage metrics within the DMAC.5. Design Constraints5.1. The DT shall be designed to work cooperatively with other systems. For example, if a repositoryalready uses a system that depends upon a particular data storage format, that site shouldnot be forced to abandon its system in order to adopt IOOS.5.2. The DT shall be designed to operate with minimum reliance on proprietary software.5.2.1. The DT specifications shall be fully and openly accessible to the public.5.2.1.1. There is a stated preference for software licensed under the General Purpose License.5.3. The scheme that the DT adopts for generating syntactic and semantic data models shall beflexible and extensible so that any IOOS server can find a way to express its archive’s storageformat in an IOOS data model.5.4. The DT shall support interoperability between Geographic Information Systems and ScientificInformation Systems.5.5. The DT shall support interoperability with other systems developed within other disciplines.66