Andrew Olsen
Andrew Olsen
There's no indication when sno push, pull, or clone might be done. Underlying git commands support this so a fix will be reasonably straightforward.
Originally, there were three types of change in a diff: - inserts - updates - deletes However, as Kart gets more complex, it is possible for the user to put...
... during working copy checkout of raster datasets. Adds a utility method to check if an environment variable is turned off since bool(os.environ.get(key)) won't work anymore. ## Checklist: - [x]...
Adding url redirect rules to the linked-storage.json meta item causes those redirect rules to be honoured when fetching tiles for any commit that includes the new linked-storage.json. However, this won't...
A yet-to-be-fully-designed flow that creates a tile-based Kart dataset that is "backed" in some sense by the original data on S3 (or similar), rather than being necessarily stored in the...
Since Kart 0.12, Kart repositories are not homogenous: there is now more than one type of dataset. Supported datasets are table (v3), point cloud (v1) and raster (v1). The command...
**To Reproduce** kart import some-laz-file-that-doesnt-have-a-crs.laz (You can agree to constrain-to-COPC or not - makes no difference.) **Expected behaviour** Should import the tiles, even with no CRS. **Output** A stacktrace, ending...
We use git to update an index for the "workdir" - the filesystem working copy. Git is good at detecting changes to files in an efficient way, which is what...
Right now, numerics are imported / committed as numerics along with any extra precision / scale information from the DB, and without that information if it is not present. Here...
On Windows - and potentially other platforms, depending on the filesystem - copy-on-write is not supported. Currently, Kart simply does a regular copy, which means all LFS files that are...