qgis / QGIS

QGIS is a free, open source, cross platform (lin/win/mac) geographical information system (GIS)
https://qgis.org
GNU General Public License v2.0
10.04k stars 2.92k forks source link

Untwine fails if path contains Swedish characters #57913

Open mnoreke opened 1 week ago

mnoreke commented 1 week ago

What is the bug or the crash?

When importing LAZ files into a point cloud, the import fails with an error of: Layer 19A004_616_42_7575: Untwine error: create_directory: The system cannot find the path specified.: "D:/QGIS/SjöboPointCloud/61_4/19A004_616_42_7575.copc.laz_tmp"

Changing "Sjöbo" to "Sjobo" resolves this issue.

Steps to reproduce the issue

Add layer of type PointCloud Select a file with "ö" in the file name Add layer

Versions

QGIS version 3.36.3-Maidenhead QGIS code revision 2df96554 Qt version 5.15.13 Python version 3.12.3 GDAL/OGR version 3.9.0 PROJ version 9.4.0 EPSG Registry database version v11.004 (2024-02-24) GEOS version 3.12.1-CAPI-1.18.1 SQLite version 3.45.1 PDAL version 2.6.3 PostgreSQL client version 16.2 SpatiaLite version 5.1.0 QWT version 6.2.0 QScintilla2 version 2.14.1 OS version Windows 10 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

New profile

Additional context

While I haven't tried a new profile, I have no idea how to create a custom one to start with. It's only day 2 of QGIS. :)

nicogodet commented 1 week ago

Weird, it should have been fixed long time ago... See https://github.com/qgis/QGIS/issues/41833

agiudiceandrea commented 1 week ago

Confirmed using both QGIS 3.38.0 and QGIS 3.34.8 on Windows 10 (OSGeo4W). For example, with a tèst.laz file the following error is displayed: CRITICAL Layer tèst : Untwine error: Unable to open stream for 'C:/Users/Andrea/Downloads/tèst.laz' with error 'No error'

mnoreke commented 1 week ago

Weird, it should have been fixed long time ago... See #41833

I found that as I was trying to figure out what was wrong. For some reason it didn't occur to me to link that issue, but I will blame my sleepy head at the time. :)