🌐 Geocoding Settings — Service Provider & Cache Configuration

Primary Provider — selected provider is called first for every reverse geocode request

BigDataCloud
Free · No Key Needed
Client-side reverse geocoding. No API key, no rate limit for normal usage. Best for high-frequency fleet tracking. Returns detailed Malaysian addresses.
🗺️
Geoapify
Free Tier · 3,000 req/day
OpenStreetMap-powered geocoding with commercial-grade reliability. Free tier covers small fleets. API key required. Good Malaysia coverage.
📍
Google Maps
Paid · $5 / 1,000 req
Industry-leading accuracy. Requires billing enabled on Google Cloud. Best address quality for Malaysia. Use as primary only for premium operations.

Fallback Chain — when primary fails, try these in order

ℹ️ Primary provider is always tried first. Fallback chain is used only on failure or missing API key.

API Keys — stored server-side, never exposed to browser

🗺️ Geoapify
Get a free key at geoapify.com · 3,000 req/day free
📍 Google Maps
⚠️ Billing must be enabled on Google Cloud Console before use.

Redis Cache — geocode results cached to prevent duplicate API calls

Locations Cached
Sample TTL (days)
Uncached Positions
Distinct Positions (30d)
Selected TTL applies on next save

Setup History — every configuration change is logged

Date / Time (MYT) Changed By Primary Provider Fallback Order Cache TTL Keys Changed Note
Loading history…
⚠️ Unsaved changes