Open
Description
What is the bug or the crash?
When a VPC is given as input for the Create COPC tool from the Processing Toolbox, it gives the following error in the log:
QGIS version: 3.40.6-Bratislava
QGIS code revision: 5d7f6a3e26
Qt version: 5.15.13
Python version: 3.12.10
GDAL version: 3.10.3
GEOS version: 3.13.1-CAPI-1.19.2
PROJ version: Rel. 9.6.0, March 15th, 2025
PDAL version: 2.8.3 (git-version: 56e405)
Algorithm started at: 2025-05-10T13:33:35
Algorithm 'Create COPC' starting…
Input parameters:
{ 'LAYERS' : ['vpc://E:/Virtual_Point_Cloud/WinkelcentrumWoensel_Eindhoven_Clipped.vpc'], 'OUTPUT' : 'E:\\Virtual_Point_Cloud\\' }
Processing layer 1/1: WinkelcentrumWoensel_Eindhoven_Clipped
Failed to index file E:\Virtual_Point_Cloud\/WinkelcentrumWoensel_Eindhoven_Clipped.copc.laz: Unable to convert scaled value (3868717790) to int32 for dimension 'Y' when writing LAS/LAZ file.
Execution completed in 18.16 seconds
Results:
OUTPUT_LAYERS: E:\Virtual_Point_Cloud\/WinkelcentrumWoensel_Eindhoven_Clipped.copc.laz
Loading resulting layers
Algorithm 'Create COPC' finished
This used to work. I had it included in my course at Udemy. Now more and more participants face this error, which I was also able to reproduce.
Steps to reproduce the issue
- Go to the Processing Toolbox.
- Click on the Create COPC tool.
- Choose a VPC layer as input.
- Choose a directory for the output
Versions
QGIS version | 3.40.6-Bratislava |
QGIS code revision | 5d7f6a3e26 |
Libraries | |
Qt version | 5.15.13 |
Python version | 3.12.10 |
GDAL version | 3.10.3 |
PROJ version | 9.6.0 |
EPSG Registry database version | v12.004 (2025-03-02) |
GEOS version | 3.13.1-CAPI-1.19.2 |
SQLite version | 3.46.1 |
PDAL version | 2.8.3 |
PostgreSQL client version | unknown |
SpatiaLite version | 5.1.0 |
QWT version | 6.3.0 |
QScintilla2 version | 2.14.1 |
OS version | Windows 11 Version 2009 |
Active Python plugins | |
db_manager | 0.1.20 |
grassprovider | 2.12.99 |
MetaSearch | 0.3.6 |
processing | 2.12.99 |
Supported QGIS version
- I'm running a supported QGIS version according to the roadmap.
New profile
- I tried with a new QGIS profile
Additional context
The first question about this error came in November on my course at Udemy.