Shapefile

If you have found a tutorial that includes a line like ogr2ogr -f GFT ... or links to http://www.gdal.org/ogr/drv_gft.html, the tutorial is dead. The GFT driver connected to Google Fusion Tables, which Google shut down on December 3, 2019. The gdal.org/ogr/drv_gft.html URL itself no longer resolves — the entire GDAL documentation was restructured and the GFT driver pages were not preserved. Links to it from GIS community sites still circulate and lead nowhere. ...

Data scientists encounter GIS when spatial data shows up in a project: a dataset with latitude/longitude columns, a shapefile from a government portal, a GeoJSON file someone dropped in the repo. The first few operations usually work. Then something breaks silently — a spatial join returns an empty DataFrame, a buffer produces geometry the size of a continent, or exported shapefiles arrive at the lab with every field name truncated. ...

GIS format conversions do not crash loudly when they fail. They produce an output file, report success, and leave you with data that is wrong in ways you may not notice until the analysis is already done. Field names get silently cut at 10 characters. Geometries disappear without warning. Coordinate systems shift without errors. Attribute types coerce to something that looks right but produces wrong numbers. These are not edge cases. They are the default behavior of the tools most GIS teams use daily — including GDAL/OGR, QGIS’s built-in export, and ArcGIS Pro’s geoprocessing toolbox. None warn you by default. ...

A shapefile arrives in your inbox, or you need to verify what’s in a .shp file before importing it into your pipeline. The two questions that come up immediately: what software do you need, and do you have to install anything? The short answer: no install required for a quick look. For anything involving CRS inspection, attribute filtering, or geometry validation, a desktop tool is worth the effort. What You’re Actually Inspecting A shapefile isn’t a single file — it’s a bundle that requires at least four components to be useful: ...

You convert a GeoJSON file to a shapefile and load it into ArcGIS. Your attribute table has changed. The field called municipality_name is now municipali. The field called building_type_code and the field called building_type_category are both now called building_t, except one of them got renamed to building_t0 by GDAL and you missed it. Your spatial join script that references building_type_code now silently returns nulls on every row. This is not a GDAL bug. It is the shapefile format working exactly as designed since 1983. ...

The problem with most “free GIS tools” roundup lists is that they treat GDAL, QGIS, GRASS, and PostGIS as competing products when they’re actually layers of the same stack. GDAL underpins QGIS. QGIS calls GRASS as a processing backend. PostGIS sits behind both for production data. Choosing between them isn’t “which is best” — it’s “which layer do I need to interact with directly.” This is a functional comparison: what each tool does well, where it breaks down, and which one to reach for when you receive a shapefile, a GeoJSON, or a KML and need it in something your software actually reads. ...

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. ...

A state environmental agency analyst posted on r/gis last week, describing the same problem every public-sector GIS team deals with: contractors, federal agencies, and utility companies all send shapefiles that are technically valid per the format spec, and yet every batch requires hours of cleanup. The analyst was scoping an open-source CLI tool to run preflight checks — field truncation, CRS mismatch, missing indexes, null geometry. The tool they need already exists in pieces inside GDAL. The problem is that nobody publishes the checklist. Here is the full preflight — the specific failure modes, the ogrinfo and ogr2ogr commands that detect them, and the decisions each check forces. ...

You run a GeoJSON-to-Shapefile conversion. The tool says it succeeded. You load the Shapefile into ArcGIS or QGIS and everything looks fine at first glance. Three weeks later, someone discovers that half the attribute data is wrong or missing. This is not hypothetical. It happens constantly in GIS workflows, and the reason is that GeoJSON and Shapefile are fundamentally different formats with incompatible assumptions about how data should be stored. Most conversion tools handle the geometry correctly but silently destroy the attributes. ...