1 / 19

NSDI and Cyberinfrastructure

NSDI and Cyberinfrastructure. Doug Nebert April 2010. Geospatial Web Services. Over the past ten years the FGDC has been promoting online sharing of government data using Web Services Helped formulate the first OGC “Testbed” in 1999 to evolve a common Web Map Service specification

yves
Télécharger la présentation

NSDI and Cyberinfrastructure

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. NSDI and Cyberinfrastructure Doug Nebert April 2010

  2. Geospatial Web Services • Over the past ten years the FGDC has been promoting online sharing of government data using Web Services • Helped formulate the first OGC “Testbed” in 1999 to evolve a common Web Map Service specification • OGC WMS is now the most commonly adopted geospatial Web Service, allowing neutral requests to multiple map servers

  3. Google Earth World Wind ArcGIS WMS Services for the desktop

  4. NSDI CAP Programs • Supported establishment of geographic Web Services by State and Local government • 2004: WMS • 2005: Web Feature Services for Framework • 2006, 2007: Framework client development • 2008: Best practices in geospatial SOA • 2009: GOS Catalog- Use of GOS Map and Data Services

  5. Geospatial Line of Business • Geospatial data lifecycle, A-16 “Framework+” data definitions and stewardship, governance • Common Services WG • SmartBuy2 for geospatial • Evaluating acquisition strategies • Technical Architecture WG • Developing geospatial “segment” guidance • Hosting a GeoCloud initiative

  6. Geospatial Platform Capabilities Federal Agencies Commercial Sector Common Acquisition Capability Business Driven Applications Governance Common Catalog Data Publication Services Service to Citizens Portfolio Management Common Services Academic, Not-for-profit Institutions, NGO State/Local/Tribal Government

  7. Service Interfaces Shared Services Functions/ Processes Data Geospatial Architecture: Agency View Purchase Collect DSS GIS Access Model Create/ Acquire Use Catalog Service Catalog Client Data Find Data & Services Publish Disseminate Map Service Data Access Store/ Manage Process Update Service Archive Manager Internal Access Geocode External Access

  8. Geospatial Segment Architecture Guidance • Use cases • Acquire or Create Geospatial Information • Store and Manage Geospatial Assets • Process Geospatial Information to Maintain or Update Resources • Find Geospatial Information or Services • Publish or Disseminate Geospatial Resources • Use and Integrate Geospatial Information to Support Business Driven Applications Create/ Acquire Use Data Find Data & Services Publish Disseminate Store/ Manage Process

  9. Geospatial Segment Architecture Guidance SRM • FSAM Process • EA Reference Model Contexts: • Business Drivers (BRM) • Service Components (SRM) • Technical Standards (TRM) • Data and Metadata (DRM) • Performance (PRM) • Examples, Use Cases • Reference Materials TRM BRM Segment enables DRM Segment Architecture and the Technical Architecture Service Interfaces Catalog Map Service Data Access Geocoder Geospatial Technical Architecture (Used to create Solution Architectures) Services Functions/ Processes Data

  10. Service patterns that support shared business processes Service patterns (specifications) are recipes that combine specific data, functions, and services for a defined purpose or shared context Shared Geospatial Service Patterns Service Interfaces Geospatial Segment Architecture Guidance SRM Catalog Map Service Data Access Geocoder Geospatial Technical Architecture (Used to create Solution Architectures) • FSAM Process • EA Reference Model Contexts: • Business Drivers (BRM) • Service Components (SRM) • Technical Standards (TRM) • Data and Metadata (DRM) • Performance (PRM) • Examples, Use Cases • Reference Materials Services TRM BRM Segment enables Functions/ Processes DRM Data

  11. Multi-Tier Architecture Client Applications Application Tier Platform Tier Service Interfaces SRM Catalog Map Service Data Access Geocoder Geospatial Technical Architecture (Used to create Solution Architectures) Services TRM BRM Software Components Functions/ Processes DRM Data Suitable for deployment in agency or commercial data center and Cloud environments Infrastructure Tier Hardware, Networks, Storage

  12. GeoCloud Initiative • One-year project to test and monitor externally-hosted Cloud data and service solutions for the geospatial domain, sponsored through the Geospatial LoB • Anticipated outcomes: • Identify requirements-driven solution architectures for various sized deployments of geospatial data and services • Document and assess cost models to support scalability, reliability, and redundancy • Expedite FISMA certification and accreditation for agency adoption of packaged solution architectures • Support and collect cost comparison information from agencies for existing and externally-hosted Cloud solutions

  13. Notional Cloud Computing Stack http://en.wikipedia.org/wiki/Cloud_computing • GSA apps.gov will be offering Infrastructure as a Service (IaaS) solutions for acquisition • This is roughly equivalent to “shared-hosting” of raw computers with an operating system in the Cloud domain

  14. Platform as a Service (PaaS) “A cloud platform (PaaS) delivers a computing platform and/or solution stack as a service, generally consuming cloud infrastructure and supporting cloud applications. It facilitates deployment of applications without the cost and complexity of buying and managing the underlying hardware and software layers.” The GeoCloud intends to pilot the deployment of candidate services or solutions architectures (suites of software) on top of the GSA IaaS to provide common geospatial capabilities. GSA will venture into PaaS next. http://en.wikipedia.org/wiki/Cloud_computing

  15. Geospatial solutions – 1. Data case • Large geospatial data repositories, no processing • External catalog pointers required to persistent RESTful URLs • ftp- or OpenDAP-like access • Examples: imagery, tile cache files, static file downloads registered access open access Geospatial Platform Tier Geo-data apps.gov solutions

  16. Geospatial solutions – 2. Service case • Geo-processing services • Typically used to perform computations • May have local data to work with user inputs • Examples: routing service, geocoder Geospatial Platform Tier Compute service ref Geodata apps.gov solutions

  17. Geospatial solutions – 3. Service and data case • Coupled and decoupled data access/processing services • Typically used in workflows • Accesses data from the Cloud and/or Web services • Examples: Web Processing Service, WFS, WMS External data service Geospatial Platform Tier Geo service Cloud Geodata apps.gov solutions

  18. Geospatial solutions – 4. Solution case • Bundled system images: virtual servers with software • Instantiable in Cloud as single or multiple instances • Example: Amazon Machine Images of GI service suites Geospatial Application Tier VS VS Virtual Server Application Server DBMS Apps Webserver Non-Cloud Web Resources Geospatial Platform Tier Operating System Cloud Geodata apps.gov solutions

  19. Services and the Cloud • Direction from CTO and OMB to: • Deploy services (PGFSOA) • Place data online (data.gov) • Evaluate cloud provisioning for federal IT • Federal geospatial resources are key: • Large data volumes • Complex information content with high value • Analytical capabilities, data structures, and Web Services are standardized

More Related