Cloud Native file formats

[imakihi]

Hi there!
I have been converting all kind of vector and raster data to the cloud native format such as GeoParquet and COG. I also want to convert LAS files to COPC too. So it would be super cool if Terria can support GeoParquet and COPC. COG support looks closet to the final stage so I am super exceited about that. Especially GeoParquet support would be nice.

[nf-s]

Hi @imakihi

I agree, I would also love to add Zarr and FlatGeobuff support.
Currently, we mostly only get demand to add COG support - but I'm sure this will change as more open-data is published in cloud-native file formats.

[imakihi]

@nf-s Thank you for your comment.

Zarr sounds nice too! I am sure you guys are super busy but cloud native formats must be the way for any geospatial web apps in the future.
https://beta.source.coop/repositories/streambatch/worldcereal/description/

Than you for yoru hard work!!

[nf-s]

Thanks @imakihi!

It is great to see more data being published to Source Cooperative - Radiant Earth is an amazing organisation!

We already support pmtiles - so we should try and add one of the pmtiles datasets - https://beta.source.coop/repositories/?tags=pmtiles

[imakihi]

@nf-s
How can I add a pmtile dataset to a TerriaMap? I didn't know that I can use it. That would be super cool. Can you tell me how to do it when you have a chance??
Thanks!!

[techmavengeospatial]

Probably the easiest way to support many new formats is to use QGIS WASM Web Assembly https://github.com/qgis/qgis-js and render them as Raster Tiles for Terriajs and have functions for feature info requests. To do this would need to automate QGIS Project creation.
This would be client-side javascript and not persistent.

There are other WASM Packages like SPL.jS Spatialite, GDAL3.JS, GeoParquet WASM
Most cloud native formats still work better with server-side code than just in browser.

there is also DUCKDB WASM the spatial extension is not supported yet but they are working on supporting spatial extension in future versions of web assembly version

DUCKDB Spatial has access to import and export any OGR format

[nf-s]

Wow qgis-js is very cool - but I don't think we will be able to use it due to GPL license.

I think the bottleneck with these formats for TerriaJS will be rendering - especially with tabular/vector sources. We probably have to look into a more "GPU native" approach - rather than decoding these formats and using TerriaJS existing tabular/vector engine

[TimeScience]

FYI, TERN is publishing all of their point clouds in COPC, so that's another vote for COPC support