Since their beginning, the SpatioTemporal Asset Catalog (STAC) specification and OGC API - Features have been evolving together and continually aligning. This post explains the relationship between STAC, OGC API - Features, and OGC itself.
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 second of a series of blog posts, Ignacio "Nacho" Correas, Chief Technology Innovation Officer at Skymantics, offers some tips and best practices for creating an interoperable routing engine.
The OGC 116th Member Meeting was held virtually from 14–18 September, 2020. Every quarter, OGC Member Meetings highlight all things location, including standards development, innovation initiatives, and new technologies and domains that are powered by geospatial data.
Together, the Open Portrayal Framework and the SymCore standard define a modern and modular approach to portrayal based on the intent to have many extensions from a common conceptual model and many encodings of those extensions. With this approach, a common symbology definition can be implemented in multiple encodings and easily shared by multiple clients to provide similar visualization effects to different users. The OPF helps to define a seamless online and offline experience that incorporates emerging OGC APIs for enhanced sharing of features and coverage data, images, and tiles for networked users and GeoPackages for disadvantaged and disconnected users.
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'?