Presentation on theme: "GEOSS Architecture Status and Way-forward Unofficial presentation Just for brain Storming GEO Secretariat CEOS/WGISS, May 24 2007, Hanoi."— Presentation transcript:
GEOSS Architecture Status and Way-forward Unofficial presentation Just for brain Storming GEO Secretariat CEOS/WGISS, May 24 2007, Hanoi
GEO Status Membership –69 Member Countries and European Commission –46 Participating Organizations Concentrate the activities to Ministerial Summit in Nov. 30 in Cape Town, South Africa –Preparatory Task Forces have formed for Declaration, Report on Progress, Communication and Logistics –Demonstration (e.g., Video), Exhibitions Near term schedule for Summit –Report on Progress Task Force meeting: June 4-5 –GEO Committee Co-Chairs meeting: June 6 –Communication Task Force meeting: June13 –GEO Executive committee: July 3-4 –One more iteration would be happened in September (Task Force, Executive committee) –GEO Executive committee: Nov 27 –GEO Plenary: Nov 28-29 –Ministerial Summit: Nov 30
ADC meeting ADC-V Sept. 12-13, Washington DC area, US, chaired by I. Deloatch/USGS –with one or half day workshop of GEOSS data policy workshop organized by ICSU/CODATA ADC-VI early Feb. 2008, Europe, Ispra, chaired by A. Annoni/EC ADC-VII May-early June 2008, Asia, chaired by R. Shibasaki/Japan ADC-VIII September 2008, America, chaired by J. Pearlman/IEEE
Model/Integration GEO Web Portal GEOSS Clearinghouse GEONETCast Uplink Center Data Center Information system... Satellite Obs Systems In-Situ Obs Systems Airborne Obs Systems CEOSCGMSGOS Others ArgoHARONFluxTower FDSN Others Various Data Center Information system Data Center Information system Users of 9SBAs Data Archives GEO Information System Data Management Data Access and Dissemination GEOSS Technical Architecture (Not Official) Model/Integration Commercial
Two Core Architecture Tasks AR-07-01 (Enabling Deployment of a GEOSS Architecture) AR-07-02 (GEOSS Architecture Implementation Pilot) System of Systems Activities Strategic and Tactical Guidance Documents Process for Interoperability Arrangement Component Registration Process Interoperability Process Pilot Projects (IPPP) Component Linking Guideline GEOSS Requirements - 10YIP - CoP GEO M&POs Guidelines and Processes Input Refer/Register AR-07-01 activities Utilize as test cases AR-07-02 GEO Web Portal, GEOSS Clearinghouse and Services Participate Access IPPP data ?? Participate Japan IEEEADC IEEE OGC ADC Spatial Data Infrastructure GSDI Standard Interoperability Forum IEEE Apply Component registration
Registries title description standardType contact status title description standardType contact status Special Arrangements title description standardsOrg standardType URN status title description standardsOrg standardType URN status Standards componentAbbrev componentContact componentCategory description onLineReference SBA status componentAbbrev componentContact componentCategory description onLineReference SBA status Component serviceAbbrev serviceInfo (URL) latLongBox timePeriod agreement implementationRef serviceAbbrev serviceInfo (URL) latLongBox timePeriod agreement implementationRef ServiceInstance Identifier title contact onlineRef Identifier title contact onlineRef GEOmembersPO implementation Reference Member offers May have service (Partial Attribute Listing) Interoperability Arrangement Interoperability Arrangement 0..* Hosted by IEEE Hosted by GEOSec Hosted by GMU (Temporary: 6-12months)
IPPP components and scenarios WIS GBIF FDSN CEOP Species Response to Climate Change Scenario Nativi Fault Lubrication Scenario Ahern Landslide Risk Scenario Thomas Flood Risk Scenario Burford Seismic Events from Glacier/Ice Sheet Disintegration Scenario Ahern Exotic event catalog Terminus retreat GLIMS Event catalog Precip (NCAR/TIGGE), stream gauge (CUAHSI /USGS) Seismic Trigger Precip, soil moisture (TIGGE) Climate data (NCAR) Species data DEM (DEMIS) Ancillary Meningitis Early Warning System Kelly Precip, soil moisture (TIGGE) Soil moisture, stream gage, etc.
Architecture Implementation Pilot (CFP) Pilot for GEO Web Portal, GEOSS Clearinghouse and Services
The proposed idea of GEO Web Portal by Secretariat Disaster Health Energy Climate Water Weather Ecosystem Agriculture Biodiversity Direct Access To Data & Services Capacity Building GEONETCast About GEO Search by location Search by theme A Portal to DATA and SERVICES
Current Status of GEOSS Architecture GEOSS Processes have been established –component registration process, process for reaching GEOSS interoperability, component linking guideline –Strategic and Tactical guidance documents would be essential but still in drafting Requirement driven ? –Engineering view point Focus on the process –Where is the requirement? 10 Year Implementation Plan + Reference Document UIC Community of Practice, = subset of 10YIP, Reference Document? –Tactical guidance + Roadmap should be established based on the requirement –Test cases and scenarios would be useful
GEOSS IP Targets - Water 2006-20072008-20112012-2015 In-situ observation Integration Product Model User IF Improve existing in-situ sys Test global net of integrated in-situ sites Test a fully integrated prototype data system with assimilation, analysis & visualisation Make integrated in-situ obs site operational Operational integrated data system Space-based observation Study capabilities for: - surface water quality - streamflow and water storage (altimeters) Integrated info on climate indices/ extreme events Implementation plan for data integration system Plan integrated in-situ network 3 hourly global precipitation Integrated precip. and soil moisture products (IGOS-P) Intl coord. mechanisms GPM & Missions for surface & subsurface water stores Plan water quality monitoring System for monitoring WC changes Data and info on water quantity and quality to protoype expert decision support sys Collaborative mechanism between obs and research community Framework for ensemble hydro prediction Gravity mission for ground water stores New products for precipitation, soil moisture, evaporation and evapotranspiration Integrated water cycle data sets Water level data collection sys PlanningPrototypingOperational Routine watershed health indicators How to look the real world? - Monitor by using the GEOSS Roadmap -
Global/Regional/National, Programs dimension Global: example components are WIS, FDSN, GBIF, Argo Regional: example components are HMA, Sentinel Asia National: many… Enhanced Observing Programs: CEOP, IPY, … We may need to classify these components one by one?
How to look the real world? How each organization to cover the GEOSS Architecture. For example, CEOS world as one of Participating Organizations Satellite Observing Systems Data Archive Data Center/Information System Web Portal/Clearinghouse NASAESAJAXAUSGSCNESNOAAetc CEOS/WGISS CEOS/WGCV CEOS/SIT Capacity Building By CEOS/WGEdu GEONETCast/Uplink Center EUMETSATESA
In-situ Network How to look the real world? How each organization to cover the GEOSS Architecture. For example, EEA and UNEP, as a Participating Organization for In-situ network. Satellite Observing Systems Data Archive Data Center/Information System Web Portal/Clearinghouse Capacity Building By EEA, UNEP GEONETCast/Uplink Center EEA, UNEP
In-situ Network How to look the real world? How each organization to cover the GEOSS Architecture. For example, EC, as a Member. Satellite Observing Systems Data Archive Data Center/Information System Web Portal/Clearinghouse Capacity Building By FP GEONETCast/Uplink Center GMES, FP
In-situ Network How to look the real world? How each organization to cover the GEOSS Architecture. For example, China, as a Member. Satellite Observing Systems Data Archive Data Center/Information System Web Portal/Clearinghouse Capacity Building By National Program? GEONETCast/Uplink Center
Way-forward Near term: for the Ministerial Summit in November –GEO Web Portal and GEOSS Clearinghouse –Interoperable Information Systems Registration process should start soon What to show? Registries? + Use Cases? (discussed in ADC) How to show? Through GEO Web Portal? (discussed in Outreach team) Long term: –Establish and refine the Strategic and Tactical Guidance documents –Refine the processes (component registration, etc) –Establish the sustainability of the Registry operation by the GEO Secretariat and monitoring the status –System of Systems approach would be needed –Currently Architecture has only two years targets. It would be necessary the 6 and 10 years targets.
Your consent to our cookies if you continue to use this website.