Sponsoring Update OpenLayers in Mapbender

We need your help!

In our OSGeo project Mapbender, the coming months will contain some major improvements: The map framework will be upgraded to the latest version of OpenLayers. This is the biggest change to the software that has been made in recent years!

The scheduled customizations will include a rewrite of all elements of Mapbender, from key components such as the map itself to the legend, the layer tree, the FeatureInfo, the Print element, and so on. For details of the introducing of the new version of OpenLayers are public at our GitHub code and the Github ticket management.

For our Mapbender-Team this milestone "OpenLayers" has the highest priority and we have already planned extensive human and financial resources to achieve this milestone. Nevertheless, we need your support to achieve the goal.

With this sponsoring program, anyone interested can participate in the further development of the project. Every contribution is welcome! Starting from a contribution of 1.000 Euro, we publish here the name and also the logo of the supporter on this website.

How can you donate?

The work of the Mapbender team can be supported by bank transfer or via PayPal:

Bank Transfer:

VR-Bank Bonn eG
WhereGroup GmbH & Co. KG
IBAN: DE73 3816 0220 6114 2230 16
Verwendungszweck: Mapbender Sponsoring


You can donate via PayPal with your personal PayPal account.


We thank out sponsors and donors who support our OpenLayers-project and who enable us to achieve this important development-step with their financial support.

Our special thank you goes to the following companies and municipalities:


Deutsche Bahn
Stomnetz Hamburg
Stadt Gütersloh
Stadt Troisdorf
WhereGroup GmbH & Co. KG


The current status of our Sponsoring program shows, that a third of the planned and organized days are sponsored and financed yet.

Stand Sponsoring



Testserver and Testing-applications

Our testserver is available at: https://test.mapbender.org/ol4/. We will continue to update the several example-applications. A basic application is the simple map: https://test.mapbender.org/ol4/application/map_naked.

The example-applications are written in YAML-files and are available at Github: https://github.com/mapbender/mb-test-applications. From a technical view, we simple unzip the files into the "mapbender/application/app/config/applications" directory.



Our goals

Our goal is not to change the functionality of the individual Mapbender elements. Of course - if necessary - corrections and cleanups are made; however, the basic structure of the software will remain. Upon completion of the development work, it will be possible to migrate existing OpenLayers 2 applications to the new OpenLayers release.

The integration of the new OpenLayers version in Mapbender promises advantages such as the easier handling of mobile applications, the support of higher resolutions and the better compatibility with the printed image. Also future drafts such as the 3D implementation and the support of other file formats are feasible. In addition, working with self-drawn complex geometries is much smoother.

Moreover, given that OpenLayers 2 will not be developed further in the future, it is necessary to update Mapbender just to avoid security risks.

In the future, we will provide here small articles about the work done.



Blog & Status Report

The following information shall give you an overview on the actual development.

Preparation before the sprint (week 24)

3 Members of Mapbender team prepared the sprint and worked on the tasks, they provided a concept, created tickets and defined the workflow and priority.

What todo: All elements have to be analysed. We made a checklist which the developer has to use to analyse each element and find out how OpenLayers is involved.

How to proceed: We setup a catalog of rules to follow.

We provide two weeks where the developer can concentrate on the OpenLayers topic and stay in contact via chat and video conference. Twice a day we come together for a meeting to give a status report, answer questions and define the next steps.


Day 1: 18.06.2018

The whole team got an introduction in the goals and how to work on it. All elements were scanned and the check were made. You find the status and checklist in several tickets. https://github.com/mapbender/mapbender/projects/3

At the same time backend functions were defined to communicate with OpenLayers 4.

Demo applications were prepared. We defined new applications with only few functionality to run and test them separately.

- Integration of OpenLayers 4 specific CSS: for the different map engine (OpenLayers 2 & OpenLayers 4) you can use different JavaScript and CSS

- AssetFactory & ApplicationAssetCache Classes were defined

- Definition of the Mapbender.Model OpenLayer 4. There are some methods already but no content yet. The content will be generated tomorrow (https://github.com/mapbender/mapbender/blob/ol4/src/Mapbender/CoreBundle...) The Model will provide wrapper functions for many tasks. Like this we will provide compatibility for individual Mapbender projects and prepare the update to OpenLayers 4.

We got along quite well at the first day! Like expected some elements (like map, layertree, digitizer) were more complex as others and will need more refactoring. The team is high motivated and looks forward to the next day.




FOSS4G Europe 2018 Portugal 16.-21.07.2018 FOSS4G Europe Conference (Guimarães) FOSS4G 2018 Dar es Salaam, Tansania 14.-18.08.2018 FOSS4G Dar es Salaam (Tansania)

OSGeo Project

Follow us on Twitter https://twitter.com/mapbender/