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 8 — use the page links below, or browse by topic above.
- LST Values on the Wrong Scale
- M values are lost when you export the route
- Metadata disappears when you convert the file
- Metadata extents and dates do not match the data
- Mixed Geometry Types Error When Saving a GeoDataFrame: How to Fix It
- MODIS Sinusoidal Tiles Do Not Line Up
- ModuleNotFoundError in a Scheduled GIS Job: Fixing the Wrong Python Environment
- My Cleaned Layer Has More Rows Than the Original: How to Fix It
- My Composite Has Holes, Stripes or Grey Patches
- My Folium Map Is Blank or Will Not Display: How to Fix It
- My Geocoder Returns No Match for Addresses That Exist
- My GeoJSON Is Too Big for the Browser
- My GeoPandas Choropleth Colours Look Wrong: How to Fix It
- My GIS Pipeline Fails Silently: Fixing Swallowed Errors and Wrong Exit Codes
- My IDW Surface Is Full of Bullseyes
- My Interpolated Surface Extends Far Beyond the Data
- My Kriging Fit Fails or Returns a Flat Surface
- My LiDAR DTM Has Holes, Spikes or Terraces
- My Model Scores 0.95 in Testing and Fails in the Field
- My Points Plot in the Ocean: Fixing Swapped Latitude and Longitude
- My PostGIS Spatial Query Is Slow: How to Fix It
- My Prediction Raster Is Striped, Blocky or Full of NoData
- My Tiles Are Offset or in the Wrong Place
- My Time Column Sorts or Joins Wrongly
- My Track Has Impossible Speeds or Teleports
- My Web Map Is Blank or the Layer Never Appears
- Nameplate or Summer Capacity: Why Power Plant Capacity Totals Disagree
- NBI Coordinates Land in the Wrong Place: Packed Degrees, Minutes and Seconds
- NBI Inspection Dates That Will Not Parse: Month and Year Without Leading Zeros
- NDSI Snow Is Confused with Cloud or Water