This is for both geoparquet and pmtiles files.
I think if we are sure we got the geoparquet conversion right.. we should start dropping the .geojsonl.7z files( this involves updating the links in releases as well ), so, no need to worry about them.
Migration Pros and Cons :
Pros: no more bespoke partitioning scheme for geoparquet as we can have folders.. We can move to Hive style or Iceberg style partitioning( I prefer Iceberg as there is a external metadata file which can be used to automatically pick the relevant parquet files for a given spatial query in duckdb itself ).
Cons: Currently hosting is free( in fact the whole project is running on free tier no longer the case ).. might need to start a github sponsors link.
Even though Cloudflare R2 does not have any practical limits on individual file sizes.. if we want to take advantage of the caching, we may need to partition the files to 512 MB chunks.
This is for both geoparquet and pmtiles files.
I think if we are sure we got the geoparquet conversion right.. we should start dropping the .geojsonl.7z files( this involves updating the links in releases as well ), so, no need to worry about them.
Migration Pros and Cons :
Pros: no more bespoke partitioning scheme for geoparquet as we can have folders.. We can move to Hive style or Iceberg style partitioning( I prefer Iceberg as there is a external metadata file which can be used to automatically pick the relevant parquet files for a given spatial query in duckdb itself ).
Cons: Currently hosting is free(
in fact the whole project is running on free tierno longer the case ).. might need to start a github sponsors link.Even though Cloudflare R2 does not have any practical limits on individual file sizes.. if we want to take advantage of the caching, we may need to partition the files to 512 MB chunks.