Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[FR] Client side geometry generation for known indexes (H3, S2, etc.) #218

Open
AbelVM opened this issue Jun 28, 2024 · 0 comments
Open

Comments

@AbelVM
Copy link

AbelVM commented Jun 28, 2024

It's quite common nowadays to have raster-like data (continuous coverage) stored as key-value tuplas using H3 or S2, without geometry, so the stored data size is minimized.

It would be great to add client-side geometry generation to those spatial indexes so the tile's payload is stripped to its bones, in those cases it's possible. Something like Unfolded' hex tiles

For the last 2 years, I've been using a custom protocol in production to achieve this, but I'm sure that this feature would be welcome as native in this upcoming format

louwers added a commit that referenced this issue Feb 7, 2025
* Remove render-link.html

* Revert "Remove render-link.html"

This reverts commit fc6693bad881962895f44d19097f2e451d08520f.

* Remove newline at end of file

* Revert "Remove newline at end of file"

This reverts commit bcc039a46d3cb3a0c17d52321a383d71106afef2.

* Delete render-link.html again

* Revert "Delete render-link.html again"

This reverts commit f60f0a5572bd91e16befa3c3f28c48e7f6cb9081.

* Add back render-link.html

* Update .prettierignore
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant