@joshmoore following up from the #51 thread-- we'd like to propose a new repo. Here's the details:
This would be for a client-side typescript library to read virtualizarr stores; icechunk is the only existing store format, hence the repo name, icechunk-js. For background, Shane and I developed independent library implementations to do this; we've combined efforts and merged features from englacial/icechunk-js into this branch of the carbonplan/icechunk fork. We have a growing set of both internal and external users, multiple viewers that use this library as a dependency, and would love to find a home for the project.
We have already talked with the icechunk core devs about this project; they're working on a full WASM implementation that would provide both read and write capabilities that targets a different user community. For us and our users, want to enable just a reader, which is lighter and simpler to deploy client side, and the consensus is that this makes sense as a separate project. We're hoping that zarr-developers would be a good place to run this as a community project that isn't under carbonplan, englacial, or earthmover.
@joshmoore following up from the #51 thread-- we'd like to propose a new repo. Here's the details:
This would be for a client-side typescript library to read virtualizarr stores; icechunk is the only existing store format, hence the repo name, icechunk-js. For background, Shane and I developed independent library implementations to do this; we've combined efforts and merged features from englacial/icechunk-js into this branch of the carbonplan/icechunk fork. We have a growing set of both internal and external users, multiple viewers that use this library as a dependency, and would love to find a home for the project.
We have already talked with the icechunk core devs about this project; they're working on a full WASM implementation that would provide both read and write capabilities that targets a different user community. For us and our users, want to enable just a reader, which is lighter and simpler to deploy client side, and the consensus is that this makes sense as a separate project. We're hoping that zarr-developers would be a good place to run this as a community project that isn't under carbonplan, englacial, or earthmover.