Neat!
Does this improve Git's support for large binaries generally, or is it necessary to have introspection into any filetype you want to support?
Is there good interoperability with existing Git repos?
Does this improve Git's support for large binaries generally, or is it necessary to have introspection into any filetype you want to support?
Is there good interoperability with existing Git repos?
> Because Kart uses Git for data transfer and storage, you can host a Kart repository anywhere you can host a Git repository - for example, GitHub, Bitbucket...
ref: https://docs.kartproject.org/en/latest/pages/basic_usage_tut...
Kart serializes vector/tablular data into datasets in the repository, and manages the process of writing them out to useful working copies (GeoPackages, or into databases).
For large binaries - rasters and pointclouds - we're using LFS. We include some additional spaital information into pointer files to enable some very useful GIS functionality, like spatially filtered clones (this works for vector data too).
No, this still uses LFS for larger binary formats (ie raster or point cloud datasets)