1 / 47

GeoWeb Vision - Technical Requirements -

GeoWeb Vision - Technical Requirements -. Overview. What/Why of the GeoWeb? Relation to SDI? Technology Requirements Galdos Approach Summary. Why the GeoWeb?. How can we make decisions?. If we don’t know what is happening?. Why the GeoWeb?. Why the GeoWeb?. Why the GeoWeb?.

gautam
Download Presentation

GeoWeb Vision - Technical Requirements -

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. GeoWeb Vision - Technical Requirements -

  2. Overview • What/Why of the GeoWeb? • Relation to SDI? • Technology Requirements • Galdos Approach • Summary Powering the Geo-Web

  3. Why the GeoWeb? How can we make decisions? If we don’t know what is happening? Powering the Geo-Web

  4. Why the GeoWeb? Powering the Geo-Web

  5. Why the GeoWeb? Powering the Geo-Web

  6. Why the GeoWeb? Powering the Geo-Web

  7. Why the GeoWeb? Powering the Geo-Web

  8. Why the GeoWeb? Powering the Geo-Web

  9. Why the GeoWeb? Powering the Geo-Web

  10. Why the GeoWeb? Powering the Geo-Web

  11. Common Foundations or Separate Silos? Urban Planning & Design Infrastructure Construction Urban Infrastructure Management Environmental Security National & Regional Security Energy Management Spatial Data Infrastructure (GeoWeb) GeoWeb is the aggregation of SDI’s local to global! Powering the Geo-Web

  12. GeoWeb as Planetary Digital Nervous System Aggregation of local SDI’s Common framework for multiple problems! Not GIS – focus is information management! Powering the Geo-Web

  13. GeoWeb Vision Technical Requirements

  14. Rich Variety of Data Types – Open Standards Powering the Geo-Web

  15. Rich Variety of Data Types – Open Standards • Common encodings would be useful • GML 3.1.1 or 3.2 can capture: • Coverages (including imagery) • Vector Features • CAD - (e.g. cityGML) • Sensor data (Observations) • Augment by specialized GML “vocabularies” • Observations & Measurement • GeoSciML • cityGML Powering the Geo-Web

  16. Rich Variety of Data Types – Open Standards • Related XML vocabularies • IFCXML (Building Models) • SensorML • TransML (transducer ML) • Industry Standards • Raster Process Definition File (RPDef) • ArcXML/Shape • Others! • Key thing is move rich variety of information about easily – be pragmatic!! Powering the Geo-Web

  17. Feature or Object Orientation Focus on !!! The Thing Powering the Geo-Web

  18. Feature or Object Orientation Powering the Geo-Web

  19. Feature or Object Orientation • Objects characterized by properties. • Objects characterized by behaviour. • Objects characterized by classification. • Common approach over ALL data types. Powering the Geo-Web

  20. Connections must be Unobtrusive Powering the Geo-Web

  21. Connections must be Unobtrusive • No change to existing applications. • No change to existing databases. • Easy configuration. • Automatic data change propagation. Powering the Geo-Web

  22. Support for Automated Change Detection • land parcel changes • road changes • sensor data – level exceedances • new imagery • imagery change detection • emergency event declaration Stay in synch! Powering the Geo-Web

  23. Support for Automated Change Detection • General change detection mechanism • Database changes (e.g. Oracle, MS SQL etc). • File changes • Any vendor to any vendor – event propagation! • User notification! Powering the Geo-Web

  24. Open Standards for Security Security in a distributed environment is complex! • need secure single sign on (SSO) • often hard to know what access control policies are in place. • hard to administer many distributed nodes! • web services (SOA) pose new challenges! Need standard mechanisms for SSO, Identification & Authorization (Access Control) ! Powering the Geo-Web

  25. Open Standards for Security SAML and XACML Authorization Request Web Service Policy Decision Point Authorization Decision Policy Store Other Web Service Powering the Geo-Web

  26. Federated Security Domains • Participant has own security domain. • Create trust relationships between domains. • Support access control across domains. Trust Relationships! Powering the Geo-Web

  27. New Architectures – P2P and Event Driven • OGC/ISO specifications have assumed client-server (REST or SOA) .. • Change driven processes must be event driven! • Scalability demands consideration of peer to peer architectures. Powering the Geo-Web

  28. New Architectures – P2P and Event Driven (Server) request Client (typically visualization) response Data Source Web Service Over emphasis on C-S models leads to client side integration Powering the Geo-Web

  29. New Architectures – P2P and Event Driven (Server) request Client (typically visualization) response Client (typically visualization) Not scalable and very disruptive as a general model! Data Source Web Service Powering the Geo-Web

  30. New Architectures – P2P and Event Driven Highly scalable systems! No single point of failure Peers (Server) (Server) Client Client Data Consumer Web Service Data Provider Web Service Reduced network traffic Client can be Web client or not – interacts with own persistent store Powering the Geo-Web

  31. Communities, Schema Management and Schema Translation Shared Vocabulary Shared Understanding • Ontology • Typology • Schemas • CRS def’n • Units def’n Shared Resources Membership • list of members • join procedure • responsibilities • benefits • Features • Coverages • Metadata • Services What is a community? Information Sharing Community Powering the Geo-Web

  32. Communities, Schema Management and Schema Translation Organization A Organization B Road numLanes surface class Street number of Lanes surfaceType type Powering the Geo-Web

  33. Communities, Schema Management and Schema Translation Tools that allow users to map “local” to “community schema(s)” Management of schemas! Type mapping Property mapping Ontology-based mapping Powering the Geo-Web

  34. Communities, Schema Management and Schema Translation Transformation Schema Mapping defines rules that transform from one schema to another. Acts on requests and on the data! Powering the Geo-Web

  35. Spatial Data Infrastructure Galdos Approach

  36. Galdos SDI Architecture – Conceptual View • Peer-to-Peer Architecture with Control Center. • Control Center to monitor & manage connections. • Data flow can be push or pull • Data flow is connector to connector. • Connectors for common/GIS spatial or other DBMS • Oracle Spatial • ArcSDE/ArcGIS Server • MS SQL Server • No restrictions or changes for/on client applications. Powering the Geo-Web

  37. Galdos SDI Architecture – Conceptual View Developers Municipal Staff Architects Engineers Urban Support System Control Center Project Collaboration Infrastructure Visual Portal Project Managers Common Geospatial Database Maritime Survey Land Survey Police = connector Maintenance Fire/Ambulance & Emergency Services

  38. Technology Components – SDI Framework GeoWeb Controller Notification/Monitoring participant spatial database Data flow is peer-to-peer e.g. ArcGIS Server e.g. Oracle Spatial = connector Powering the Geo-Web

  39. Technology Components – SDI Framework • Framework for managing & automating data distribution • Framework for managing & automating data aggregation • Publication & Subscription • Context • Notification Powering the Geo-Web

  40. Technology Components – SDI Framework • Builds on standard spatial & non-spatial databases (e.g. ESRI, Oracle, MS). • Audit Trail & Monitoring • Unobtrusive • Secure Powering the Geo-Web

  41. Technology Components – Web Registry Service Critical component for data sharing • Manages context for sharing. Data Communities. • Manages Publications/Subscriptions. • Manages identifiers (object names, ID’s) • Based on open standards (ebRIM, GML, XML) • Notification • Spatial Data Support A general artifact and digital content manager Powering the Geo-Web

  42. Galdos Technology Components & Solutions • Solutions: eGovernment, Aviation, Emergency Response, Defense & Security. • INdicio Web Registry Service • GeoWeb SDI Framework • Automated quality assurance. • Google Earth & ArcGIS Server Powering the Geo-Web

  43. Summary GeoWeb is the aggregation of SDI’s New SDI Concept! Powering the Geo-Web

  44. Summary • Requirements: • Rich variety of data types • Feature/Object Orientation • Communities/Schema Mapping/Management • Unobtrusive Connectivity • Automated change detection • Open standards for security – security framework. • New Architecture – P2P and Event Driven Powering the Geo-Web

  45. Summary • Galdos Systems: • Maturing GeoWeb SDI Framework • P2P/Event Driven Architecture • Exploits OGC/ISO/OASIS standards under the cover! • P2P or Managed P2P deployments • Integral INdicio Web Registry Service • Seeking development partners and System Integrators !! Ron Lake (rlake@galdosinc.com) Powering the Geo-Web

  46. GeoWeb 2009 Conference Vancouver, Canada July 27-31, 2009 Urban Environments 3D Modeling Student Contest Powering the Geo-Web

  47. Discussion Powering the Geo-Web

More Related