Thanks! Unfortunately further development of that project went closed-source, but that code should be instructive as-is. Client side GPU-based raster processing is going to be released soon as part of our [0] SaaS product. Demo here [1]
Unfortunately, closed source seems to be the way that the mapping gl community is going right now.
I'm doing open data stuff, and the general push is definitely to open data/open source as a general principle. And also as an important consideration, when we deliver a project, with open source we at least know that the service isn't just going to go away if it gets bought by google/apple or just dies 6 months down the road. We also tend to shy away from systems that are on the Oracle "Call Us" for pricing model.
Well this "extension" is closed source, but at the core we use deck.gl [0]. deck.gl is under open governance [1] inside the Linux Foundation/Urban Computing Foundation, so no contributor can take the project closed source.
No, this is a common misconception about deck.gl. deck.gl is completely independent from other frameworks, however deck.gl is more geared towards data visualization, so it's commonly paired with other frameworks that focus on a vector basemap.
There are examples [0] of pairing deck.gl with either Mapbox GL JS or Google Maps. It's also easy to use deck.gl with the open source Mapbox GL JS port [1]. Also if you're ok with a bitmap basemap, you can just render OSM tiles with deck.gl directly [2].
(Also I guess good to disclaim that I'm a maintainer of deck.gl )
