-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to read MBTiles in paths containing multibytes #56023
Comments
@kohei-hasegawa thanks for reporting. Does the issue only occur trying to import an MBTiles layer file from a path containing Japanese characters or also trying to import any other layer file from a path containing Japanese characters? |
The same problem exists no matter which Japanese language is used. The 2022 report also occurred in "航空写真" and in Chinese characters meaning aerial photography in English. As far as I know, the problem occurs when any of the Hiragana, Katakana, or Kanji characters commonly used in Japan are included. |
@kohei-hasegawa, does the issue only occur trying to import an MBTiles layer file or does it also occur trying to import any other layer file (e.g. ESRI Shapefile, or GeoPackage, or GeoTIFF, ...)? |
@agiudiceandrea I have worked with Esri Shape files, GeoPackages, GeoJSON, GeoTIFF, and many other formats of data, but the problem occurs only with MBTiles. The same problem occurs in the Browser panel and Data Source Manager. The error displayed in Data Source Manager showed URI encoding. Error Description Paths set in the UI I have attached the MBTiles used in this test. |
@kohei-hasegawa, thanks for checking. Anyway the provided layer is not a "Vector Tile" layer, but it is a raster layer: please try if it is possible to add it using the Data Source Manager -> Raster tab. It seems to me the issue only occurs importing the MBTiles layer file having name The issue occurs also with various characters other than Japanese or Chinese or Korean in the path: for example Additional notes:
|
Testing some LTR versions, it looks like:
|
Hi @wonder-sk, have you seen this issue report about MBTiles raster layers in paths containing multibytes that are not correctly handled by the WMS provider? |
Thanks for your help. Please correct me if I am wrong in my perception.
Do you need any additional information from me? |
@kohei-hasegawa , thanks for the report, this was a rather serious limitation/issue I'm glad we could address. The fix should make its way to the next public release (end of February). |
What is the bug or the crash?
Unavailable layer!
Layer data source could not be found.
Click to set a new data source
"テスト" in the layer or file name is Japanese and means test in English.
Error in Layer List
![image](https://private-user-images.githubusercontent.com/9637150/299928808-ff89a71e-aac5-406a-b6f0-2796ecf70783.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA4OTkyNjAsIm5iZiI6MTcyMDg5ODk2MCwicGF0aCI6Ii85NjM3MTUwLzI5OTkyODgwOC1mZjg5YTcxZS1hYWM1LTQwNmEtYjZmMC0yNzk2ZWNmNzA3ODMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTNUMTkyOTIwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZGU0YzVlMmRjNThlNTk3MzhkYWYxZjc4MjFkMWY2YjMxMTgxNTVmZDQ3NGNkNzEzOTFiMTE3MDg3NGMwYmM3MCZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.m8tN8kfDDwZUp1oWJiyXLx77fBmHOL4mQYuqeGAG3a8)
Repair Data Source screen
![image](https://private-user-images.githubusercontent.com/9637150/299929803-20eca9e0-1cce-4033-a135-ce5dd3c902c1.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjA4OTkyNjAsIm5iZiI6MTcyMDg5ODk2MCwicGF0aCI6Ii85NjM3MTUwLzI5OTkyOTgwMy0yMGVjYTllMC0xY2NlLTQwMzMtYTEzNS1jZTVkZDNjOTAyYzEucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDcxMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA3MTNUMTkyOTIwWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDM0OTM1OTc0MzlkM2FmMGQ3ZTlhNjIyYmFiNzZjZDVmMGIzOTY4M2I0ZjYwZTJiOWFlODUyODJjNjhkNjlhYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.Pi9xhejg_Ydk5JYijJWt1MKjzqxWp2ovj7Erw-aAhrM)
Steps to reproduce the issue
example:
"C:\OSGeo4W\テスト.mbtiles"
,"C:\OSGeo4W\テスト\test.mbtiles"
,"C:\OSGeo4W\テスト\テスト.mbtiles"
Versions
QGIS version
3.34.3-Prizren
QGIS code revision
4737323
Qt version
5.15.3
Python version
3.9.18
GDAL/OGR version
3.8.3
PROJ version
9.3.1
EPSG Registry database version
v10.098 (2023-11-24)
GEOS version
3.12.1-CAPI-1.18.1
SQLite version
3.41.1
PDAL version
2.6.0
PostgreSQL client version
15.2
SpatiaLite version
5.1.0
QWT version
6.1.6
QScintilla2 version
2.13.4
OS version
Windows 10 Version 2009
Active Python plugins
QuickOSM
2.2.3
db_manager
0.1.20
grassprovider
2.12.99
MetaSearch
0.3.6
processing
2.12.99
Supported QGIS version
New profile
Additional context
To try out the new profile, I started QGIS in PowerShell with the following command
PS C:\OSGeo4W\bin> .\qgis-bin.exe --profile english --lang en-us
The text was updated successfully, but these errors were encountered: