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 10 — use the page links below, or browse by topic above.
- RasterioIOError: Not Recognized as a Supported File Format (How to Fix)
- Reading a COG from a URL Is Slow or Downloads Everything
- Relative Paths Break When a GIS Script Runs Automatically: How to Fix It
- Restaurant Inspection Counts Too High: One Row per Violation
- Restaurant Inspections Dated 1 January 1900: New Places Not Yet Inspected
- Restaurants Plotted in the Ocean: Zero Coordinates in Inspection Data
- Route measures are not monotonic
- SAR scenes from different dates do not line up
- SAR values come out negative, huge or averaged wrongly
- Satellite Bands Have Different Shapes or Do Not Align
- Satellite NO2 Map Mostly Empty
- Sea-Ice Extent Numbers Disagree
- Shadows point the wrong way or have the wrong length
- Shapely TopologyException: Found Non-Noded Intersection (How to Fix)
- Siting Mask Removes Everything
- Slope Values Are Wrong or Absurdly Steep
- Snow Depth Data Has Gaps, Zeros and Impossible Values
- Solar Timestamps Shifted by an Hour
- Spatial Join Returns Empty Results in GeoPandas: How to Fix It
- Spatial Weights Warn About Islands or Moran's I Returns nan
- SPI Fails in Dry Climates: Months With No Rain and the Gamma Fit
- stop_times.txt is too big to load comfortably
- Storm Events Damage Columns Will Not Sum: 10.00K, 1.60B and Blanks
- Storm Events Will Not Join to Counties: Forecast Zones Are Not FIPS Codes
- Storm Track Crosses the Dateline: Lines Across the Whole Map
- Street Network Routing Returns Absurd Distances
- Street Orientation Looks Wrong
- Street Trees 425 Inches Across: Impossible Diameters in Tree Census Data
- SUHI Rural Reference Gives the Wrong Answer
- Suppressed cells can be recovered from the totals