has someone ever seen this kind of artifacts with vector tiles generated by ogr2ogr ?
The strangest part is that is it only one some small territories.
cloud optimized #geotiff (#cog) question:
I've got a layer that renders fine in @qgis when is stored in a local drive & from a S3 URL.
But when its on a network drive (well, a "drive" through an S3 storage gateway), I get the following when zooming in:
[layername]: IReadBlock failed at X offset 21, Y offset 22: TIFFReadEncodedTile() failed.
Thought maybe its a file system thing & I need to use #gdal virtual file system paths, but not getting that to work at all. Any ideas? #gischat
I've not taken time over the last few months to "play" with geo. I've been hitting conferences and marketing and doing all the things I sort of don't like that much. More talk of conferences coming. One thing I've seen pop up more and more is duckdb. Wht is it? Basically a serverless database. It's local. You use it for data analysis or data update locally.
@migurski@nyalld@rjhale1971 Indeed, #GDAL / #OGR already has optimizations for column-oriented formats with a dedicated API. Supporting this natively in #QGIS would need some low-level work though, which has to be carefully designed and agreed on collectively. @EvenRouault already made interesting feedback on this topic. We can go step by step, evaluating use cases with the plugin before implementing into core. Get in touch with @oslandia if you want to help and/or fund the effort ! #duckdb
Observation: #OpenSoftware spatial analytics tools (#QGIS, #GDAL, #GeoPandas)—despite heroic efforts from their developers—are frequently broken and/or unusable because of fragile and complex dependencies.
Research Questions:
Why has the open source spatial analytics ecosystem resisted greater centralization or coordination?
What social and material factors shape(d) these relationships?
How does popular proprietary software like ArcGIS distort open source alternatives?
1/2 @bkeegan I mostly use @qgis and #PostGIS, and #gdal only indirectly via those two. I don't think these 3 shouldn't be further centralised into 1, but that's probably not what you meant.
@qgis does have issues, and I encounter bugs more often than I like, especially in the more esoteric parts of the system. However, so far the haven't been caused by dependencies but "normal bugs" within Qgis itself.
@bkeegan Your observation is absolutely correct, but it doesn't specifically plague spatial software. It is generally applicable to the greater realm of scientific software and the replication crisis. #GDAL itself currently has over 1800 configuration options! For package managers to provide a one-size fits all binary is near impossible. One potential solution is for users of complex software is to use functional package managers like #guix which allow per-package transformations, for example.
#Introduction Trained as a historian at the university of #Trier I started programming during my exchange year in Bordeaux, France. After my graduation I worked at the University of Trier and specialized in Historical GIS #hisgis#hgis. Currently I am working in the field of #spatialhumanities and #digitalhumanities at the Hessische Institut für Landesgeschichte in #Marburg, using Open Source Technologies (#Python, #QGIS, #Gdal, #GRASS, #OpenLayers, #Angular et. al.)