1 / 34

Interoperability to Interconnection April 2008 by Ron Lake, Chairman & CEO

Interoperability to Interconnection April 2008 by Ron Lake, Chairman & CEO. SDI lessons from “the wild west”. Overview. Galdos Information Infrastructure (SDI) Drivers! Information Infrastructures (SDI) Shortcomings A better approach Summary.

silvio
Download Presentation

Interoperability to Interconnection April 2008 by Ron Lake, Chairman & CEO

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. Interoperability to InterconnectionApril 2008by Ron Lake, Chairman & CEO SDI lessons from “the wild west”

  2. Overview • Galdos • Information Infrastructure (SDI) Drivers! • Information Infrastructures (SDI) Shortcomings • A better approach • Summary Powering the Geo-Web

  3. Real Time Geographic Data Sharing and Aggregation Who is Galdos? Powering the Geo-Web

  4. Galdos and Open Standards • Creator of GML (Geography Markup Language) • OGC Leader – WFS/WRS/WMS/FPS/KML • GMLJP2 Image Standard • Member of OASIS TC’s • Active in ISO TC/211 – 19115, 19136, 19139, 19142/19143 .. Etc. Powering the Geo-Web

  5. Who relies on Galdos? Powering the Geo-Web

  6. Why SDI? How to put it back together?

  7. Information Infrastructure – Natural Disasters • You are responsible for dealing with the hurricanes impact! Many kinds of information are needed! • population centers • hazardous materials • flood protection systems • evacuation routes • ECOM centers • storm track • rainfall distribution • impact area • needs assessment! Need fast access to data across multiple jurisdictions

  8. Information Infrastructure - Natural Disasters You must provide the data to multiple – geographically distributed persons, companies, agencies – and systems !! Ongoing problem (years)! Participants are not only distributed but autonomous!

  9. Information Infrastructure – Property Management Cities/Counties share common borders Features cross from one city/county to another ! None of this data is STATIC ! Cities/towns are merged and divided Unified Cadastre Cities/Municipalities in a State or Province

  10. Information Infrastructure - Security Immediate demand for data integration Many agencies impacted – many to be informed and mobilized Sharing of information in real time ! Stakeholders are autonomous and geographically distributed Critical need for data security and authentication ! National Security

  11. Information Infrastructure - Environment State – Federal – Local Governments – Private Corporations Distributed & Autonomous Stakeholders! Dynamic changing situation Complex Situation – Hard to know what is happening !

  12. Information Infrastructure - Physical Infrastructure Multiple government agencies & corporations Complex structure & geometry Highly distributed stakeholders Multi-directional data exchange Evolution and development over a protracted time period !!

  13. Shortcomings from the “wild west” • Over emphasis on visualization • Ignores CAD/Physical Infrastructure Design. • “Library” oriented – clearinghouses. • Non real time. • Too much focus on discovery • User generated data not included. Powering the Geo-Web

  14. New Approaches & Concepts for SDI! • Interconnection not just interoperability • CAD & GIS & BIM integration – one world • Custodians and Observers. • Automated data conversion. • Publication/Subscription • Staging and Automated QA Powering the Geo-Web

  15. Custodians and Observers • In a typical community some organizations are responsible for certain data types. • e.g. “Water company knows where the water pipes are” • May be controlled by legal issues (e.g. land parcels) • Is a direct part of a business process (e.g. land registration). • BUT – anyone can be an observer. • “my neighbour is encroaching on my property” • “the street light does not work outside my house” • “the gas main does not cross the property boundary” Powering the Geo-Web

  16. Custodians and Observers • If the Custodian makes a change and I want that change I should accept it. • If an Observer provides an observation I need to look at that in relation to other data. • I should record any Observations of interest. • If I am a Custodian – I may issue a change based on Observations I receive. Powering the Geo-Web

  17. Street Centerline Observation City Hall Application Custodians and Observers Custodian Observer Custodian Agency e.g. City Hall Observer Agency e.g. Water Company status Water Application ملاحظ مالكة Assume many Observers for each feature type Powering the Geo-Web

  18. Street Centerline feature update Street Centerline Observation Street Centerline feature update Application Application Custodians and Observers Observer Custodian Subscriber Agency e.g. Teleco Custodian Agency e.g. City Hall Observer Agency e.g. Water Company Application Observations enable submission of changes by all parties - only custodian can make it official Powering the Geo-Web

  19. Observation and Features ملاحظ • Features are “authorized” models of real world things. • Authorization may be formal and controlled or not. • Features evolve but are essentially persistent. • Observations are “acts” of measuring or observing. • Observations are partial and local in time: • “June 1, 2007 Bob noted that the building had 24 stories” • A set of Observations leads to the creation or update of a Feature. • Observations are “about” Features. Observation Feature شيء Powering the Geo-Web

  20. Handling different world views • Different organizations have different models of the world. • Implies different schemas. • Requires schema driven data translation. Bus Company Name ID Description Address Street Number Street Name City TransitAgency AgencyName AgencyID Description Street Number Street Name City Schema driven data translation Powering the Geo-Web

  21. DataBase #2 DataBase #1 Different Coordinate Reference Systems • In an open GeoWeb there will be many coordinate systems (CRS). • Aggregators or communities may standardize on a particular CRS or set of CRS. • Automated CRS translation by the infrastructure. CRS#2 CRS#1 Coordinate Transformation Powering the Geo-Web

  22. Role of open standards تحت الغطاء • GML supports the Feature and Observation concepts. • Can support any data model (Database). • Transport observations (Insert) and Feature changes (Updates). • Companion WFS provides transaction mechanism. • Open standards needed to keep the “community” open – e.g. add new publishers and subscribers. Open Standards WFS GML KML WRS WMS Powering the Geo-Web

  23. e.g. “Class 2 roads” Advertisement Subscription e.g. “Class 2 roads intersecting test line” Publication/Subscription اشتراك نشر System – Manages Subscriptions and Advertisements Advertisement Subscription “Board” Subscriber selects advertisement to create a subscription إعلان Advertisement مشترك ناشر Subscriber Publisher Powering the Geo-Web

  24. Different vendors – different data models Open standard transaction DataBase #2 DataBase #1 Change Detection Transaction Generator Geographic Application status Change Change Geographic Application Different applications – different views Change Detection and Propagation • Be minimally disruptive (tools, applications, DBMS) Connector ما من حاجة أن يغيّر Powering the Geo-Web

  25. System Concept – High Level Custodian is the master source for a feature type. Client Application Custodian Agency Subscriber Agency Subscriber Agency Subscriber Agency Updates are propagated to all subscribers Powering the Geo-Web

  26. Data Staging • Some times data quality assurance is complex. • May require manual intervention. • May need to deal with multiple observations/features • May be controlled by a formal work flow. Data Staging Area Observation Inserts, Feature Inserts/Updates Geographic Database Automated & Manual QA Powering the Geo-Web

  27. Automated Quality Assurance • Complex problem: • Absolute Accuracy/Precision of objects. • Relative positions of objects. • Semantics. • Best approach – rule-based mechanisms. • SWIRL (Radius – 1Spatial) • DROOLS + JTS • CITE + JTS • Data Quality Group in OGC Powering the Geo-Web

  28. Building the Data Provenance تاريخ • Audit trail of transactions – “who did what to whom and when” • Observation history. • What observations were used to create a feature instance and why? • Must be in-obtrusive. • Must embed in the normal business process. • Must be able to search provenance by feature type, instance, time window etc. Powering the Geo-Web

  29. “New” SDI in practice City Hall publishes road centerlines & parcel boundaries. Developer City Hall Developer subscribes to road centerlines, water 1-line • Riydah • ICC Galdos SDI Framework Post Office Water Company Telecom Provider Powering the Geo-Web

  30. Connectors & Connection Management Geomedia Application ESRI Authoring Tool Connection Manager (HUB) Oracle Spatial ArcGIS Server Monitoring & Reporting connector connector Data Flow GeoWeb Server(s) = {Connector, Connection Manager} Powering the Geo-Web

  31. Sharing information in practice • Each participant keeps existing database & client applications. • Easy install connector to publish/subscribe to data. • Hub manages the data connections, advertisements and subscriptions. • Hub monitors data traffic on report basis. • Hub provides directory of data providers. • Data flow is connector to connector. • Participants control who sees what. • Participant controls ingest of data from staging area. Powering the Geo-Web

  32. Summary • Real and useful SDI demands a new approach! • CAD/BIM/GIS Integration • User Generated Data (custodian/observer) • Live data integration – real time/transactions. • Think interconnection not just interoperability! • Open standards “under the hood”. Powering the Geo-Web

  33. Questions and Answers Thank You Powering the Geo-Web

  34. platinum sponsors gold sponsor silver sponsor Conference Organizer Conference Supporter • Join us at GeoWeb 2008 • We’ll discuss and further explore the many facets of the “GeoWeb”, such as: • Global data aggregators and data communities • GeoWeb in Security and Defense • Real time emergency response and environmental security • Neo-geo, user generated data and the GI professional • CAD-BIM-GIS-Games Integration – 3D Cityscapes (Worlds Real and Virtual) • Infrastructures for information – building alongside physical infrastructure • Municipal SDI in the GeoWeb • Imaging, Coverages and Image Information Infrastructures • www.geowebconference.org • July 21st-July 25th, 2008

More Related