Spatially Enabling Web APIs
through OGC Standards
Dr. Gobe Hobona, PhD
Director of Product Management, Standards
Open Geospatial Consortium
#OGCAPI
What is OGC?
A hub for thought leadership, innovation, and standards for all
things related to location
Our Vision
Building the future of location with community
and technology for the good of society
Our Mission
Make location information Findable, Accessible,
Interoperable, and Reusable (FAIR)
Our Approach
A proven collaborative and agile process combining consensus-based
standards, innovation project, and partnership building
Location information is everywhere
5-Step Process to Spatially Enabling your API
1. Identify the type of location-referenced information that you would like to
publish or access
2. Identify the relevant OGC API Standard at ogcapi.ogc.org
3. Familiarize yourself with the requirements documented in the relevant OGC
API Standard
4. Use the OpenAPI definition document of the OGC API to help build your
implementation
5. Test your implementation for compliance to the relevant OGC API Standard
What is an OGC Standard?
• A document, established by consensus and approved by the OGC
Membership, that provides rules and guidelines, aimed at the optimum
degree of interoperability in a given context.
Photo taken March 2018
New York
JULY
Australia
SEPTEMBER
Singapore
APRIL
Helsinki & North
MARCH
Paris
DECEMBER
London
OCTOBER
Jakarta
FEBRUARY
Hong Kong
AUGUST
JUNE
India
MAY
Check out our API Conferences here
50+ events since 2012, 14 countries, 2,000+ speakers, 50,000+ attendees,
300k+ online community
Want to talk at one of our conferences?
Apply to speak here
‘Why’ OGC API Standards?
• APIs are a very effective and popular enabler of rapid software development
• API variations without standardized elements can degrade interoperability
• Open Standards improve interoperability between independent
implementations
• OGC API Standards enhance geospatial interoperability between Web APIs
OGC API Development Principles
Spatially enable Web APIs in a consistent way
• Spatial Data on the Web Best Practices
• Leverages OpenAPI
• Focus on developer experience and usability
• Modular building blocks for access to spatial data that can be used in data
APIs
• Open development; Public GitHub, Early implementations,
In-depth validation
Approved and Candidate OGC API Standards
Certification as OGC Compliant
• Executable Test Suites
• OGC Compliance Badge
• Product Database
For more information
compliance@ogc.org
What to expect
… as an API Developer
ogcapi.ogc.org
Everything is on GitHub, including the discussions
All defined in OpenAPI
Overview of OGC API - Features
Resource Path
HTTP
method
Landing page / GET
Conformance declaration /conformance GET
Feature collections /collections GET
Feature collection /collections/{collectionId} GET
Features /collections/{collectionId}/items GET
Feature /collections/{collectionId}/items/{featureId} GET
Overview of OGC API - Processes
Resource Path
HTTP
method
Landing page / GET
Conformance declaration /conformance GET
Process list /processes GET
Process description /processes/{processID} GET
Process execution /processes/{processID}/execution POST
Job status info /jobs/{jobID} GET
Job results /jobs/{jobID}/results GET
Job list /jobs GET
Job status info /jobs/{jobID} DELETE
Overview of OGC API - Environmental Data Retrieval
Resource Path
HTTP
method
Landing page / GET
Conformance declaration /conformance GET
Description of the collections of
spatio-temporal data available from
this API. /collections GET
Identifies a collection of spatio-
temporal data with the unique
identifier {collectionId} /collections/{collectionId} GET
Identifies an Information Resource of
type {queryType} associated with
the {collectionId} collection. /collections/{collectionId}/{queryType} GET
Deployment as Building Blocks
Example Case Study: OGC API - Features
https://ogcapi.bgs.ac.uk
Publishing of geological data at the British Geological Survey
Example Case Study: OGC API - Processes
Analytical processing of RADARSAT satellite imagery
https://www.cubewerx.com/analytics
Example Case Study: OGC API – Environmental
Data Retrieval
Weather forecasting at the US National Weather Service
Innovation
Aviation
Geospatial
Data Cubes
COG & ZARR
CITE
Model Driven
Standards
Moving
Features
Geometries &
Features JSON
Attracting
Developers
Data Centric Security
Sensor Integration
Testbed-17
Topics
Upcoming Code Sprint
• 1st to 3rd March 2022 (Tentative Date): Joint OGC OSGeo ASF Code Sprint
Free registration, Free participation
Visit
ogcapi.ogc.org
What to expect
… as an end-user
Example Client Applications
25
5-Step Process to Spatially Enabling your API
1. Identify the type of location-referenced information that you would like to
publish or access
2. Identify the relevant OGC API Standard at ogcapi.ogc.org
3. Familiarize yourself with the requirements documented in the relevant OGC
API Standard
4. Use the OpenAPI definition document of the OGC API to help build your
implementation
5. Test your implementation for compliance to the relevant OGC API Standard
Summary
#OGCAPI
• OGC API Standards are becoming a key requirement for Web APIs offering
location-referenced information
• Early impact has already been seen across government, private and academic
sectors
• Organizations should spatially enable their Web APIs through OGC API
Standards to ensure the data is Findable, Accessible, Interoperable, and
Reusable (FAIR)
500+ International Members
110+ Member Meetings
60+ Alliance and Liaison partners
50+ Standards Working Groups
45+ Domain Working Groups
25+ Years of Not for Profit Work
10+ Regional and Country Forums
Innovation
120+ Innovation Initiatives
380+ Technical reports
Quarterly Tech Trends monitoring
Standards
65+ Adopted Standards
300+ products with 1000+ certified implementations
1,700,000+ Operational Data Sets
Using OGC Standards
Copyright © 2021 Open Geospatial Consortium
Thank You
Community
Visit
ogc.org
New York
JULY
Australia
SEPTEMBER
Singapore
APRIL
Helsinki & North
MARCH
Paris
DECEMBER
London
OCTOBER
Jakarta
FEBRUARY
Hong Kong
AUGUST
JUNE
India
MAY
Check out our API Conferences here
50+ events since 2012, 14 countries, 2,000+ speakers, 50,000+ attendees,
300k+ online community
Want to talk at one of our conferences?
Apply to speak here

apidays LIVE Paris 2021 - Spatially enabling Web APIs through OGC Standards by Dr.Gobe Hobona, Open Geospatial Consortium

  • 1.
    Spatially Enabling WebAPIs through OGC Standards Dr. Gobe Hobona, PhD Director of Product Management, Standards Open Geospatial Consortium #OGCAPI
  • 2.
    What is OGC? Ahub for thought leadership, innovation, and standards for all things related to location Our Vision Building the future of location with community and technology for the good of society Our Mission Make location information Findable, Accessible, Interoperable, and Reusable (FAIR) Our Approach A proven collaborative and agile process combining consensus-based standards, innovation project, and partnership building
  • 3.
  • 4.
    5-Step Process toSpatially Enabling your API 1. Identify the type of location-referenced information that you would like to publish or access 2. Identify the relevant OGC API Standard at ogcapi.ogc.org 3. Familiarize yourself with the requirements documented in the relevant OGC API Standard 4. Use the OpenAPI definition document of the OGC API to help build your implementation 5. Test your implementation for compliance to the relevant OGC API Standard
  • 5.
    What is anOGC Standard? • A document, established by consensus and approved by the OGC Membership, that provides rules and guidelines, aimed at the optimum degree of interoperability in a given context. Photo taken March 2018
  • 6.
    New York JULY Australia SEPTEMBER Singapore APRIL Helsinki &North MARCH Paris DECEMBER London OCTOBER Jakarta FEBRUARY Hong Kong AUGUST JUNE India MAY Check out our API Conferences here 50+ events since 2012, 14 countries, 2,000+ speakers, 50,000+ attendees, 300k+ online community Want to talk at one of our conferences? Apply to speak here
  • 7.
    ‘Why’ OGC APIStandards? • APIs are a very effective and popular enabler of rapid software development • API variations without standardized elements can degrade interoperability • Open Standards improve interoperability between independent implementations • OGC API Standards enhance geospatial interoperability between Web APIs
  • 8.
    OGC API DevelopmentPrinciples Spatially enable Web APIs in a consistent way • Spatial Data on the Web Best Practices • Leverages OpenAPI • Focus on developer experience and usability • Modular building blocks for access to spatial data that can be used in data APIs • Open development; Public GitHub, Early implementations, In-depth validation
  • 9.
    Approved and CandidateOGC API Standards
  • 10.
    Certification as OGCCompliant • Executable Test Suites • OGC Compliance Badge • Product Database For more information compliance@ogc.org
  • 11.
    What to expect …as an API Developer
  • 12.
  • 13.
    Everything is onGitHub, including the discussions
  • 14.
  • 15.
    Overview of OGCAPI - Features Resource Path HTTP method Landing page / GET Conformance declaration /conformance GET Feature collections /collections GET Feature collection /collections/{collectionId} GET Features /collections/{collectionId}/items GET Feature /collections/{collectionId}/items/{featureId} GET
  • 16.
    Overview of OGCAPI - Processes Resource Path HTTP method Landing page / GET Conformance declaration /conformance GET Process list /processes GET Process description /processes/{processID} GET Process execution /processes/{processID}/execution POST Job status info /jobs/{jobID} GET Job results /jobs/{jobID}/results GET Job list /jobs GET Job status info /jobs/{jobID} DELETE
  • 17.
    Overview of OGCAPI - Environmental Data Retrieval Resource Path HTTP method Landing page / GET Conformance declaration /conformance GET Description of the collections of spatio-temporal data available from this API. /collections GET Identifies a collection of spatio- temporal data with the unique identifier {collectionId} /collections/{collectionId} GET Identifies an Information Resource of type {queryType} associated with the {collectionId} collection. /collections/{collectionId}/{queryType} GET
  • 18.
  • 19.
    Example Case Study:OGC API - Features https://ogcapi.bgs.ac.uk Publishing of geological data at the British Geological Survey
  • 20.
    Example Case Study:OGC API - Processes Analytical processing of RADARSAT satellite imagery https://www.cubewerx.com/analytics
  • 21.
    Example Case Study:OGC API – Environmental Data Retrieval Weather forecasting at the US National Weather Service
  • 22.
  • 23.
    Aviation Geospatial Data Cubes COG &ZARR CITE Model Driven Standards Moving Features Geometries & Features JSON Attracting Developers Data Centric Security Sensor Integration Testbed-17 Topics
  • 24.
    Upcoming Code Sprint •1st to 3rd March 2022 (Tentative Date): Joint OGC OSGeo ASF Code Sprint Free registration, Free participation Visit ogcapi.ogc.org
  • 25.
    What to expect …as an end-user
  • 26.
  • 27.
    5-Step Process toSpatially Enabling your API 1. Identify the type of location-referenced information that you would like to publish or access 2. Identify the relevant OGC API Standard at ogcapi.ogc.org 3. Familiarize yourself with the requirements documented in the relevant OGC API Standard 4. Use the OpenAPI definition document of the OGC API to help build your implementation 5. Test your implementation for compliance to the relevant OGC API Standard
  • 28.
    Summary #OGCAPI • OGC APIStandards are becoming a key requirement for Web APIs offering location-referenced information • Early impact has already been seen across government, private and academic sectors • Organizations should spatially enable their Web APIs through OGC API Standards to ensure the data is Findable, Accessible, Interoperable, and Reusable (FAIR)
  • 29.
    500+ International Members 110+Member Meetings 60+ Alliance and Liaison partners 50+ Standards Working Groups 45+ Domain Working Groups 25+ Years of Not for Profit Work 10+ Regional and Country Forums Innovation 120+ Innovation Initiatives 380+ Technical reports Quarterly Tech Trends monitoring Standards 65+ Adopted Standards 300+ products with 1000+ certified implementations 1,700,000+ Operational Data Sets Using OGC Standards Copyright © 2021 Open Geospatial Consortium Thank You Community Visit ogc.org
  • 30.
    New York JULY Australia SEPTEMBER Singapore APRIL Helsinki &North MARCH Paris DECEMBER London OCTOBER Jakarta FEBRUARY Hong Kong AUGUST JUNE India MAY Check out our API Conferences here 50+ events since 2012, 14 countries, 2,000+ speakers, 50,000+ attendees, 300k+ online community Want to talk at one of our conferences? Apply to speak here