This article solves a HarmonyOS 7 issue where getAddressesFromLocation returns an empty array without errors, revealing the root cause is a coordinate system mismatch: Map Kit provides GCJ02 coordinates while the geocoding API requires WGS84, and provides a conversion algorithm and complete implementation.
This article details the step‑by‑step development of a WeChat mini‑program that adds location‑based check‑ins, covering fuzzy location retrieval, moving reverse‑geocoding to the backend for key protection, the failed attempt at precise GPS, and the final hybrid approach of fuzzy auto‑location combined with manual map point selection.
The author recounts how a tutoring mini‑program’s required reverse‑geocoding API from Tencent, Baidu, and Gaode each demanded ¥50,000 annually, explores cheaper shared or second‑hand options, and ultimately proposes using a static province‑city database to avoid the expense, noting the trade‑offs.
By eliminating unnecessary reverse‑geocode calls, aggregating nearby coordinates with GeoHash, and employing a multi‑layer LRU‑K cache with time‑ and access‑count eviction, the Hellobike map team cut daily requests from 200‑300 million to 20‑30 million while adding fallback and monitoring mechanisms.
This article explains how Baidu Maps’ reverse‑geocoding service converts coordinates into addresses using point, line, and polygon data mapped onto a grid index, describes the incremental indexing mechanism that enables rapid data updates, and highlights the system’s high availability and performance characteristics.
