Modified point-cloud-import --replace-existing to reuse tiles
#783
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Modified `point-cloud-import --replace-existing` to reuse previously imported tiles, rather than reimport them, if tiles that have already been imported are imported again - potentially saving time and disk space. This is particularly relevant when importing with convert-to-copc, since converting to COPC can make the hash differ each time and so cause the same points to be stored more than once in equivalent but not identical files, at different hashes. Note that `point-cloud-import --update-existing` already had this optimization.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Modified
point-cloud-import --replace-existingto reuse previously imported tiles, rather than reimport them, if tiles that have already been imported are imported again - potentially saving time and disk space.This is particularly relevant when importing with convert-to-copc, since converting to COPC can make the hash differ each time and so cause the same points to be stored more than once in equivalent but not identical files, at different hashes.
Note that
point-cloud-import --update-existingalready had this optimization.Checklist: