Looked at their source code out of curiosity. They use Elasticsearch as a geo backend, tile server that renders PNG images server side for each map tile request.
- low zoom -> server aggregated grid
- high zoom -> switcher to point tiles
browser just displays images, there is no work to do on client side..
I didn't know how old this actually is. I was surprised to learn Marcus Aurelius wrote his Meditations as a private journal... never meant to be published.
had the same question and after reading about it, I found there are multiple layers on each other.
Existing plans are built to run 40-60 years.. retiring creates "stranded assets". pension funds fight hard to avoid that.
The renewable projects that wait for permits exceed total existing capacity.. the bottleneck is not tech, but locality.
30 years and nobody (pharma, govts, etc.) have not found it worth to study this properly.
If it worked, would not at least some researched pick this up?
- low zoom -> server aggregated grid
- high zoom -> switcher to point tiles
browser just displays images, there is no work to do on client side..
I generated a visual schematic how these kind of systems work: https://vectree.io/c/server-side-geo-tile-rendering-elastics...