not storing metadata for tiles without hash matched #278
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.
I found 2 main issues:
The success of the LAZ files was set to True even when we had the
force_download
option - which was the case in this runWhen storing the PDAL output to the metadata_ahn* tables, there was no filter for the unsuccessful LAZ tiles.
I added a filter to skip the metadata storage if the download or the hashes have failed.
This is what happened in this release's run:
Hashes are failing, the last download object gets a success=False and an empty path (.) but this is information is not used anywhere for filtering.
Then the lazdownload object is fed into pdal and of course there is no output:
The metadata is still stored in the metadata_table. Example from the metadata_ahn4 table (I have cleaned it now):
Specifically, these tiles had failed hashes:
AHN3 = 25gn2, 25hz2, 26cz1
AHN4 = 06hn2, 11fn2, 11fz2
I suggest we skip them and we ask Adriaan about it (why are the hashes diverging?)
For AHN5 the issue was different and it had to do with what I did in my previous commits.
I suggest we make a fresh download for all AHN5