What is the bug or the crash?
In the "Build virtual point cloud (VPC)" window, when opening the dialog to select the output filename, the dialog automatically adds a .las extension when a .vpc extension would be expected.
Even so, the actual output file appears to get written with a .vpc extension rather than the .las that results from the dialog.
Steps to reproduce the issue
- In the Processing Toolbox, open "Point Cloud Data Management" > "Build virtual point cloud (VPC)"
- By the field "Virtual point cloud", click "..." and enter some filename in the dialog
- The field "Virtual point cloud" now contains a path ending with
.las
Versions
| QGIS version | 3.43.0-Master |
| QGIS code revision | 1896cf2247d |
| |
| Libraries |
| Qt version | 5.15.13 |
| Python version | 3.12.3 |
| GDAL version | 3.9.3 |
| PROJ version | 9.4.1 |
| EPSG Registry database version | v11.006 (2024-03-13) |
| GEOS version | 3.12.2-CAPI-1.18.2 |
| SQLite version | 3.45.1 |
| PDAL version | 2.6.2 |
| PostgreSQL client version | 16.8 |
| SpatiaLite version | 5.1.0 |
| QWT version | 6.1.4 |
| QScintilla2 version | 2.14.1 |
| OS version | Ubuntu 24.04.2 LTS |
| This copy of QGIS writes debugging output. |
| |
| Active Python plugins |
| Dataforsyningen | 0.7 |
| processing | 2.12.99 |
| db_manager | 0.1.20 |
| MetaSearch | 0.3.6 |
| grassprovider | 2.12.99 |
Supported QGIS version
New profile
Additional context
No response
What is the bug or the crash?
In the "Build virtual point cloud (VPC)" window, when opening the dialog to select the output filename, the dialog automatically adds a
.lasextension when a.vpcextension would be expected.Even so, the actual output file appears to get written with a
.vpcextension rather than the.lasthat results from the dialog.Steps to reproduce the issue
.lasVersions
Supported QGIS version
New profile
Additional context
No response