Fix batch geocoding rate limits for datasets over 10 rows

[svickars]

Summary

• Raises the geocode API rate limit from 10 to 60 requests per minute to support normal batch geocoding while staying within Nominatim's ~1 req/sec guidance
• Fixes in-memory rate limit counter expiry so local dev no longer stays blocked indefinitely after hitting the limit
• Skips rate limiting for server-side cache hits and adds client retry/backoff on 429 responses
• Throttles geocoding requests to 1.1s between API calls instead of 200–400ms bursts

Test plan

• Load a symbol map dataset with 28+ rows (city + state columns, no lat/lng)
• Run geocoding and confirm all rows complete without 429 errors
• Re-run geocoding and confirm cached rows resolve instantly without consuming rate limit budget
• In local dev (no Vercel KV), hit the rate limit, wait 60 seconds, and confirm geocoding resumes
• Verify geocoded coordinates appear correctly on the map preview

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
map-studio	Ready	Preview	Aug 10, 2026 7:05pm