Spatially enabling Web APIs through OGC Standards
summary
Open Geospatial Consortium outlines a five‑step method to add location support to Web APIs, publishes modular OGC API specs (Features, Processes, Coverages, Tiles, Records, DGGS) with OpenAPI 3.0.2 definitions, and runs Testbed 17 with 500+ members. Implementations include British Geological Survey publishing vector data, Kubworks processing Radarsat to locate vessels, and a US National Weather Service EDR client. Executable test suites and the OGC validator enable certification, and OGC API Features and OGC API Processes provide the concrete endpoints and job-monitoring paths.
AI-written summary · about
chapters (13)
- 0:00Start
- 2:23Ogc Has Developed a Five-Step Process To Specially Enable any Web Api
- 3:09What Is an Ogc Standard
- 3:54Why Are We Developing Ogc Api Standards and Why Should You Be Interested in in Ogc Api Standards
- 6:42What Are those Ogc Api Standards
- 9:58Executable Test Suites That Are Accessible from the Ogc Validator
- 10:49What Can You Expect as an Api Developer
- 13:07Examples of Ogc Api Standards
- 13:39Ogc Api Features
- 16:34Case Studies
- 20:36What Can You Expect as an End User
- 21:20Enable Your Web Api
- 21:57Summary
related talks
31mOGC APIs: Web API Standards for Handling and Exchanging Location Data
21mOpen Standards for Getting your APIs into the Geospatial Ecosystem.
20mOGC API Standards: Enhancing Digital Infrastructure
39mAn introduction to the OGC API - Processes and practical examples
27mThe Close Bond Between Open Standards and Open Source
12mGeoEnabling Gov 2.0
48mEmpowering AI Innovation Through Open Geospatial Ecosystems
22mSpatial Analysis and the Geoweb