-
-
Notifications
You must be signed in to change notification settings - Fork 126
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
GDAL/OGR + QGIS read-only support #177
Comments
OGR PMTiles driver proposed per OSGeo/gdal#7938 |
the GDAL PR addresses opening PMTiles to retrieve OGR features, however given the above requirements maybe what we want is a QGIS native driver analogous to qgsmbtiles.cpp for PMTiles. This would enable proper dynamic zoom and tile display in QGIS. However, the QGIS native driver for MBTiles opens a SQLite database in-process, and can't benefit from the existing abstraction over |
I believe my issue (as commented qgis/QGIS#57041) was related to QGIS just picking the highest zoom level and trying to render everything at once... |
@four43 that is correct, for multi-resolution tiled data that chooses a zoom level with the viewport, the driver needs to be implemented in QGIS itself and not in GDAL (MBTiles for example) |
Motivation
Read PMTiles, particularly vector archives, from the cloud or local storage using QGIS.
Currently MBTiles works by "drag and drop" into QGIS, and may work through adding a Vector Tile layer type. We want the same while also supporting
vsicurl
for accessing tiles via HTTP Ranges.The priority should be on vector tiles, since raster tiles are well covered by existing formats. We only care about read support for now, because writing vector tilesets is best left to specialized tools like tippecanoe/planetiler.
pmtiles.hpp is the existing C++ implementation of pmtiles v3 utility functions that is copied into the tippecanoe source tree. This is intentionally written to be unopinionated about I/O and compression, as to re-use those already in GDAL.
Links
Tagging @rouault (via @cholmes)
The text was updated successfully, but these errors were encountered: