Philadelphia, May 2–4, 2005
www.locationintelligence.net
How OGC Location Service Standards
Enable Integration with Enterprise IT
Carl Reed, PhDCTO, Open Geospatial Consortium
May 2, 2005
What is the OGC?
• The Open Geospatial Consortium, inc. (OGC) is a non-profit international voluntary consensus standards organization that is leading the development of standards for geospatial and location based services.
– The OGC facilitates a consensus process in which government, private industry, and academia collaborate to create open and extensible software application programming interfaces for geospatial and other mainstream information technologies
The OGC vision enables a global geospatial and IT community
Composed of many collaborating organizations... authoring and publishing Composed of many collaborating organizations... authoring and publishing open standards for geospatial interoperabilityopen standards for geospatial interoperability
Some OGC Members providing solutions in LBS space
• Autodesk• Oracle• MapInfo• Intergraph• ESRI• Navteq• TeleAtlas• Ionic Enterprises• CPdQ• Webraska• TelContar• Northrup Grumman• Boeing
• Ordnance Survey• DeLorem• Mobile GIS• FEMA• NGA• Others
What is Spatial Interoperability?
• Interoperability is the ability to:– Link business processes across organisational lines and
cost-effectively share information resources, – Find data, information and processing tools no matter
where they are physically located, and– Seamlessly operate no matter what type of computer
system or display device is being used, whether local or remote
• Also known as “on demand access”– Real time– As and when needed– Vendor and content model independent– Accessing the source of operational data
“My stuff operates with your stuff, and I don’t care where it is, how it works
and what the format is”
“Invisible Success” of the enabling framework
MIC alert: storm warning for Liverpool area. Take precautions to protect your home and car from damage.
OGC Standards and the Location Services Market
The OGC OpenLS Interface Suite• OGC - Open Location Services – Core Interfaces
defined as XML for Location Services (XLS) Supports both HTTP and SOAP.– OpenLS ADTs– OpenLS Directory Service– OpenLS Geocoder – OpenLS Reverse Geocoder– OpenLS Presentation Service– OpenLS Route Service– OpenLS Gateway Service (Interface to OMA MLP)
• And of course GML (Geography Markup Language) for encoding payloads of geospatial content.
Role of OpenLS in LS Server Architecture
Provide Subscribers with Location-Based Application Services / Content
On the go
At work or home
Portal &Service
Platforms
GeoMobility Server
GMLC/MPC
Internet
•Navigation•Discovery•Presentation
•Maps•Routes•Directories•Points of Interest•Addresses
CORENETWORK
MobileSwitch
Position Determination Methods:LDT/PDE: cell/ID/sector, A-GPS,
E-OTD, AOA, TDOA, TOA
Example LBS Technology Providers Using OpenLS Interfaces
• Hutchison 3G – Location Enabled Application• Autodesk – LocationLogic• ESRI – Arc Location Services• TelContar – Drill Down Server version 3.2• Oracle - Oracle 9iAS Wireless Version 9.0.3 and Oracle
Application Server 10g Wireless Edition(Version 9.0.4)• Ionic Enterprise – RedSpider Lobos (LOcation Based
OGC Solution)• MapInfo – Envinsa 3.0 (SOAP and HTTP)
Implementations of OpenLS• Intergraph – Will be part of next release of LocationServer
and GeoMedia WebMap• Webraska - SmartZone Geospatial Platform (Java and
SOAP)• LBS research Team, Telematics Research Division, ETRI,
South Korea• SAM (Mobile Services and Applications) is a CPqD Project
that aims to develop Location Based Services to public administration (Presentation, Gateway, and Geocoding)
• Sprint – Mobility Framework• Verizon• Others . . .
Example Application that Uses Standard Interfaces
Benefits of moving to a standards based LBS
architecture
Benefits and Value of using standard interfaces and protocols for LBS
• Integrate (fuse) many information resources on demand for better customer experience and decision support.
• Protect investment in legacy systems• More easily respond to changes in the LBS infrastructure• Change technology providers as well as better protect and
enhance relationships with existing partners.• Access and utilize content from many partners without
requiring a common format or model.– Can quickly wrap local or remote routing and geocoding
engines of any vendor (comment from a user)• More effectively plug into larger information infrastructures• Reduce coding development and maintenance costs
Cost reduction
• Initially the task of adding security to a Web service took 20,379 lines of code; adding reliable messaging took 5,988 lines of code and adding transactions took 25,507 lines of code, Rudder said. With an additional 4,442 for infrastructure plumbing, the total came to more than 56,000. Now security, reliable messaging, and transactions each require one line of code, he said.– Referring to the value of using the WS-Security and
WS-Discovery standards
OGC Collaboration with other Standards Orgs
• OMA MLP 3.1 uses OGC standards and models for geometry and coordinate reference system expression.
• A new MOU defines how OGC and IEEE 1451 (sensors) collaborate and work towards harmonizing our standards work.
• Work with OASIS in several areas.• Work with ISO TC 211 in numerous joint work items.• The new Liberty Alliance geo-location Web service
interface references MLP 3.1 and therefore OGC standards.
• Collaborating with IETF Geopriv WG. The proposed enhancements to PIDF for location uses OGC GML encoding.
Webcam
EnvironmentalMonitor
StoredSensor
Data
Satellite-borneImaging device
HealthMonitor
AirborneImaging Device
Business IntelligenceAnalyst
StoredImagery
Data
StoredVector
Data
Internet and Intranet
Open interface ][ Integration with Sensor
Nets
Support Emergency Notification & Incident Reporting
Situation Notification ServiceSituation Notification Service• Common means for sharing Common means for sharing
location-based emergency location-based emergency notification messagesnotification messages
• Collaboration with OASISCollaboration with OASISIncident ReportsIncident Reports• Location-based incident reports Location-based incident reports
for cross-jurisdictional usefor cross-jurisdictional use• Collaborate with DOJCollaborate with DOJProjects with ORNLProjects with ORNL
Emergency Command Center
Summary – the value of good standards
• Enable innovation• Protect legacy and future investments• Enable integration and interoperability• Future proof current applications• Leverage value of legacy applications and infrastructure• Flexibility of choice and implementation • Enable co-opetition• Increase partner loyalty• Increase win-win in partner relationships• Enables technology convergence
Thank you for your attention
Carl Reed, PhD
Open Geospatial Consortium
www.opengeospatial.org