1. Expanding SDI Thinking from File Transfer to Geospatial SOA GSDI 11
Raj Singh
Director, Interoperability Programs
Open Geospatial Consortium
June 15, 2009

2. Workshop Outline OGC Overview: 20 minutes
the organization
standards overview
technology framework
GeoWeb State-of-the-Art: 10 minutes
A Framework for Understanding S+DIs: 20 minutes
Group Session on Modeling one’s own SDI: 40 minutes
Individual work
Group discussion (1 or 2 individual examples)

3. What is the OGC?
Not-for-profit, international standards development consortium
380+ industry, government, and university members
Specification Development Program (since 1994)
Class A liaison with ISO/TC211
27 Implementation Standards, with additional standards profiles, and best practice documents…
Several candidate Implementation Standards in progress
OGC Reference Model defines interoperable geo architecture
Mission
To advance the development and market adoption of open standards for geospatial interoperability.
Interoperability Program (since 1999)
A global, innovative, hands-on engineering and testing program designed to accelerate interface development and bring interoperability to the market
Outreach and Community Adoption Program (since 2002)
Awareness raising, education and training, encourage take up of OpenGIS® standards, business development
overview on slides 3-9

4. Selected Membership Academia/Research: 100+ institutions worldwide
Sensors: 3eTI, Smart Sensor Systems, IRIS Corp, Overwatch Systems…
Government: JRC, EUSC, ESA; US DHS, EPA, Census, Geological Survey, Army Corps TEC, DISA, NGA, NASA; Oak Ridge National Labs; United Nations; Natural Resources Canada; Geosciences Australia; and others at the national, provincial, state and local levels.
Geospatial/AEC/CAD: Analytical Graphics Inc., Autodesk, Bentley Systems, Blue Marble Geographics, Cadcorp, ESRI, e-spatial, Galdos, Intergraph, Ionic, Laser-Scan, MapInfo, NavisWorks, NAVTEQ, PCI Geomatics, others…
Infrastructure: Oracle, Google, Shell Exploration…
Integrators / Engineering: BAE Systems, Boeing, EADS Astrium, Lockheed Martin, GeoDecisions, Raytheon, Northrop Grumman, General Dynamics, Parsons Brinkerhoff, Mitre, Hansa Luftbild, Tetra Tech, Michael Baker, others…
Telecom/LBS: Telecom. Systems, Tele Atlas N.V., SiRF

5. Geospatial Interoperability and NCES Applicable Open Standards / Organizations
International Organization for Standards (ISO)
World Wide Web Consortium (W3C)
Digital Geospatial Information Working Group (DGIWG)
OASIS
Open Mobile Alliance (OMA)
Internet Engineering Task Force (IETF)
buildingSMART International / Alliance (bSi / bSa)
IEEE Technical Committee 9 (Sensor Web)
Web3D Consortium
Others

6. OGC Policy Positions Group on Earth Observations
National Geospatial-Intelligence Agency
US Federal Enterprise Architecture (Geospatial Profile)
NATO C3
United Nations Strategic Plan

7. More OGC-based Policy Positions
USGS and NASA are Strategic Members (our highest level)
USGS Framework Features served with WFS and WMS
OGC is a Participating Organization of GEO and leads the task to create the GEOSS persistent network of publicly accessible services for demonstration and research.
Canada Geospatial Data Infrastructure (CGDI) Implements OGC Web Service Specifications
UK Ordnance Survey using GML format to distribute its MasterMap product
European Union INSPIRE technical architecture built around OGC specifications
Numerous OGC standards on the DISR with NGA adoption
CIA and DHS have adopted OGC as part of their Geospatial Enterprise Architectures

8. OGC Standards

9. Approved OpenGIS® Standards
Tightly coupled
Simple Feature Access – OLE, SQL, CORBA {ISO}
Grid Coverage Service
Coordinate Transformation
Data Access and Presentation
Sensor Observation Service (SOS)
Style Layer Descriptor (SLD)
Web Map Service (WMS) {ISO}
Web Feature Service (WFS) {ISO}
Web Coverage Service (WCS) and related extensions
Discovery
Catalog Services for the Web (CS/W) and various profiles
Encodings
Geography Markup Language (GML) {ISO}
KML
Observations and Measurements (O&M
SensorML (SML)
Symbology Encoding (SE)
TransducerML (TML)
Web Map Context (WMC)
Processing
Open Location Services (OpenLS)
Sensor Planning Service (SPS)
Web Processing Service
Other
GeoXACML
Geospatial Objects
GML in JP2000
Web Service Common
Available free of charge at
I won’t spend a great deal of time today going through the intricacies of each of our specifications, but I do want you to visit our site and review the 27 OpenGIS Implementation Specifications that have been formally approved for adoption by our membership.
These specifications represent a solid reference architecture for geoprocessing interoperability, focused heavily on Web Services, and experiencing substantial implementation in the market. I’ll talk about that in a moment. But first, let me summarize how some of these specifications empower the processes of geospatial discovery, access, integration and application. 9 9

10. SEARCH

11. Publishing and Discovery
OGC Catalog Service 2.1.2,
ISO Metadata Profile
Z39.50 Profile
OASIS ebRIM Profile
RegRep in the works
Support publishing and discovery of distributed geospatial data and associated services 11 11

12. Catalogs/Registries
Catalogs for services, data, styles, catalogs, etc.
Provide easy update and maintenance of discovery metadata
Provide standard interfaces for registration (Publish)
Support automated cross-catalog updates (harvesting)
Provide easy discovery of resources (Find)
Provide standard interfaces for discovery
Provide standard query language(s)/metadata
Provide associations among related objects
Goal is to enable Publish and Find with or without human intervention

13. GEOSPATIAL INFORMATION ENCODING

14. Geography Markup Language: Representing Geographic Features
Another Information
Community’s Schema
Highway is:
_Pavement thickness
_Right of way
_Width ….
Cell transm. Platform is:
_Location
_No. of antennas
_Elevation
GML
Support for complex geometries, spatial and temporal reference systems, topology, units of measure, metadata, feature and coverage visualization.
Backward compatible
One Information
Community’s Schema
Road is:
_Width
_Lanes
_Pavement type ….
Cell tower is:
_Owner
_Height
_Licensees
Mayberry’s Cell Tower
(an instance of Cell Transm. Platform
in another IC’s schema)
Mayberry Road
(an instance of Road
in one IC’s schema)
GML defines a data encoding in XML that allows geographic data and its attributes to be moved between disparate systems
Version 3.2 advances interoperability on all fronts!!

15. Geography Mark-up Language (GML) Application Schema Examples
CityGML (
Common information model for the representation of 3D urban objects. It defines the classes and relations for the most relevant topographic objects in cities and regional models with respect to their geometrical, topological, semantic and appearance properties. Included are generalization hierarchies between thematic classes, aggregations, relations between objects, and spatial properties.
GeoSciML (
GeoSciML accommodates the goal of representing geoscience information associated with geologic maps and observations, as well as being extensible in the long-term to other geoscience data.
An approved standard in that community
MarineXML (
Marine Data exchange based on ISO19136 (GML Feature Types). The alignment between ISO and OGC on ISO19136 makes GML the clear (only) choice for developing an XML-based framework for marine data exchange.
AIXM/GML (
The Aeronautical Information Exchange Model (AIXM) Specification supports the data-centric environment. It supports aeronautical information collection, dissemination and transformation throughout the data chain

16. VECTOR DATA ACCESS

17. Web Feature Service (WFS)
GetCapabilities
<Service>
<Name>CubeWerx WFS</Name>
<Title>CubeWerx Web Feature Service</Title>
<Abstract>Web Feature Server maintained by X.</Abstract>
<OnlineResource>
</Service>
<!– Defines the list of feature types that this instance can operate upon and -->
<!-- which operations are supported on each feature type-->
<FeatureTypeList>
<Operations> <Query/> </Operations>
<FeatureType>
<Name>Roads</Name>
<SRS>EPSG:4326</SRS>
<LatLongBoundingBox minx="-179" miny="-85“ maxx="179“ maxy="83"/>
<Operations>
<Insert/>
<Update/>
<Delete/>
</Operations>
</FeatureType>
</FeatureTypeList>
<!– Defines the capabilities of the filter supported by this feature instance-->
<ogc:Filter_Capabilities>
<ogc:Spatial_Capabilities>
<ogc:Spatial_Operators> <ogc:BBOX/> </ogc:Spatial_Operators>
</ogc:Spatial_Capabilities>
</ogc:Filter_Capabilitites>
<Capability>
<!-- defines which WFS operations the service supports, etc. -->
</Capability>
Client
Opaque Feature Store
Web Feature Server
WFS
GetCapabilities
Request
Capabilities
Response

18. Web Feature Service (WFS)
DescribeFeatureType
<?xml version="1.0" ?>
<DescribeFeatureType version="1.0.0“ service="WFS"
xmlns="
xmlns:ns01="
xmlns:xsi="
<TypeName>ns01:Roads</TypeName>
</DescribeFeatureType>
<complexType name=“Roads">
<complexContent>
<extension base="gml:AbstractFeatureType">
<sequence>
<element name="WKB_GEOM“ type="gml:LineStringPropertyType">
<element name="SURFACE_TYPE" minOccurs="0">
</element>
<element name="NLANES" nillable="true" minOccurs="0">
<simpleType><restriction base="integer">
<totalDigits value="2"/> </restriction> </simpleType>
</sequence>
</complexContent>
</complexType>
Client
Opaque Feature Store
Web Feature Server
WFS
DescribeFeatureType
Request
FeatureType
Description
Response

19. Web Feature Service (WFS)
GetFeature
<GetFeature version="1.0.0“ service="WFS“
xmlns:myns=
<Query typeName="myns:ROADS“>
<ogc:PropertyName>myns:PATH</ogc:PropertyName>
<ogc:PropertyName>myns:LANES</ogc:PropertyName>
<ogc:Filter>
<ogc:Within> <ogc:PropertyName>myns:PATH</ogc:PropertyName>
<gml:Box>
<gml:coordinates>50,40 100,60</gml:coordinates>
</gml:Box>
</ogc:Within>
</ogc:Filter>
</Query>
</GetFeature>
<wfs:FeatureCollection
<gml:featureMember>
<ROADS fid="ROADS.100">
<PATH>
<gml:LineString gid="1“ srsName="epsg.xml#4326">
<gml:coordinates>10,10 10,11 10,12 10,13</gml:coordinates> </gml:LineString>
</PATH>
<NLANES>4</NLANES>
</ROADS>
</gml:featureMember>
<ROADS fid="ROADS.105">
<gml:LineString gid="2“ srsName="epsg.xml#4326">
<gml:coordinates>10,10 10,11 10,12</gml:coordinates> </gml:LineString>
<NLANES>2</NLANES>
</FeatureCollection>
Client
Opaque Feature Store
Web Feature Server
WFS
GetFeature
Request
Feature
Data
Response

20. COVERAGE DATA ACCESS

21. Coverages Represent Space-Varying Phenomena
Point grid (e.g., wind speed & direction)

22. WCS Same methodology as WFS GetCapabilities DescribeCoverageType
GetCoverage

23. WEB MAPPING

24. Web Map Service (WMS) can get multiple maps
Elevation
Cloud Cover
Borders
Cities
Multiple
overlaid maps
One GetMap
request:

25. OWS Integrated Decision Support
Web Feature
Server
Web Coverage
Server
Web Map
Server
With OGC web services, an analyst or operator can dynamically access that data which is relevant to the task at hand, directly from the authoritative data steward, using a variety of tools.

26. Sensor Web Enablement

27. OGC Sensor Web Enablement
Industrial
Process
Monitor
Sensors connected to and discoverable on the Web
Sensors have position & generate observations
Sensor descriptions available
Services to task and access sensors
Local, regional, national scalability
Enabling the Enterprise
Automobile
As Sensor Probe
Environmental
Monitor
Traffic
Monitoring
Temp
Sensor
Stored
Sensor
Data
Airborne
Imaging
Device
Webcam
Strain
Gauge
Health
Monitor
Satellite-borne
Imaging Device

28. Sensor Web Enablement (SWE) Specifications
Information Models and Schema
Sensor Model Language (SensorML) for In-situ and Remote Sensors - Core models and schema for observation processes: support for sensor components, georegistration, response models, post measurement processing
Observations and Measurements (O&M) – Core models and schema for observations
TransducerML – adds system integration and real-time streaming clusters of observations
Web Services
Sensor Observation Service - Access Observations for a sensor or sensor constellation, and optionally, the associated sensor and platform data
Sensor Alert Service – Subscribe to alerts based upon sensor observations
Sensor Planning Service – Request collection feasibility and task sensor system for desired observations
Web Notification Service –Manage message dialogue between client and Web service(s) for long duration (asynchronous) processes
Sensor Registries – Discover sensors and sensor observations
DIB Applications - External Tasking, Mission Management, Distributed Sensor Planner
Sensor Planning Service
Provides a standard interface for planning and tasking sensors.
SPS interface operations include:
DescribeCollectionRequest()
GetFeasibility()
SubmitRequest()
UpdateRequest()
CancelRequest()
GetStatus()
ACTM – Airborne Common Tasking Message
Created to reflect the tasking information used by all DoD and IC platforms.
Provided as input to OWS-3 in support of the SPS maturation.
Sensor Alert Service
Under development in an OGC Interoperability Experiment

29. To integrate sensors into the Geospatial Web, need a standards based framework
Copyright 2008, OGC

30. Geospatial Digital Rights Management (GeoDRM)

31. Geospatial Digital Rights Management
OGC members are leveraging broader standards based Digital Rights Management (DRM) approaches in conjunction with OGC standards to validate their ability to support geospatial data and services use cases
Authentication
Pricing
As geographic content (geodata) and services become more widely available in digital form over ubiquitous networks, data becomes easier to distribute, share, copy and alter. While this is generally a good thing, many organizations involved in the production and trading of geodata find the need to protect their Intellectual Property (IP) assets through the digital distribution value chain. Organizations want to specify, manage, control and track geodata distribution within secure, open and trusted environments. A system of operating agreements and interoperable technologies are needed to enable broader distribution and use of geodata while protecting the rights of producers and users.
In or e-commerce models for dissemination and use of Intellectual Property (IP) assets, geodata are treated as commodities to be priced, ordered, traded and licensed. Direct monetary reward, however, is often not the motivation or is only secondary behind the desire for more rigorous control of IP assets. Harlan Onsrud of the GeoData Alliance argues that the incentive structures implicit in “library systems” are an appropriate model for motivating data producers, collectors and traders to document, share and otherwise disseminate their geodata. Onsrud observes that the library system is a “chaordic” framework of seemingly ad hoc agreements among stakeholders that strikes a balance supporting “…strong public goods, access and equity principles while fully protecting the intellectual property rights of authors and publishers.”
Licensing
Copyright
GeoDRM Reference Model:

32. STANDARDS-BASED LIGHTWEIGHT PAYLOADS AND MICRO-FORMATS

33. Mass Market Geo OGC Vision is being realized in ‘mass market geo’
Google Earth & Maps
Windows Virtual Earth
Yahoo Maps
Mobile phone location based services (e.g. Nokia Ovi)
Real time ‘sensor connection’ to the world coming soon
Standards for Mass Market Geo need to match weight of uses
Lightweight application schemas of encodings
GeoRSS
GeoJSON
Open Location Services

34. What is RSS?
RSS stands for Really Simple Syndication. It is a way to easily distribute a list of headlines, update notices, (alerts), and sometimes content to a wide number of people.

35. GeoRSS Encodings for expressing geography in RSS feeds
Multiple geometries: point, line, area or bounding box
Can be used for news feeds & alerts for weather warnings, earthquakes, photo sharing, database update alerts, traffic alerts, and on and on and on and on . . .
released in January of 2006

36. OGC Architecture

37. Benefits of OGC Standards - User Perspective
Introduce requirements into standards process – The OGC consensus process gives user organizations a way to align technology providers to cooperate on advancing important new standards
Improve choice in the marketplace – Because no single application meets the needs of all users, OGC standards are designed to enable a choice of products that can plug-and-play seamlessly in system or enterprise environments.
Reduced technology life cycle costs – Through the use of standards based COTS products, users have a better chance to reduce the cost of custom solutions and associated maintenance.
Rapid Insertion of New Technology – By working with industry and academia to implement OpenGIS® specifications in their offerings, organizations can maximize their ability to rapidly transfer new solutions into use.
Major Benefits for Industry:
Influence definition of new open standards
Reduce costs through cooperative development of standards with other OGC members
Shorten time to market
Quickly enter new markets
Develop new customer relationships and business partnerships
Rapidly provide precise solutions to meet immediate needs
Benefits of Participation in the OGC Process:
Understand the breadth of capability in the location IT market and identify opportunities for your organization.
Assure that your organizational and industry requirements are represented in OGC’s standards development programs.
Have direct and legal interaction with other industry players, meeting, partnering and building business relationships with a range of innovative organizations and potential customers.
Exercise leadership and steer the advancement/adoption of specifications important to your markets.
Stay on the forefront of innovation and be among the first to deploy standards- based products critical to your customer base.

38. OGC Architecture
OGC standards can be integrated into a web services architecture / platform so that:
Resource providers can advertise their resources (publish)
End users can discover resources that they need at run-time (find)
End users and their applications can access and exercise resources at run-time (bind)
This requires:
A forum where resources can advertise their capabilities and users can find the resources they need.
Self describing resources so applications can bind at run-time to the resources they find.

39. A Web Services Framework for OGC Standards
Bind
Discovery
Client
Map Viewer
Client
Imagery
Exploitation
Client
Value-Add
Client
SWE
Client
Symbol
Management
Client
Find
Multi-source, Integrated Application Client
GML
3.1.1
Open Web Context
SLD
Service
Metadata
SensorML
O & M
Service
Catalog
Style
Catalog
Device
Catalog
Other Type
Catalog
Data
Catalog
Catalog Services
Filter
Encoding
Web Map
Context
Transducer ML
Publish
Encodings SF
WFS
WCS
Acronyms: See for additional information. Click on “Documents” and review adopted specifications “OpenGIS Specifications”, publicly available “Discussion Papers”, “Requests” and “Recommendation Papers”. Some in work specifications are not yet public, but are accessible by OGC members.
CPS – Coverage Portrayal Service
FPS – Feature Portrayal Service
GML – Geography Markup Language
LOF – Location Organizer Folder
SensorML – Sensor Model Language
SCS – Sensor Collection Service
SLD – Styled Layer Descriptor
SF – Simple Features
SWE – Sensor Web Enablement
WCS – Web Coverage Service
WFS – Web Feature Service
WPS – Web Processing Service
WMS – Web Map Service Interface Specifications
WTS – Web Terrain Service
XIMA – XML for Image and Map Annotation
Coord.
Transf.
Service
Geocoder/
Rev Geoc*
WMS SE
WPS
Grid Cover
SOS
Gateway
Service*
Directory
Service*
Navigation
Service
KML
WTS
Gazetteer
SPS
GeoSync
Portrayal Services
Processing Services
Data Services
= OGC/IP Interface 39 39

40. A Framework for Understanding S+DIs

41. Characteristics of a (S)DI
Group of loosely affiliated organizations coming together to pursue a shared interest
Benefits and costs are spread unevenly across parties
No central point of control or authority
The infrastructure has little value without broad, sustained participation
Technology is the easy part!

42. 2009: year of “mass market geo?”
Firefox 3.5 has geo-location built-in
Google, Yahoo!, and Amazon have CRUD* web services for geo-data
Microsoft has geo services in the OS (v7)
Nokia launches Ovi Maps
Underlines the importance of framing SDI thinking within a larger IT perspective for many reasons:
- economies of scale: using same technology as mainstream IT benefits from commoditization of technology (e.g. Apache/Tomcat, online storage, compute clouds)
- SDI management is cheaper and more reliable when general IT manages it
CRUD: create, retrieve, update, delete
* CRUD: create, retrieve, update, delete

43. An SDI Taxonomy type capability examples file transfer read
file sharing, FTP, Web download
file transfer with search
read/search
portals, such as
GEOSS GEO Portal, Geospatial One-Stop
data infrastructure
read/write/search
Google MyMaps (plus Maps Data API)
spatial data infrastructure
distributed read/write/search/spatial search
GeoConnections Canada(?)
spatial compute cloud
read/write/search/spatial search/spatial processing ?

44. OGC Service Match with SDI Taxonomy
type
capability
examples
file transfer
read
WFS, WCS
file transfer with search
read/search
add CSW
data infrastructure
read/write/search
add WFS-T (no WCS-T), GeoRM
spatial data infrastructure
distributed read/write/search/spatial search
add Cascading WFS, Geo-Synchronization
spatial compute cloud
read/write/search/spatial search/spatial processing
add distributed WPS
WCS: Web Coverage Service
WFS: Web Feature Service
WFS-T: Web Feature Service – Transactional
CSW: Catalog Services for the Web
WPS: Web Processing Service
GeoRM: Geospatial Rights Management

45. Missing Standards for SDI

46. Service Chaining for Decision Support

47. “Chaining” Web Services For Decision Support
Assess Wildfire Activity
Demonstrated in 2004 as part of OGC Web Services Testbed 2
Service chaining creates Value-added products
OGC
Interfaces
Decision Support Client
Internet
WCS
(NASA Data Pool)
WCTS
(Producer-B, Vendor-2)
WICS
(Producer-C,Vendor-3)
WFS
(Producer-n, Vendor-x)
Web-based geospatial service chaining and decision support. How do we reliably and repeatedly combine results from several distributed services on the web to produce a result for a user? Service chaining is the term commonly used for the process of organizing disparate web based services into an orderly process. For instance, a raw image is sent to a service that performs a coordinate transformation. This services sends the transformed image to a classifier service that processes the image to highlight areas of active fire. The result of this service is sent to a user’s client along with other geospatial data such as vegetation overlays, transportation. Service chaining will play an important role in future capabilities. …
Web Servers

48. Service Chaining
OGC recent testbed work with BPEL has shown the value of users being able to access a suite of services and put them together into custom workflows.
Possible next steps:
Semantic Support for Service Workflow Development - What processes do we evolve to reliably and repeatedly build and execute service chains from registries of services?
How do we assure an audit trail for the state of services that come together in a chain to provide an answer to a user?

49. GEO-SYNCHRONIZATION

50. Atom Publication Protocol
…for publishing and editing Web resources belonging to periodically updated websites. The protocol at its core is the HTTP transport of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format (draft-ietf-atompub-format-06.txt).

51. How GeoSync works A Server publishes 2 things: A Client:
a Web Feature Service (the latest data set)
a “change feed”
A Client:
queries the WFS once for the data it wants
then queries the change feed for updates

52. “Big” data requests vs. update requests
WFS request: give me all the parcels in town X
new
data
change
log
WFS
adapter
WFS
client
spatial
database
spatial
database
GeoSync request: give me all changes to the parcels in town X since time T
GeoSync
adapter
GeoSync
client

53. Implementation in CGDI Pilot

54. The Draft GeoSynchronization Spec
OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot

55. GEOSPATIAL RIGHTS MANAGEMENT

56. GeoRM Progress
Geospatial Digital Rights Mangement Reference Model (GeoDRM RM)
GeoXACML Implementation Specification
What’s needed
GeoRM web service APIs
exemplary rights management schemes
GeoRM Summit on June 22 (at next TC)

57. DISTRIBUTED WEB PROCESSING SERVICE

58. Distributed Web Processing Service
Still a twinkle in our eye
No experimental implementations or documents yet
Sponsorship opportunity for a Testbed

59. Group Session on Modeling one’s own SDI

60. Questions At what stage is your SDI?
At what stage would you like to be in five years?
Who are the key partners? Is the general public one?
What policies must be in place for you to get there?
What technologies must mature for you to get there?

61. Answers from the Participants
Malaysia: stage 2, go to stage 4, all govt. agencies, policies in place but no enforcement (disconnect between technology and policy?), own all the technologies and OGC-compliant but not in full use yet.
Rwanda: at stage 1, local cooperation, SDI Pilot project at CGIS sponsored by GSDI, data & metadata inventory, have ESRI GPT and GeoNetwork and hope to use it to put up web geoportal, RITA ahs nat’l portal and inventorying geodata. Need policy for data sharing. Need technical expertise.
FGDC: US is very large, hard to cover the whole country for things like cadastre. SDI will be lower-resolution and not cover all types of data.
Europe INSPIRE: UK, Sweden, Iceland. at level 2 (read, search), key partners are public agencies at different levels. INSPIRE drives policy at the national level. Technology is often too complex for local government. Need different tech. for different levels of govt?
Cape Urban Observatory: sustainable human settlements data. want more private sector participation. informal settlements a mapping problem. Community self-mapping?
UAE: in data creation stage, early stage portal
Belgium: level 2. pricing policy is an issue. some data free, some not. local govt doesn’t have ability to get involved

62. OGC Public References Adopted Standards: OGC Reference Model:
OGC Reference Model:
OGC Web Services 4 Testbed Video Summary
Compliance Testing and Certification
List of Registered Products using OGC Standards:
OGC Network – member-contributed OGC “encyclopedia”
OGC User – case studies of OGC implementations in the global community
click on “Press Room”