1 / 15

Architecture Task AR-06-05 “Clearinghouse” Status

Architecture Task AR-06-05 “Clearinghouse” Status. Presented to the July 20-21, 2006 Meeting of the GEO Architecture and Data Committee George Percivall, Chuck Heazel, Sean Forde; OGC gpercivall@opengeospatial.org AR-06-05 Point of Contact. AR-06-05 Task Sheet.

tavita
Download Presentation

Architecture Task AR-06-05 “Clearinghouse” Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecture Task AR-06-05“Clearinghouse” Status Presented to the July 20-21, 2006 Meeting of the GEO Architecture and Data Committee George Percivall, Chuck Heazel, Sean Forde; OGC gpercivall@opengeospatial.org AR-06-05 Point of Contact

  2. AR-06-05 Task Sheet • Task Title: Initiate development of a publicly accessible, network-distributed clearinghouse, subject to GEOSS interoperability specifications to date, and including an inventory of existing data, metadata, and pre defined common products. • Description of the Work to be Performed 1. Develop content and presentation criteria for permission to use “GEO Clearinghouse” brand. 2. Request offers from among GEO Members and Participating organizations to designate network nodes of the GEO Clearinghouse, linked via GEOSS interoperability standards and containing existing data, metadata, and pre-defined common products. 3. Test and demonstrate interoperability via Web portals or other verification tools. 4. Include access to GEO Clearinghouse as a key function of the GEO Home Web portal managed by GEOSEC. Highest Priority per Task Team

  3. Task Team proposes two-phase approach • Request for Information (RFI) for Proof of Concept Phase • Include a candidate architecture for distributed catalog network • Include criteria for permission to use “GEO Clearinghouse” brand. • Request comments on architecture • Call for components for Proof of Concept phase • RFI issued by December 2006 • Request for Proposals (RFP) for Operational Phase • RFP to include target architecture for distributed catalog network • Request offers from among GEO Members and Participating organizations to designate network nodes of the GEO Clearinghouse, • Request offers to perform integration of nodes - significant effort • RFP issued in 2007

  4. AR-06-05 - Concepts • Distributed Architecture - Network of Catalog Services • Support GEO Home Web portal – what does this require of the catalog • Multiple portals access Clearinghouse via interoperability specifications • Multiple catalog nodes containing metadata for registered resources • GSDI clearinghouse as example • Resources to be registered • Highest priority: metadata for: maps, vector and raster types • Will need to describe services that provide access to the data • Coordinate with Registry discussions • Interoperability Arrangements - use existing standards • GSDI clearinghouse example of ISO 23950 (ANSI Z39.50) • OGC Catalog Services Specification • Bindings for Z39.50 and Web Services (CSW) • ISO TC 211 Metadata standards; ISO 19115, ISO 19139 • Compelling need for the metadata discovered in catalog to link to on-line web services, e.g., GEOSS Web Services (Network)

  5. GEOSS Web Services (Network) • OGC comment on Task November 2005, briefed to ADC March 2006: • “Beginning with a metadata clearinghouse, develop a GEOSS Services Network (GSN) as a persistent network of a publicly accessible services for demonstration and research regarding interoperability arrangements in GEOSS.” • Status - “GSN” successfully demonstrated • Demonstrations developed as part of GEOSS User Workshops • Open Standards for Catalog, Web Mapping, Web Service access to data. • Consider network to become a parallel component of the Proof of Concept • Name change from GSN to GWS • Avoid conflict with Global Seismographic Network (GSN) • New name: GEOSS Web Services (GWS) - replaces GEOSS Services Network • Beijing Wind Energy Demo highlights

  6. Demo in Beijing GEOSS Workshop Jinsoo You & Mike Jackson Centre for Geospatial Science University of Nottingham jinsoo.you@nottingham.ac.uk

  7. Demo Theme: “Wind Farm Siting” in Hainan Island Demo in Beijing GEOSS Workshop

  8. ? m Offshore Wind Farm Example Demo Theme: “Wind Farm Siting” • Q: Where are the suitable wind farm sites? • Q: Where are stronger winds? • Q: What is the acceptable hub height?

  9. Prospecting Validation Micrositing Common Wind Farm Siting Criteria • Landscape factors • Proximity to and impact upon residential buildings • Biodiversity impact • Potential highways constraints and access issues • Wind speeds at Hub Heights (about 50m above ground) (suitable wind speeds are between 5 and 30 m/s) • Land ownership and constraints • Topography • Archaeology • Hydrology • Connection to the electricity grid

  10. List of Participating Organizations(alphabetic order) • CGS, University of Nottingham: Technical lead for demonstrator build • CIESIN, Columbia University: WMS, WCS and WFS for various data layers • Civil Engineering, University of Nottingham: Expertise on wind modeling • Geomatic Engineering, University College London: WMS and WCS for various data layers • IEEE and Workshop Organizers: Workshop coordination & high speed internet arrangements • IMAA/CNR (University of Florence): WCS and CPS for above ground wind speed data • Ionic Software: OGC compliant products and technical supports • ITT (formerly RSI): OGC compliant products and technical supports, and WCS and WMS • LAITS, George Mason University: WMS, WCS and WRS for various data layers • NASA: Earth-Sun System Gateway (ESG) catalog service and web mapping client • NOAA/NCDC, Unidata/UCAR, and Washington University: WCS and CPS for Global Wind Data (1 degree global wind magnitude and wind vector data) • NRCan/GeoConnections and Environment Canada: WMS for analyzed mesoscale wind atlas • OGC: Coordination with GEOSS and of demonstrator program • RISO National Laboratory: Processed wind speed data based on Envisat images, and expertise on wind farm siting analyses • Sun Yat-Sen University: Provided 10m/40m above ground wind speed data  And, there are many other participants who commented and supported the demonstrator development through the GEOSS Service Network (GSN) and OGC/GSN Telecons. Many thanks!

  11. OGC Architecture for GEOSS demo WMS = Web Map Service WCS = Web Coverage Service WFS = Web Feature Service CSW = Catalog Service – Web WRS = Web Registry Service CPS = Coverage Portrayal Service VCG = Viewer Client Generator WMS WCS VCG WFS Web Browser using VCG WMS WCS CPS OWS Client not using VCG WFS WRS(CSW) *** High Bandwidth Network (1 Mbit/sec) will be used at the demo.

  12. GEOSS Beijing Workshop: Movie http://geoapp2.nottingham.ac.uk:8080/GEOSS_Beijing_Demo-2006(flash)/GEOSS_Beijing_Demo-2006(flash).html http://geoapp2.nottingham.ac.uk:8080/GEOSS_Beijing_Demo-2006(flash)/GEOSS_Beijing_Demo-2006(flash).zip

  13. Starting point for expert of Demo in Flash

  14. Thank you

  15. Catalog Services Catalog Services Catalog Services Portrayal Services Portrayal Services Portrayal Services Reference Architecture Service Distribution https://portal.opengeospatial.org/files/?artifact_id=6669 Geospatial Portal • Viewer Clients • Discovery Clients • Management Clients • Access Control • Exposed Services Portal Services Data Services Internet Data Services Data Services • Features • Gazetteer • Coverages • Symbology Mgmt • Maps • Styling • Coverages • Map Context • Data Discovery • Service Discovery • Catalog Update • Query Languages

More Related