Geopackage

At some point, every mechanical or civil engineer gets handed a shapefile or GeoJSON and told to “do something with it.” Usually it is site boundary data for a facility layout, parcel boundaries for a land survey, drone-acquired point cloud footprints, or utility infrastructure from a municipal dataset. None of these came from SolidWorks or AutoCAD. They came from GIS, and they arrived in a format you may never have opened before. ...

Most municipalities and utility contractors have their underground infrastructure documented somewhere — in CAD as-built drawings, in PDFs, in someone’s head. Getting it into a proper GIS layer is the difference between calling 811 and hoping versus knowing where a 6-inch water main runs before you start excavating. QGIS handles this well. It’s free, it imports CAD files, and it exports GeoPDF files that field crews can use offline on a tablet. The setup isn’t complicated, but there are decisions you need to make before you start drawing — particularly around file format, CRS, and attribute schema — that determine whether the data is useful for the next 20 years or becomes another file nobody trusts. ...

A PSA on r/gis last month pointed out that Apache Parquet now has native geospatial types and that GDAL’s GeoParquet driver is mature, ESRI ships read/write support, and QGIS treats it as a first-class format. The thread had the same energy as the old “stop using shapefiles” threads, except this time the alternative is not a marginal incremental improvement. GeoParquet is a different shape of file that solves problems shapefiles never could. ...

GeoJSON keeps showing up in places it shouldn’t. Someone drops a 2 GB .geojson into a processing pipeline, the script that used to run in 20 seconds runs for eight minutes, and the team spends a Thursday wondering whether the problem is their query planner, their RAM, or their patience. The problem is the format. GeoJSON is a perfectly good interchange format — human-readable, one-spec wonder, works everywhere a text editor opens. It’s a terrible working format as soon as your dataset has more than a few hundred thousand features. This post is about when to stop loading GeoJSON directly and what to convert to instead, based on what teams handling real-scale data actually reach for. ...