Documents
Resources
Learning Center
Upload
Plans & pricing Sign in
Sign Out

GAEL Consultant - PowerPoint

VIEWS: 3 PAGES: 33

									      f

                                                                 &
                                                                Progress status

                                                                       Stéphane Mbaye
                                                                Stephane.Mbaye@gael.fr




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Support to XFDU Specifications

    • Final fixes to « XFDU Red Book »
    • Contribution to « XFDU Green Book »
    • Critical analysis of the standard regarding ESA needs
      (ENVISAT L1/L2 and analysis of EGOS system)
    • Improvement of the implementations
    • Produce sample packages (more than 500)




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Historical Archive Rationalization (HARM)

    • Core project being concluded
    • Additionnal packages for supporting ENVISAT Level 1
      and Level 2 products (until end of February):
           • 49 product types
           • about 300 additional XML Schemas
           • 500 examples




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    SAFE - Physical Model Reminder




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Manifest - Internal Constraints




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Manifest - Reference Informations




     « SAFE requires
        Representation
        Information of each
        Data Object »


CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Manifest – Multiple Rep. Info’s




     « Representation
        Information may be
        composed of several
        components »


CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
      Manifest – Binary Metadata




« XFDU Recommends to
    refer to Binary Metadata
    Components through a
    Data Object »
« XFDU requires that all Data
    Objects should be
    referenced from the
    Information Package
    Map »



  CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
  SAFE Status
    Manifest – Reference between Components
        Manifest file

              2

                                                                                     ?




                                                                     1
                                                                Requires to know the Manifest content
                                                                            locate the Manifest
                                                                    - Hight Manifest/Components coupling factor…
                                                                    Structure/Semantic
                                                                    - Could a registry
                                                                    Context/Profile help ?
                                                                    (…)
                                                                    -SAFE tackle this with Xquery


CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
                                    SAFE Specializations




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Specialization - Definition




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Abstract specializations




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Abstract specializations - Example




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Redefinitions and Imports




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
                          ESA/XFDU I/O Java/C++ API




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Overview



                                                                JNI Interface




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Use cases
    •     Create of an XFDU package
    •     Open an XFDU package
    •     Remove an XFDU package
    •     Move an XFDU package considering referenced objects
    •     Validate an XFDU package including the object contents
    •     Verify fixty i.e. Components checksums
    •     Add/Remove/Browse Content Units of the Information Package Map
    •     Add/Remove/Retrieve Metadata Objects
    •     Add/Remove/Retrieve Data Objects
    •     Apply Transformation Objects




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Java Packages
    •     esa.xfdu                      General XFDU packages management.
    •     esa.xfdu.map                  XFDU Information Package Map Section
    •     esa.xfdu.object               Classes handling all XFDU object types.
    •     esa.xfdu.object.metadata      XFDU meatadata object types.
    •     esa.xfdu.object.data          Classes handling XFDU data object types.
    •     esa.xfdu.object.behavior      Classes handling XFDU behavior object types.
    •     esa.xfdu.object.behavior.impl Behavior Implementations




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Main Java Interfaces
    • esa.xfdu.object.Object
           • esa.xfdu.object.metadata.MetadataObject
           • esa.xfdu.object.data.DataObject
           • esa.xfdu.object.behavior.BehaviorObject
    • esa.xfdu.object.behavior.Mechanism
    • esa.xfdu.object.behavior.Transformer




                                                                « The second version of XFDU may
                                                                    gather the means for referencing
                                                                    Metadata/Data/Behavior objects in
                                                                    a common object list. »




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    C++ Wrapper




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Current Version



                                    xfdu-1-0-rc-10
                                                   (April 28, 2006)




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Code Statistics




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Further information

    http://www.gael.fr/xfdu




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Connected Application

    • CNES has developped a GUI on top the XFDU I/O Java
      API: the « XFDU View »
    • C.f. http://www.gael.fr/xfdu-view




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
                          ESA/SAFE I/O Java/C++ API




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Overview




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Use cases
    •     Create of a SAFE product
    •     Open a SAFE product
    •     Remove a SAFE product
    •     Move a SAFE product considering referenced objects
    •     Validate a SAFE product including the object contents
    •     Verify fixty i.e. Components checksums
    •     Add/Remove/Browse Content Units of the Information Package Map
    •     Add/Remove/Retrieve SAFE Specialized Metadata Objects
    •     Add/Remove/Retrieve SAFE Data Objects
    •     Browse XML and Binary Data Object Contents
    •     Accelerate Content access using SAFE Indexes




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Java Classes
    esa.safe.object.metadata.AcquisitionPeriod                  esa.safe.object.metadata.MissingElements
    esa.safe.object.metadata.CloudVoteNotationSystem            esa.safe.object.metadata.OrbitNumber
    esa.safe.object.metadata.Container                          esa.safe.object.metadata.OrbitReference
    esa.safe.object.metadata.CorruptedCause                     esa.safe.object.metadata.Platform
                                                                esa.safe.object.metadata.Point
    esa.safe.object.metadata.CorruptedElements
                                                                esa.safe.object.metadata.Processing
    esa.safe.object.metadata.Facility
                                                                esa.safe.object.metadata.QualityInformation
    esa.safe.object.metadata.Frame
                                                                esa.safe.object.metadata.Resource
    esa.safe.object.metadata.FrameSet                           esa.safe.object.metadata.Software
    esa.safe.object.metadata.FrameTile                          esa.safe.object.metadata.Time
    esa.safe.object.metadata.GridReference
                                                                esa.safe.Safe
    esa.safe.object.metadata.Instrument
                                                                esa.safe.SchemaValidator
    esa.safe.object.metadata.Line
    esa.safe.object.metadata.Location




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    C++ Wrapper




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Current Version



                                    safe-1-0-rc-13
                                                   (June 10, 2006)




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Code Statistics




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Further information

    ESA Official Web:
    http://earth.esa.int/SAFE

    GAEL’s Project Web:
    http://www.gael.fr/safe




CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status
    Conclusions
    • SAFE Specifications verified that XFDU is suitable for
      some amount of EO data sets (59)
    • An alternate XFDU implementation is available
      (C++/Java) and interoperates with NASA API
    • Up to 59 EO sample packages have been generated
    • SAFE Volume 2 is ready to be conveyed to the XFDU
      Green Book
    • An XFDU v2 may improve the v1, at least, by:
           • Simplifying the association mechanism between Objects
           • Generalizing Metadata/Data/Behavior Object references
    • Future of XFDU and SAFE within ESA: c.f. ESA Agency
      Report

CCSDS MOIMS Falls Meeting 2007 – Colorado Springs - June 2006
SAFE Status

								
To top