map

To plan a route and find POIs using the AMap API, you need a valid API key for geocoding, route computation, and point-of-interest discovery. This Skill handles address normalization and returns formatted outputs with origin and destination names.

Yes, POI search supports text-based queries for restaurants and attractions with city and type filtering. It leverages the AMap API to return localized point-of-interest results for travel planning and city navigation.

Yes, a valid AMap API key is required to perform routing, geocoding, and smart location resolution. The Skill uses this key to authenticate requests for driving, walking, cycling, and transit route computations.

AMap routing supports driving, walking, cycling, and transit route planning with waypoint processing and strategy selection. It computes distances and ETAs while normalizing origin and destination inputs for accurate travel navigation.

Smart location resolution parses raw origin and destination inputs into normalized coordinates using AMap geocoding. This ensures accurate route computation and returns formatted outputs containing recognizable location names for conversational output.

Route request errors during travel planning typically occur when the AMap API key is missing, invalid, or lacks permissions for geocoding and routing. Ensure your API key is active and properly configured for the required map services.