Actions16
Overview
This node integrates with the Gaode Map (Amap) API to provide various map-related services, including location conversion, positioning, and route planning. Specifically, for the "路径规划" (Route Planning) resource and the "骑行路径规划" (Cycling Route Planning) operation, it calculates optimal cycling routes between a specified origin and destination based on geographic coordinates.
Common scenarios where this node is beneficial include:
- Planning bike-friendly routes for delivery or courier services.
- Providing users with cycling directions in navigation apps.
- Integrating cycling route suggestions into travel or fitness applications.
Practical example:
- A logistics company wants to optimize bike courier routes within a city by inputting start and end GPS coordinates to receive detailed cycling paths.
Properties
| Name | Meaning |
|---|---|
| 出发点 | Starting point coordinates in longitude,latitude format (e.g., "117.500244,40.417801"). Longitude and latitude decimals up to 6 places. Required. |
| 目的地 | Destination point coordinates in longitude,latitude format (e.g., "117.500244,40.417801"). Longitude and latitude decimals up to 6 places. Required. |
Output
The node outputs JSON data containing the cycling route details between the origin and destination points. This typically includes step-by-step navigation instructions, distance, estimated duration, and possibly route geometry.
If binary data output is supported (not explicitly shown in the provided code), it would likely represent map images or route visualizations, but no such indication is present here.
Dependencies
- Requires an API key credential for the Gaode Map (Amap) service.
- The node uses the base URL configured in the credentials for API requests.
- Internet access is necessary to communicate with the external Gaode Map API endpoints.
Troubleshooting
- Invalid Coordinates: Ensure that the origin and destination are correctly formatted as "longitude,latitude" with valid numeric values and up to six decimal places.
- API Authentication Errors: Verify that the API key credential is correctly set up and has permissions for route planning services.
- Network Issues: Check internet connectivity and that the base URL for the API is reachable.
- Unexpected API Responses: Since HTTP status errors are ignored by default, inspect the returned JSON for error messages from the API and adjust parameters accordingly.