You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the merge step, executed with merge_staged_vector_tiles.py, most tiles in worker nodes succeed in undergoing one of the following:
being copied over to the head node (if the tile does not yet exist in the head node at all)
being merged (deduplicated) into the tile that already exists in the head node (because the tile existed in both nodes, but the files are different)
being skipped, so nothing is done (because the tile exists in both nodes, and the files are the same)
Some errors occur when merging:
The errors imply that either one of the matching tiles is corrupted in general, or that more specifically the geometry at index 0 is invalid due to a self-intersection.
The text was updated successfully, but these errors were encountered:
During the merge step, executed with
merge_staged_vector_tiles.py
, most tiles in worker nodes succeed in undergoing one of the following:Some errors occur when merging:
The errors imply that either one of the matching tiles is corrupted in general, or that more specifically the geometry at index 0 is invalid due to a self-intersection.
The text was updated successfully, but these errors were encountered: