Comparison of webmapping frameworks

[Bernd Welter]

Hello community,

This is an ongoing thread which will be updated/extended every once in a while.
Therefore I recommend that you check the posts at the end.
Be aware that this discussion isn't a proprietary thing - therefore you can also find similar generic threads on the web, e.g. on github.

in december 2014 a customer asked me which framework PTV recommends for the implementation of web based applications (incl. mapping). I therefore requested our experts to provide an overview - here it is.
(Thank you very much, Andreas!! )

I hope it helps you to decide which one of the alternatives fits you the best.
Let us know if you have experience with other options so we might learn as well.

OpenLayers

• First open source alternative to Google maps. Initially developed and provided based on openstreetmap.org
• Early version of the API (2.0) was rather complex. Since version 3.x (summer 2014) more convenient (as simple as Leaflet)
• Provides rotation of maps (e.g. for rotation into drivers direction instead of North, navigation on mobile devices)

Leaflet

• Slim alternative to open layers v2. Todays default on openstreetmap.org
• API is very simple
• Does not support map rotation
• Supports PTV vector maps (project software, not product!)

AjaxMaps

• PTV-MapWidget, also supports external datasources
• API complexity is "different" (some features are easier to use than with the alternatives, other features are more complex than with other frameworks)
• Provides rotation of maps (e.g. for rotation into drivers direction instead of North, navigation on mobile devices)
• Native integration of PTV xMap services enables AjaxMaps to provide extended functions (e.g. print mode)
• Performance of displaying several thousand client objects is much better than with Leaflet or Openlayers
• Supports PTV vector maps (project software, not product!)
• Supports integration of Leaflet instead of own engine (i.e. API and controls are same as with AjaxMaps, mapping itself is provided by Leaflet)

Decision support

• OpenLayers V2: we advise against V2.
• If you want to display simple maps with just a few objects (markers and lines) without the necessity to rotate maps: We recommend Leaflet (1. Though OpenLayers v3 is also an option, but migration from OpenLayers to AjaxMaps is not on the roadmap and therefore might raise more stress than necessary, 2. Leaflet is more robust than OpenLayers v3).
• Simple maps with rotation: OpenLayers V3.
• Complex maps with large numbers of displayed objects and print mode: Ajaxmaps (native (incl. rotation) or as Leaflet wrapper (no rotation))
• From our point of view the estimated complexity of an application is the major criteria for the decision:
  • How many objects do you want to visualize?
  • Do you need print mode?
  • Do you need map rotation?
  • Do you want to access Vectormaps (Attention: project software!)

Best regards from Germany,

Bernd

[Bernd Welter]

Hi there,

the original recommendation was state-of-the-art in 2014/2015.

With the updated perspective of 2016/2017 there is some new info available:
PTV recommends to use LEAFLET

• It is opensource
• Huge active community to improve the framework
• Very performant
• More features in comparison to AJAX Maps

Statement from our Solution Director Michael Nutto:

PTV has decided to no longer support AJAX MAPS in the context of PTV xServer 2.

And one more statement:

The usage of AJAX maps is still meaningful in your current application. Ajaxmaps 3.5.18 is the latest version (of february 2017) and we will create bugfixes in the same way as we do it with xMap 1.x.

Best regards Bernd

[Bernd Welter]

And here is the 2019 version: in fact the recommendation is LEAFLET.
Especially since the interface of the xMap2 has now a REST API which simplifies the usage once more.

Check the chapter Display a Basic Interactive Map in the xServer 2 Online Docu!

Best regards,
Bernd

[Bernd Welter]

In the context of 2023 we recommend to consider the following frameworks for an evaluation:

Framework	Leaflet	MapLibre
License	BSD 2-clause "Simplified"	BSD 3-Clause
Base Technology	HTML5/Raster Tiles	WebGL/Vector Tiles
Footprint	Very lightweight	Requires WebGL
Main Usecase	General purpose "slippy map"	Data visualization
Learning Curve	Simple basic API + many plugins	Requires additional frameworks (KeplerGL/DeckGL)
Handling	Only fixed zoom levels	rotation/tilting/factional zoom
Interop	leaflet-maplibre-gl	raster-tile-source
Example	4ua173rd	o5r0ujwq