Migrate to maplibre-gl-js?

[pathmapper]

https://github.com/maplibre/maplibre-gl-js#migrating-from-mapbox-gl

from lb-lewisham#1 (comment)

Interestingly, this particular implementation is in a position to make use of maplibre-gl, for both map tiles and geocoder. Would this be of interest for wider applications of quattromap - if so I'd be happy to investigate further for the project.

This thread is for posting any findings regarding a possible migration to https://github.com/maplibre/maplibre-gl-js.

Currently we are using the following plugins:

• https://github.com/mapbox/mapbox-gl-draw
• https://github.com/mapbox/mapbox-gl-geocoder
• https://github.com/mapbox/mapbox-gl-sync-move

Are these plugins working out-of-the-box with maplibre-gl-js?

For the geocoder we are using currently the Mapbox geocoding service. If we would switch to https://github.com/maplibre/maplibre-gl-geocoder, which geocoding services could be used?

/cc @joe-liad

[pathmapper]

mapbox-gl version 1.x. -> backward compatible to mapbox-gl

maplibre-gl version 2 -> non-backward

Would anything blocking us from migrating to v2?

[birkskyum]

The mapbox-gl-sync-move plugin is compatible with maplibre

• Add sync-move example maplibre/maplibre-gl-js#4706

The maplibre-gl-geocoder plugin is flexible, and not tied to a single service. Examples are:

• AWS Location Service - https://www.npmjs.com/package/@aws/amazon-location-for-maplibre-gl-geocoder
• Nominatim - https://maplibre.org/maplibre-gl-js/docs/examples/geocoder/
• MapTiler Geocoding Control - https://docs.maptiler.com/react/maplibre-gl-js/geocoding-control/