Tencent Maps WebService API

Problem

Location features often fail at integration details: combining addresses, coordinates, directions, distances, weather, and key permissions. Manually assembling GET requests easily hits coordinate order, coordinate system, quota, and error-code issues.

How it works

It routes requests by intent to Tencent Location Services WebService API and covers:
- Geocoding: address parsing, reverse geocoding, smart address parsing via /ws/geocoder/v1/
- Search: place search, keyword suggestions, administrative districts
- Directions: driving, walking, cycling, transit, and /ws/distance/v1/matrix
- Location and weather: IP city-level location and weather queries
- Coordinate conversion: GPS/Baidu coordinates into GCJ-02
The workflow checks or saves the key, selects a scenario, obtains coordinates first for combined requests, then calls search, directions, or weather. If a key fails, it switches candidate keys and reports the failure reason. It keeps API calls, key fallback, and error handling in one workflow.

Boundaries and notes

Coordinates must be latitude,longitude; raw GPS coordinates need conversion first. key, QPS, whitelist, and permission settings affect calls. Smart address parsing requires enterprise certification; distance matrix, waypoints, and coordinate counts have limits. Suitable for engineers embedding location capabilities into apps or scripts.