Skip to content

Rfc7:Implement OpenLayers3

Meine Toonen edited this page Jan 12, 2017 · 3 revisions

Overview

In this change, a new version of OpenLayers (version 3.X) will be implemented. This functionality will not replace the openlayers "kaartmotor", but work alongside it.
With these changes, we aim to make Flamingo more future proof, as OpenLayer 3 is more mobile friendly, scaleable and built from the ground up with performance in mind.

Functional changes

The new kaartmotor will implement all the existing superclasses defined in the current webapp. After implementation it will be possible to drag a block to the map region, after which flamingo will seamlessly switch to the openlayers 3 version of the kaartmotor.

Technical changes

The changes needed for the completion of this functionality are described here.

Affected modules

The modules which are affected by these changes are split in the viewer and viewer-admin

Viewer

This change will largely be an addition of code to the codebase, and not so much change the existing code.

That said, it's very well possible that the radical changes OpenLayers 3 bring in their architecture will require changes in our own framework. This will be mitigated through thorough research in the areas of event handling, structure of the new API and the existing architecture.

Viewer-admin

No changes are nessecary here.

Backwards compatibility

We foresee no incompatibility with older version. All the old configurations will be kept and remain functional. It does provide us with a good moment to remove the deprecated Flash components. Thoughts?

Reference to code

OpenLayers documentation
http://openlayers.org/en/latest/apidoc/
http://openlayers.org/en/latest/examples/

Projects in which we have used OpenLayers 3
https://github.com/B3Partners/verkeerbeheer-kaart
https://github.com/B3Partners/kodisionmap
https://github.com/B3Partners/playmapping

Voting history

Clone this wiki locally