FOSS4G 2022 general tracks

Welcome to the Open Source Geospatial Foundation, proud hosts of FOSS4G, and advocate for free and open source geospatial software everywhere. This is a call out to open source software developers; please join OSGeo and help us help you!

Join OSGeo today:

• Even just listing your project on the osgeo.org website is a great first step. Help us promote your technology so users can discover and enjoy your software.

• The OSGeo “community program” gives project teams a chance to join the foundation with an emphasis on supporting innovation and new projects. The foundation provides some direct support, assistance along with endorsement and recognition from our board.

• For established projects please join our “incubation program” to be recognized for excellence and as a full OSGeo committee.

Unlike other foundations, OSGeo does not require that you give up or transfer any Intellectual Property; we simply ask that you be spatial, open-source, and open to participation.

This presentation gives clear instructions on how to join OSGeo, and representatives from recent successful projects will be on hand to answer your questions.

Keeping (OGC) Geospatial Web Services up-and-running is best accommodated by continuous monitoring: not only downtime needs to be guarded,
but also whether the services are functioning correctly and do not suffer from performance and/or other Quality of Service (QoS) issues.
GeoHealthCheck (GHC) is an Open Source Python application for monitoring uptime and availability of OGC Web Services.
In this talk we will explain GHC basics, how it works, how you can use and even extend GHC (plugins).

There is an abundance of standard (HTTP) monitoring tools that may guard for general status and uptime of web services.
But OGC web services often have their own error, "Exception", reporting not caught by generic HTTP uptime
checkers. For example, an OGC Web Mapping Service (WMS) may provide an Exception as a valid XML response or
in a error message written "in-image", or an error may render a blank image.
A generic uptime checker may assume the service is functioning as from those requests and an HTTP status "200" is returned.

Other OGC services may have specific QoS issues that are not directly obvious. A successful and valid "OWS GetCapabilities" response may not
guarantee that individual services are functioning correctly. For example an OGC Web Feature Service (WFS) based on a dynamic database may
return zero Features on a GetFeature response caused by issues in an underlying database. Even standard HTTP checkers supporting "keywords"
may not detect all failure cases in OGC web services. Many OGC services will have multiple "layers" or feature types, how to check them all?

What is needed is a form of semantic checking and reporting specific to OGC services!

GeoHealthCheck (GHC) is an Open Source (MIT) web-based framework through which OGC-based web services can be monitored. GHC is written in
Python (with Flask) under the umbrella of the GeoPython GitHub Organization. It is currently an OSGeo Community Project.

GHC consists of two parts: (1) a web-UI app (using Flask) through which OGC service endpoint
URLs and their checks can be managed, plus for visualising monitoring-results and (2) a monitoring engine that executes scheduled
"health-checks" on the OGC service endpoints. Both parts share a common database (via SQLAlchemy, usually SQLite or PostgreSQL).
The database also stores all historic results, allowing for various forms of reporting.

GHC is extensible: at this moment of writing a plugin-system is developed for "Probes" in order to support an expanding number of
cases for OGC specific requests and -checks. Work is in progress to provide a GHC API for various integrations.

Links:
- Website: http://geohealthcheck.org
- Sources: https://github.com/geopython/GeoHealthCheck
- Demo: http://geohealthcheck.osgeo.org

pycsw is an OGC CSW server implementation written in Python and is an official OSGeo Project. pycsw implements clause 10 HTTP protocol binding - Catalogue Services for the Web, CSW of the OpenGIS Catalogue Service Implementation Specification, version 3.0.0 and 2.0.2. pycsw allows for the publishing and discovery of geospatial metadata, providing a standards-based metadata and catalogue component of spatial data infrastructures. The project is certified OGC Compliant, and is an OGC Reference Implementation.

The project currently powers numerous high profile catalogues such as IOOS, NGDS, NOAA, US Department of State, US Department of Interior, geodata.gov.gr, Met Norway and WMO WOUDC. This session starts with a status report of the project, followed by an open question answer session to give a chance to users to interact with members of the pycsw project team. This session will cover how the project PSC operates, the current project roadmap, and recent enhancements focused on ESA's EOEPCA, Open Science Data Catalogue and OGC API - Records.

pygeoapi is an OGC API Reference Implementation. Implemented in Python, pygeoapi supports numerous OGC APIs via a core agnostic API, different web frameworks (Flask, Starlette, Django) and a fully integrated OpenAPI capability. Lightweight, easy to deploy and cloud-ready, pygeoapi's architecture facilitates publishing datasets and processes from multiple sources. The project also provides an extensible plugin framework, enabling developers to implement custom data adapters, filters and processes to meet their specific requirements and workflows. pygeoapi also supports the STAC specification in support of static data publishing.

pygeoapi has a significant install base around the world, with numerous projects in academia, government and industry deployments. The project is also an OGC API Reference Implementation, lowering the barrier to publishing geospatial data for all users.

This presentation will provide an update on the current status, latest developments in the project, including new core features and plugins. In addition, the presentation will highlight key projects using pygeoapi for geospatial data discovery, access and visualization.

The World Meteorological Organization (WMO) Information System (WIS) is a coordinated global infrastructure responsible for telecommunications and data management functions and is owned and operated by WMO Members.

WIS 2.0 will provide users with seamless access to diverse information from a wide range of sources and will enable weather, water and climate information to be related to socioeconomic and other contexts. Through an open ecosystem of tools, applications and services, WIS 2.0 will allow all information providers to manage, publish and share their data, products and services, and will allow all users to develop value-added services and new products.

The WIS 2.0 principles highlight and promote the value of standards, interoperability and the Web/mass market. This will extend the reach of weather/climate/water data for a number of societal benefits.

WIS 2.0 is being designed to have a low barrier to entry for data providers. This will also result in enabling infrastructure and provide great benefit for less developed countries (LDCs). There is a strong motivation to provide LDCs easy to use tools and sustainable workflow for data exchange to 1./ ease the burden of exchanging data 2./ continue to provide valuable weather/climate/water data in WIS 2.0 over time.

The WIS 2.0 in a box (wis2box) project enables LDCs free and open source onboarding technology to integrate their data holdings and publish them to WIS 2.0 in a manner consistent with the architecture for plug and play capability, supporting discovery, access and visualization.

This presentation will provide an overview of the project and current capabilities highlighting the use of numerous FOSS4G tools and PubSub driven implementation of OGC API standards.

The Open Geospatial Consortium API family of standards (OGC API) are being developed to make it easy for anyone to provide geospatial data to the web, and are the next generation of geospatial web API standards designed with resource-oriented architecture, RESTful principles and OpenAPI. In addition, OGC APIs are being built for cloud capability and agility.

pygeoapi is a Python server implementation of the OGC API suite of standards. The project emerged as part of the OGC API efforts started in 2018 and provides the capability for organizations to deploy OGC API endpoints using OpenAPI, GeoJSON, and HTML. pygeoapi is open source and released under an MIT license. pygeoapi is built on an extensible plugin framework in support of clean, adaptive data integration (called "providers'').
Elasticsearch (ES) is a search engine based on the Lucene library. It provides a distributed, multitenant-capable full-text search engine with an HTTP web interface and schema-free JSON documents.
The Elasticsearch data provider for pygeoapi is one of the most complete in terms of functionalities and it also includes CQL support with the CQL-JSON dialect, which allows you to take extra advantage of the ES backend.

This presentation will provide an overview of OGC APIs, pygeoapi and Elasticsearch integration, and demonstrate usage in a real-world data dissemination environment.

The Open Geospatial Consortium (OGC) and the Open Source Geospatial Foundation (OSGeo) have a long and natural tradition of collaborating. In 2022, the Memorandum of Understanding between both organizations was updated - to pay tribute to ongoing and future activities.

In the initial MoU (2008), OGC and OSGeo agreed to work closely to coordinate with each other’s memberships regarding new standards developments and standards changes that may be required as a result of open source programs. Another important aspect of the relationship is to keep each other well informed of the respective activities and directions. Both aspects have proven to be of great importance. One goal was and is to coordinate activities in such a way as to maximize the achievement of both organizations’ mission and goals.
That includes to identify open source technologies that can be used as reference implementations for and validate compliance tests developed for OGC adopted standards.
Since the first MOU, there has been an increase in OGC on developer focus and engagement of software communities and activities. Increased collaboration has also occured by way of the OGC API code sprints. In addition, key opportunities for cross pollination have evolved given shared missions (FAIR data) and the viewpoint that FOSS4G software is beneficial for all software.

The development of the OGC API suite of standards is an excellent example on how the MoU works in practical terms. The OGC APIs are a family of Web APIs that have been created as extensible specifications designed as modular building blocks that enable access to spatial data that can be used in data APIs. These revolutionary APIs make location information more accessible than ever before through the use of RESTful principles, and the OpenAPI specification for describing interfaces. OGC APIs have been tested in close collaboration with the global developer and end user communities through hackathons, sprints, and workshops to provide a modern solution to tomorrow’s location sharing issues. For example, the 2021 Joint Code Sprint organized by OGC, OSGeo and the Apache Software Foundation (ASF) included open source implementations of OGC APIs - and became a standing sprint activity that was repeated in 2022.

This presentation provides a deeper dive into the new Memorandum of Understanding and how both open standards and free and open source software can benefit from one another.