Database Interoperability in Geospatial Systems
Bahrain 11 December 2007 David Miller, COO eSpatial dmiller@espatial.com
Topics
• • • • • • eSpatial Overview Trends in Geospatial Systems Trends in Interoperability Interoperability Options Sample implementations Conclusions& Closing thoughts
2
eSpatial Overview
eSpatial Overview
• We Provide…
•
•
iSMART software for Web delivered Spatial Applications
Services - GIS & Oracle expertise; Solution development
•
Corporate Vision – “The Best web based Spatial products & services for your applications”
•
Operating globally with European Headquarters in Dublin and US Headquarters in Herndon, VA.
iSMART for Enterprise Solutions
•
“1st choice for Oracle Spatial”
• Extends Oracle Technology Platform
• Built on Standard IT Platforms
• Reduces Cost
• Increases Effectiveness
• Easy to Deploy – Easy to Maintain
Trends in Geospatial systems
We have seen the general trends ….
• Organisations are making the connection between use of spatial data as a means to increase service levels & reduce costs • The User driven Google / Yahoo / Microsoft Factor • Use of web as standard delivery mechanism • Use of web services and SOA for integration • Increased demand to integrate business and spatial data • Increase in quantity of Geospatial data These all drive interoperability
Trends in Interoperability
Interoperability - Definition
IEEE • The ability of two or more systems or components to exchange information and to use the information that has been exchanged. Wikipedia • Interoperability is a property referring to the ability of diverse systems and organizations to work together (inter-operate). The term is often used in a technical systems engineering sense, or alternatively in a broad sense, taking into account social, political, and organizational factors that impact system to system performance.
Interoperability Implies 1. People can access it
•
From anywhere Without a PhD in GIS
Controlled view, edit, approve API / Query / Service Efficiently use and reuse components Exchange data in controlled way
2. People can use it
•
3. People can maintain it
•
4. Applications Can use it
•
5. (Normal) Developers can develop to it
•
6. Other databases can use it
•
Three Basic Interoperability Options
1. Data level 2. Application level 3. User Level
Interoperability Options - Option 1: Data Level
• Export / import
•
Flat file exchange / ETL tools
Regular exchange of data across enterprise
• Intermittent copy
•
• Remote access
•
ODBC / JDBC/ Data Bus Migrate to single source of truth
• Store centrally
•
Interoperability Options - Option 2: Application Level
• Application level
•
• •
• •
Web services / SOA Open Standards Message Oriented Middleware Direct application interfaces Application platforms (e.g. facebook)
Interoperability Options - Option 3: User Level
• Integrate processes
•
Remove stove pipes Enterprise portals Integrate at browser level Allow users to drive interoperability
• Common user interface
•
• Web interfaces
•
• Mash-ups
•
Achieving Interoperability - Wikipedia
• Through product engineering • Industry/community partnership • Access to technology and IP • Implementation of standards
Interoperability in the Geospatial world
• No real history of interoperability • One of the last great bastions of proprietary data formats • Traditionally not aimed at Enterprise grade deployments • Specialist skills required • Multiple deployments of different systems • But changing rapidly
•
• •
Consumer pull Efficiency Push Homogeneity / Heterogeneity drivers from other systems
Looking at the options
Network File Storage
Approach • Use one (or a few) common tools • Save files on common network store • Agree on who can change what, where and when Advantages • Simple & Cheap • Easy to provide Disadvantages • Relies on manual enforcement for effective use • Data sharing is more difficult especially across organisations • Data sharing with other systems is more difficult • Really easy to “break the rules” • Few of the advantages of a database approach
Central Database With Spatial Middleware
Approach • One (or a few) common tools • Database for storage (usually GIS data is in “blob” format) • Use middleware / gateway to access & change data
Advantages • All the advantages of a database approach • Spatial efficiency
Disadvantages • Expensive as it can require an additional server for the middleware • All GIS functionality has to go through the middleware • Spatial data is stored as binary objects so data sharing is difficult and access is restricted to a single GIS
Spatial Database Options
Approach • Spatially enabled database (Oracle, Open Source, Microsoft (2008)) • Spatial data uses Open Standard format (e.g., OGC) • Access using SQL and other “standard” tools that know format
Advantages • All the advantages of a database approach • Spatial component is inside the database and not middleware • Few data modelling restrictions • Open-standards approach makes data sharing easier • Seamless integration with other enterprise products
Disadvantages • Can be expensive (if a license doesn’t already exist) • Can require additional skills
Interoperability for the user
• Not just about integrating databases and interfaces • User interface access is key • Traditional access via dedicated CAD/GIS client
• • •
functionality rich but often requires customisation as a result Licenses are expensive Performance can be poor when accessing network or database data
• •
You have to install it Not easy to serve data to large audience / public
Need to make it easy to disseminate in other ways Browser access Web services access Open Standards Access
• Spatial data now being treated like any other data
• • •
• •
Web 2.0 etc.
So what is emerging ….
• Shift to Enterprise grade systems
•
Multi user, Scalable, Secure, etc.
• Spatial no longer “special”
•
But knowledge is required Ease of install, use & maintenance & cost Still needed for specialist activities
At the database At the application At the user interface
• Eliminate the fat client for general use
•
•
• Integrate in a number of areas
1.
2.
3.
• The best choice depends on the application
Example Interoperability - End Users
United States Geological Survey National Land Cover Analysis Application
United States Geological Survey: National Land Cover Application
– Land Cover Data Analysis over the web
– Single seamless database of multiple datasets – Enabling “Analysis for the masses” – More accessible, no need for client software – Database Interoperability with mass user audience
– Web Services interoperability for other agencies
Example Interoperability - Data Maintenance
Department Of Sustainability & Environment Queensland Australia
Victoria Department of Sustainability and Environment - Distributed Transactional Online Editing
Interoperability for data maintenance
Connects data originators to data custodians for realtime integration of mapping changes across the web
Highly Controlled spatial editing for authorised users Version management using Oracle Workspace Manager
Eliminates “paper shuffling” within update process
A more detailed example - Local Authority “SDI”
Hull City Council UK
Hull City Council Driven by “T-Government” Requirements
• Saving money – reduced duplication, easier access • Improving customer service • Evidence-based resource targeting • Modernisation • Seamless data sharing • Data quality • Not just geospatial drivers…
Hull City Council - Specific Spatial Drivers
• Remove data duplication
•
At least 50 datasets, separately maintained ~ 60 pro GIS licences = £1.5k each + maint + training < 6 GIS/spatial data technicians in 14,000 staff
• Reduce licence costs
•
• Make access easy
•
• Improve visibility, decision making, accountability
•
Areas with devolved budgets but not line mngt Deliver Priority Service Transformation Outcomes
• Specifics
•
•
G14 (streetworks), G5 (mapping)
HullCC Interoperability Challenge - Diverse data sources and destinations
Data Sources
GMS HULL GMS OOT
Spatial Data Store (SDS)
Data Storage & Distribution Management
LLPG, NSG, BIN DAY, CTAX BAND, CATCHMENT AREA
Data Destination
LLPG ,NSG HULL AND EXTERNAL
GRAFFITI INCIDENTS, MISSED BINS, FLYTIPPING INCIDENTS POLITICAL AREAS SCHOOLS, ENVIRONMENTAL OPERATIONALMAPS EXOR, FLARE, SLITS, HITS, I-WORLD, IBS, COMMIT, EMS POLICE, DTZ
CRM APPOINTMENTS
CRM
ADDRESS & SERVICE SEARCH, REPORTS (EG GRAFITTI VS TRUANCY)
ADDRESS & SERVICE LOCATOR, REPORT VISUALISER (EG GRAFFITI VS TRUANCY) WARDS, AREAS, POLICE HOTSPOTS, MISSED BINS
BROWSER TEXT RESULTS
IN HOUSE MAPPING DATA
BROWSER MAPPING
IN HOUSE SYSTEMS
IN HOUSE GIS USERS
PARTNERS DATA
GRAFFITI INCIDENTS, WARDENS
LLPG, NSG, WARDS, AREAS
IN HOUSE SYSTEMS
PARTNERS
Hull City Council: “Local SDI” & Intranet/Internet “MyMaps” app.
Public Street Works Reporting system (UK Local Government G14 Compliance)
Separate Applications - Public Internet application - Internal management application - Common Spatial Data Store
Increased customer service Built on & Integrated with Hull Spatial Data Infrastructure
http://www.hullcc.gov.uk
Hull City Council – Current Status
Data Sources
Spatial Data Store (SDS)
Data Storage & Distribution Management Data Destination
ORACLE
LLPG
CAPS GMS
CRM / ACCESS SYSTEMS
CRM
ORACLE
iSMART
BROWSER TEXT RESULTS
IN HOUSE MAPPING DATA
ARCVIEW
iSMART
BROWSER MAPPING
ARCSDE?
IN HOUSE SYSTEMS
CID
ORACLE / OTHERS
IN HOUSE GIS USERS
IN HOUSE SYSTEMS
PARTNER DATA
ARCVIEW, MAPINFO
ORACLE / OTHERS
PARTNERS
Added Benefit of Interoperability Hull CC Flood Response
Large areas impacted by Flood damage in June 2007
Added Benefit of Interoperability Hull CC Flood Response
“On Demand (Simple) database Interoperability”
Oracle CRM data captures public calls Transferred to SDS via scripts - near real time view Hidden benefit of database approach
Pre and post emergency information Access across council via browser
Conclusions
Interoperability Conclusions • Increasing in importance
•
Not just between Geospatial systems
• Process Interoperability essential for efficiencies • It’s not just about storing in one place
•
“Virtual central storage” is possible
• Key is to deliver conceptual central storage
•
Users & applications see a common Spatial Data Infrastructure (SDI)
Interoperability futures
• Continued growth due to process efficiencies
•
Eliminate clients – increase use of browser
• Geospatial systems & the mainstream will merge
•
Extending the reach of Geospatial data is key
• Cultural issues will remain a key challenge • IT based Open standards will grow
• •
SOA as interchange mechanism Multiple database offerings (Oracle, Microsoft, Open Source)
• Regulatory pressures will increase
•
E.g. EU INSPIRE
• Success will be achieved with simple approaches
In Summary
• Organisations focussed on
•
Increased service levels, Cost reduction, increased ROI
• Increasing drive towards user empowerment
•
•
Must disseminate to users to empower them Direct customer feedback (controlled mash-up), T-Government
Platform which is robust, Open, Enterprise grade
• This implies specific requirements
•
• GIS platforms “morphing” into mainstream
•
• • •
Using a core database Adding Integration capabilities Business and spatial as peer data types GIS no longer the “centre of the universe”
• Interoperability is becoming a “must have” • Optimum choice depends on the application
For more information…
www.espatial.com dmiller@espatial.com
“1st Choice for Oracle Spatial”
enterprise embedded easy economic effective