Why GeoJSON-to-Shapefile Conversions Silently Corrupt Your Data
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. ...