Only July 28 and 29, 2020, OGC hosted a virtual sprint to advance the OGC API - Maps candidate standard, one of many APIs being rolled out by the organization to revolutionize how location information is accessed and shared across the industry. Sponsored by Ordnance Survey, participants prototyped implementations of the draft OGC API - Maps - Part 1: Core standard, identifying missing requirements, and documenting these requirements so that the candidate standard could be improved.
Like so many nations, New Zealand is engaged in a contentious game of environmental tug-of-war. On one side, ecological enthusiasts who want to preserve and protect the country’s lush, otherworldly landscape, which is beloved by visitors and locals alike for its majestic mountains, verdant valleys and bewitching beaches. On the other side, economic opportunists who want to capitalize on the country’s natural resources in order to make New Zealand as productive as it is pretty. Along with arable land and precious mineral deposits, the rope on which Kiwis on both sides are constantly tugging comprises the country’s most valuable commodity: fresh water.
As part of OGC's Open Routing API Pilot, participants developed an API that allowed requests for routes from different users in an interoperable and standardized way via Web protocols. In this first of a series of blog posts, Ignacio "Nacho" Correas, Chief Technology Innovation Officer at Skymantics, summarizes Skymantics’ experiences and findings in building an interoperable routing engine using OGC standards.
Like almost every event in 2020, due to the COVID-19 crisis, OGC’s 115th Member Meeting was completely virtual. Yet despite the change, more than 400 people from across the world logged on between 15–22 June 2020 (with three Working Groups meeting on June 10 & 11) to attend the meeting. Using a combination of GoToMeeting and Gitter, participants joined in on community discussions, presentations, panels, casual ‘lunch break’ chats, and special sessions on health, simulation & gaming, smart roads, insurance, OGC APIs, and more.
Further testing and refinement to the OGC API - Tiles candidate standard - the spiritual successor to one of OGC’s most popular standards, the Web Map Tile Service (WMTS) - has occurred during another successful OGC Sprint. The candidate standard is just one of several efforts forming OGC’s move towards modular, resource-oriented, OpenAPI-based standards.
Another step towards the creation of the OGC Environmental Data Retrieval (EDR) API Standard has been completed: the successful testing of some of the API’s capabilities during the OGC Environmental Data Retrieval API Sprint. The virtual event was held from March 18-20, 2020. A final report detailing the EDR API Sprint is now available on GitHub.
But what is the upcoming EDR API? And how does it improve and simplify access to 'big data'?
A joint OGC / ESIP Coverage and Processing Analytics API development sprint was held on January 6-7, 2020. The Sprint was held in conjunction with the ESIP Winter Meeting. This sprint builds on the OGC API Hackathon in June 2019, and the OGC API Features and Catalogues Sprint in November 2019. The ESIP/OGC sprint focused on OGC API-Coverages, API-Processes, and API-Common as part of the overall development of OGC APIs.
The Open Portrayal Framework in OGC Testbed 15 is developing a conceptual model for styles together with a series of new APIs for styles, images, maps and tiles handling.
In the Open Portrayal Framework, a style is an encoding with essential information about itself, e.g. title, abstract description of the style, a thumbnail, and information about the data it can be applied to. These metadata elements allow users to share, discover, select, and apply a style. A style further contains a sequence of rules or instructions that define how mapping engines shall render vector or raster data or, in OGC speak, features and coverages.
Last month, OGC, Ordnance Survey, the European Space Agency, and NGA held a hackathon in London aiming to advance OGC APIs.
It is envisaged that the output of the hackathon will be instrumental to the evolution of OGC web service standards to a modern API-based approach, setting the course for open geospatial standards for the next decade. The output should lead to a solid, common core and advancement of a whole new generation of OGC standards that are flexible in modern IT environments. This does not mean that existing OGC web service standards will fade away. Instead, it means that a new suite of OGC standards will give developers and users the option of leveraging capabilities offered by Web APIs.
By now many of you have heard about new OGC standards in work that leverage OpenAPI and are being characterized as anything from evolutionary to revolutionary. I’d like to give you a few minutes’ read to explain these exciting developments in OGC.