In a 30-minute routing demo, I was explaining drive-time polygons when our CSV import swapped lat/long and dropped their headquarters at -74, 40 — hello Southern Ocean. I smiled, called it “aspirational expansion,” and kept the ROI story going; what’s your go-to line when coordinate issues turn a sales demo into stand‑up?
Been there — my “penguin filter” runs before import: if the median lat is south of 0 for a US demo or any ‘lat’ looks like ±180, it prompts to swap columns and shows a 3‑point preview. Do you prefer a hard stop or just a nudge?
After I had the -74, 40 mishap in a 30‑minute demo, I added a CONUS bbox guardrail: if most points fall outside [-125,-66] x [24–50], I auto‑swap and flash “did you mean lon/lat?” before drive‑time polygons run. Small caveat: also sniff EPSG:3857 and block numbers that look like 4.8e6/‑8.2e6 so you don’t “aspirational expansion” into Web Mercator. Got a cleaner quick CRS check you like, @sam88?
I run an “Are we in Kansas?” check: sample 5 points, reverse‑geocode, and if most aren’t in the target state I auto‑swap or pop “wrong CRS? (EPSG:4326 vs 3857)” with a one‑tap fix — builds on your bbox idea, @hannah_wilson23. Ever tried tying the check to sales territory polygons instead of CONUS?