Fixes
Targeted fixes for the most frustrating Python GIS errors — from a failed install to a batch job that stops at file seven.
Every fix, A–Z
Page 5 — use the page links below, or browse by topic above.
- Fixing Missing or Substituted Fonts in an Exported Map PDF
- Fixing Negative Populations and Values in Census Grid Data
- Fixing NetCDF Values That Look Wrong: scale_factor, _FillValue and Units
- Fixing open_mfdataset That Is Slow, Hangs or Will Not Combine
- Fixing Open-Meteo "429 Too Many Requests" Errors in Python
- Fixing OpenStreetMap Features Counted Twice as Lines and Polygons
- Fixing OpenStreetMap Lakes and Parks That Show as Lines Instead of Polygons
- Fixing OpenStreetMap maxspeed Values That Are Not Numbers
- Fixing Peak Ground Acceleration Values That Are 100 Times Too Large
- Fixing Population Densities That Are Wrong on Latitude-Longitude Grids
- Fixing Population Totals That Add Up to More Than the Whole
- Fixing Sea Surface Temperature Anomalies That Disagree Between Sources
- Fixing SST Values That Read as Thousands Instead of Degrees
- Fixing ST_Read Failures on Spatial Files in DuckDB
- Fixing Streams That Run in Straight Parallel Lines Across Flat Ground
- Fixing Streams That Stop at Roads, Bridges and Embankments
- Fixing USGS Earthquake Times That Show Up as 1970
- Fixing Voronoi Polygons That Extend Forever or Miss the Study Area
- Fixing Weather Data in the Wrong Time Zone
- Fixing xarray's "Did Not Find a Match in Any of xarray's Installed Backends"
- Forest Area Wrong in Degrees
- Forest Loss and Gain Misread
- Forest Loss Trend Not Comparable Over Time
- Forest Threshold Changes Everything
- Fragmentation Metrics Change with Resolution
- Garbled Attribute Text and UnicodeDecodeError from a Shapefile: How to Fix Encoding
- GDAL and GeoPandas Fail Inside Docker: How to Fix the Build
- GDAL Cannot Open an S3 or HTTPS Path
- Geocoding Returns Wrong or Missing Coordinates
- GeoJSON Downloaded from an API Is Empty or Truncated