[openstreetmap/openstreetmap-website] Support client-side rendered featured layers (#2686)

[Paul Norman]

> @pnorman could this issue be re-titled "Migrate from Leaflet to maplibre-gl-js"?

There's an implementation question there that the maintainers would need to weigh in on.

One implementation option is to completely replace Leaflet with Maplibre GL JS. This would
- presumably speed up the data layer
- minimize total data transferred if someone uses both a raster layer and a vector layer
- minimize code complexity
- require WebGL for most of the site to work
- lock us in to only client-side rendering that Maplibre GL JS supports

The other option is to use Leaflet for raster layers, and only use Maplibre GL JS for vector layers. This would
- require data layer implementations for Leaflet and Maplibre GL JS
- minimize time to map load for raster layers because Leaflet is smaller
- keep the site working for users without WebGL
- keep the option open for different client-side rendering

My preference is for the first option, mainly for code complexity reasons. The latter would require our leaflet integration, a maplibre integration, and logic to switch between them. But making this decision isn't my call, it's a maintainer decision.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/2686#issuecomment-1198564662
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/issues/2686/1198564662 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20220728/3bf4d0e5/attachment-0001.htm>