The ESA Earth Observation Payload Data Ground Segment ...
The ESA Earth Observation Payload Data Ground Segment ... The ESA Earth Observation Payload Data Ground Segment ...
G-POD ObjectivesProvide a “user-segment” environmentPut data & user’s processors togetherAllow “on-demand” processing of the dataAssume common functionsOpen: able to host “any” processorSizeable and SecureOffer scientists a “production” labFocus on algorithmsReuse housekeeping functions (data access, catalogue access,common software tools, etc)Bridge gap from “prototype” to “production” processorOffer scientists a “collaboration” environmentShare tools and functionsReuse output of other processorsIPR is kept, core processor is developed/maintained by the scientist
Temporal/spatial selection of EOproductsG-POD Web Portal Job definition, submission and livestatus monitoring Customisable result visualizationinterfaces Access to output products anddocumentation
- Page 1 and 2: The ESA Earth ObservationPayload Da
- Page 3 and 4: Rationale for PDGS harmonization (1
- Page 5 and 6: Ground Segment DecompositionSpecifi
- Page 8 and 9: MultiMission Facility Infrastructur
- Page 10 and 11: MMFI Main Functionality‣ Data Ing
- Page 12 and 13: MMFI ArchitectureCentral Infrastruc
- Page 14 and 15: MMFI Elements All MMFI Elements are
- Page 16 and 17: MM PDGS benefits Lower cost & risks
- Page 18 and 19: EO payload data processing needs EO
- Page 20 and 21: Distributed Processing Each MMFI ce
- Page 22 and 23: DPCS The Distributed Processing Cap
- Page 24 and 25: DPCS Solution Search Workload Manag
- Page 26 and 27: DPC Structured Processing BusMMFI A
- Page 28 and 29: DPC Conclusion Grid technology Rati
- Page 32 and 33: G-POD History and Status 2002-2004:
- Page 34 and 35: Improved Data AccessMM PDGS Future
G-POD ObjectivesProvide a “user-segment” environmentPut data & user’s processors togetherAllow “on-demand” processing of the dataAssume common functionsOpen: able to host “any” processorSizeable and SecureOffer scientists a “production” labFocus on algorithmsReuse housekeeping functions (data access, catalogue access,common software tools, etc)Bridge gap from “prototype” to “production” processorOffer scientists a “collaboration” environmentShare tools and functionsReuse output of other processorsIPR is kept, core processor is developed/maintained by the scientist