v0.12.0

0.12.0

Major changes

• First and foremost: point cloud datasets! Kart now supports point cloud datasets which track changes to a set of LAS files. This required the addition of a file-system working copy (as opposed to the existing database working copy types), and integrating Git LFS to store the large files. To get started with point cloud datasets, see
  Point Cloud Datasets #565

Other changes

• Install tab completion using kart install tab-completion instead of kart config --install-tab-completion. #701
• "Primary key conflicts" - conflicts caused by reusing a primary key which is already assigned to a feature outside the spatial filter - are renamed to "spatial filter conflicts" for future proofing with other dataset types. Consequently, commit option --allow-pk-conflicts is renamed to --allow-spatial-filter-conflicts.
• Support shell detection for tab completion installation when running in helper mode. #704
• Bugfix: directing geojson diff output to the console didn't work in a multi-dataset repo, even if only one dataset had changed. #702
• Improve argument parsing for kart diff and kart show. #706
• Bugfix: don't allow kart merge to fast-forward if the user specifies a merge message. #705
• diff, show, create-patch and apply now handle attached files (as could already be created using kart commit-files) #583
• metadata.xml is now consistently treated as an attached file, rather than as a hidden "meta item". #583
• apply and meta set now support --amend to amend an existing commit
• Bugfix: don't allow kart diff to diff to/from HEAD if HEAD does not yet point to a commit.
• Improved progress reporting during working-copy checkout. #738
• Support for changing the primary key column of an existing dataset. #238
• Help for the user get the working copy back into a valid state if a crash or similar causes it to become out of sync with the Kart repo. #751
• Enable the background CLI helper on Linux & macOS in CI builds. The helper improves CLI performance significantly. #776

New Contributors

• @olegsson made their first contribution in #709 -
  Use pyreflink to take advantage of copy-on-write capable filesystem when creating the working copy.

Compatibility

Point cloud datasets created using Kart 0.12 and later won't be visible when using earlier versions of Kart, but they are still present in the repository. Upgrading to Kart 0.12 is strongly recommended for anyone accessing repositories which contain point cloud datasets - in fact upgrading to 0.12 is generally recommended, it is easier to install 0.12 than to check what each repository contains.