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
ogrinfo "/vsicurl/https://overturemapswestus2.blob.core.windows.net/release/2024-11-13.0/theme=divisions/type=division_area/" -al -so
ERROR 4: `/vsicurl/https://overturemapswestus2.blob.core.windows.net/release/2024-11-13.0/theme=divisions/type=division_area/' not recognized as being in a supported file format. ogrinfo failed - unable to open '/vsicurl/https://overturemapswestus2.blob.core.windows.net/release/2024-11-13.0/theme=divisions/type=division_area/'.
Versions and provenance
ogrinfo --version
GDAL 3.10.0, released 2024/11/01
Additional context
I am trying to read effectively Parquet files in a bbox directly from Azure
The text was updated successfully, but these errors were encountered:
Workaround with existing versions: AZURE_NO_SIGN_REQUEST=YES AZURE_STORAGE_ACCOUNT=overturemapswestus2 ogrinfo "PARQUET:/vsiaz/release/2024-11-13.0/theme=divisions/type=division_area//" --debug on -al -so
Note the trailing slash repeated twice. The workaround is not perfect because it causes the layer name to be an empty string, hence when converting to other formats with ogr2ogr you need to use -nln some_layer_name
rouault
added a commit
to rouault/gdal
that referenced
this issue
Nov 20, 2024
What is the bug?
According to docs and ogr_parquet.py GDAL should be able to read partitioned data.
However, the docs also says: "This support is only enabled if the driver is built against the arrowdataset C++ library."
I am not sure how can this be checked except:
or
Steps to reproduce the issue
list overture data
az storage blob list --account-name overturemapswestus2 --container-name release --output table --prefix 2024-11-13.0/ --delimiter "/" Name Blob Type Blob Tier Length Content Type Last Modified Snapshot ---------------------------------- ----------- ----------- -------- -------------- --------------- ---------- 2024-11-13.0/theme=addresses/ 2024-11-13.0/theme=base/ 2024-11-13.0/theme=buildings/ 2024-11-13.0/theme=divisions/ 2024-11-13.0/theme=places/ 2024-11-13.0/theme=transportation/
read one file
read partitioned data
Versions and provenance
Additional context
I am trying to read effectively Parquet files in a bbox directly from Azure
The text was updated successfully, but these errors were encountered: