Latest revision to the Standards Guide provides recommendations on standards and good practices that ensure that the growing wealth of geospatial data and technologies can be shared, maintained, integrated, and applied.
OGC Testbed-18 will pave the way towards new levels of interoperability in areas as diverse as New Space, Machine Learning, Open Science, and Building Energy.
The 2nd Open Source Software and Open Standards Code Sprint will advance multiple ASF and OSGeo projects, supported by OGC Standards, including OGC API Standards. Sponsorship is still available.
The document outlines the implementation, packaging, and deployment of cross-cloud EO Applications - A step forward for greater efficiency and bringing the ‘user to the data.’
The Geotech IE will ensure that geotechnical engineering data can seamlessly move between GIS and BIM environments in support of engineering and infrastructure projects.
The Open Geospatial Consortium (OGC) has issued a Call for Participation (CFP) to solicit proposals for the OGC Geotech Interoperability Experiment (IE). Proposal submissions close on February 10, 2022.
Prashant Shukle brings to the role an understanding of OGC’s international operations & partnerships that will benefit the Consortium’s governance and strategy.
The Open Geospatial Consortium (OGC) Board of Directors announces that it has elected Prashant Shukle as its new Vice Chair.
As the successor to the WPS standard, OGC API - Processes provides a means to build simple-to-understand Web APIs through which complex computational tasks can be executed.
Latest version of the I3S Community Standard, used for streaming large 3D datasets to desktop and mobile devices, improves performance and scalability with enhancements to 3D Object and Integrated Mesh layers.
Congratulations to Chris Little, awarded the 2021 Gardels Award for leading impactful efforts in the meteorology and geospatial science communities, including his exemplary chairing of OGC Working Groups.
OGC API - Common - Part 2: Geospatial Data provides a common connection between the API landing page (defined by Part 1) and resource-specific details.
