AMap Command Line Tool

Problem

When automation needs to turn addresses, coordinates, POI results, and route data into structured output, calling AMap Web services directly usually means handling API keys, pagination, city parameters, coordinate systems, error codes, and request caching. This skill targets Windows scripting and exposes aligned Python and PowerShell command-line interfaces for embedding geospatial queries into workflows.

How It Works and Limits

The main commands cover geo, regeo, weather, ip, search, around, detail, route, distance, navi, and taxi, plus batch-geo, batch-around, export, and shell. Route planning supports driving, walking, bicycling, and transit; bicycling uses the v5 endpoint, while transit uses the integrated route endpoint and attempts automatic city detection. Search commands support -AllPages pagination, -OutputFile JSON export, and clear-cache for local request-cache cleanup.

Keep in mind: the API key must be an AMap Web services key; coordinates use longitude,latitude; the coordinate system is GCJ02; POI results are capped at 25 items per page; quota limits are governed by the AMap console, and throttling returns 10003. It is intended for mainland China geographic data, does not automatically convert coordinate systems, and does not replace client-side map rendering.