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 3 — use the page links below, or browse by topic above.
- Drought Percentages That Add Up to More Than 100%: Cumulative Categories
- Earthquake counts rise over time in my catalogue
- EIA-923 Monthly Values Are Dots: Reading Missing Months Correctly
- EIA-923 Plant 99999: Generation That Belongs to No Plant
- Election Results Won't Join the Boundaries: Codes, Wards and Renamed Places
- Empty Speedtest Tiles Are Not Places Without Internet
- EV Points Pile Up on One Spot: Vehicle Location Is a ZIP Centroid
- Event lengths do not add up to the route length
- Exposure counts are double-counted or missed
- Extruded buildings float above or sink into the ground
- Feature Importance Says Coordinates Are the Best Predictor
- FEMA Declarations That Will Not Join to Counties: Statewide and Tribal Rows
- Fixing "Object of type Timestamp is not JSON serializable" in Folium
- Fixing 429 Too Many Requests When Geocoding
- Fixing a Census Grid Total That Comes Out Below the Official Population
- Fixing a DuckDB Spatial Extension That Will Not Load
- Fixing a DuckDB Spatial Join That Never Finishes
- Fixing a Folium Map That Is Slow With Many Markers
- Fixing a Geocoder That Matches the Wrong Town
- Fixing a Geometry Column Lost on Export from DuckDB
- Fixing a Gravity Model That Sends Everyone to the Biggest Store
- Fixing a Gutenberg-Richter b-Value That Comes Out Too Low
- Fixing a Haversine Function That Returns the Wrong Distance
- Fixing a Location-Allocation Model That Never Solves
- Fixing a Map App That Takes Ten Seconds to Load
- Fixing a Map Export That Is Hundreds of Megabytes
- Fixing a Map That Resets or Disappears on Every Interaction
- Fixing a NetCDF Map That Is Shifted, Flipped or Split at 180°
- Fixing a Permit Series That Loses Two Years When County Codes Change
- Fixing a Plotly Choropleth Map That Shows No Colours