GDAL can fix invalid geometries in a few different ways, depending on what you want to preserve. The main options are a “linework” approach that sticks closely to the original input, and a “structure” approach that prioritises clean, valid polygons 🛠️
Since GDAL 3.12, you can also run this directly from the command line with `gdal vector make-valid`.
R package gdalraster has been updated on CRAN. The package provides comprehensive API bindings to GDAL. v2.6.0 is a feature release with full changelog at:
🚀 QGIS2VectorTiles v2.5 is out! Here’s what’s new:
✅ Added support for many additional @qgis style properties (including label placement and icon rotation) in @maplibre export.
🛠️ Fixed issues with nested renderer/labeling rule export
🧹 Refactored codebase for better maintainability and readability
https://github.com/GallPeters/QGIS2VectorTiles
Please share this post and don’t forget to say goodbye to ESRI’s VTPK 🙂
Keep spreading the word — Go #FOSS 🔥
#qgis #gdal #maplibre #gis #mapping #cartography #geospatial
@kevin the theory says you can get the object's id, from there download any version it's useful (the site provides a link to a OSM XML version), use #GDAL to convert to a projection that is locally good enough so there are not much distortion (WebMercator and LatLon are not good), hopefully one that uses meters as unit, then calculate the surface as any polygon.
The Devil is in the details, tho.