FOSS4G 2022 general tracks

After 2019 and 2021 we also want to give a status report of the GeoStyler [1] project on this years FOSS4G. GeoStyler is an OSGeo community project [2] and received a lot of new features and changes in the past months.

GeoStyler provides a set of parser libraries that allow the conversion between different styling formats. On top of the core functionality GeoStyler provides an user interface library that helps to integrate GeoStyler into your own web application. Using these components, GeoStyler can be used for example to create a WYSIWYG style editor. The project also maintains a GeoServer-plugin [3], which includes styling UI-components into GeoServer.
Two more tools from the GeoStyler universe should be mentioned: A commandline interface (CLI) and a REST interface. The CLI provides a tool for server-side style conversion for an arbitrary number of style files – completely automated. The REST interface can be used to create web services which do the conversion between formats. With these tools, it is possible to convert a huge amount of QGIS styles to SLD, or Mapfile or any other supported file based styling format and vice versa.
GeoStyler is based on a plugin concept, so the UI works with any of the supported parsers and can thereby be used for projects that use SLD, OpenLayers, QML, etc. Currently, GeoStyler supports the styling formats OGC SLD, OpenLayers Styles, Mapfiles, QML, Mapbox and also – for assistence when styling by attributes – the geodata formats GeoJSON, OGC WFS and Shapefile. Common Query Language (CQL) for filtering is understood as well as filter encoding (OGC FE).
There are a number of new features such as a card layout, enhanced support of expressions, filter UI enhancements as well as various documentation updates and translations planned for this year and we expect all or most to be realized when FOSS4G 2022 takes place.
With this talk, we want to present the current project status and show how GeoStyler evolved since the last talk. In order to show a real-life example, we will present the results of a project, where the task was to convert UMN Mapserver based styles to QGIS using GeoStyler.

[1] https://geostyler.org/
[2] https://www.osgeo.org/projects/geostyler/
[3] https://docs.geoserver.org/latest/en/user/community/geostyler/index.html

MapProxy is a tile server for geospatial data that is capable to cache, accelerate and transform data from existing map services and serve them for various clients.
MapProxy is a tile cache, but also offers many more features like full support for WMS, re-projection of tiled map services and much more. MapProxy is Open Source (Apache Software License 2.0), is easy to install and to configure and runs on various OS.
Thus, for many of our customers MapProxy is an essential part of their geodata-infrastructure (GDI), but the simple possibility to ask on a mailing list is often not enough, when they want to bring Mapproxy into production. Guidelines of IT departments often require a service contract, looking at proprietary software such a contract often is a binding part of the user agreement. But what about Open Source Software?
We as a service provider offer professional support and also service contracts for MapProxy (and other OSS software) and thus, we help customers to bring Open Source into production by filling the gap of missing warranty. In the talk we would like to discuss the various business models that we developed in the past, but we also want to show why MapProxy is an important part of their GDI for many customers.

[1] https://mapproxy.org/