Actions2
Overview
This node integrates with Yahoo! Maps' Map and Local Information API to perform geocoding operations. Specifically, the "Reverse Geocoder" operation converts geographic coordinates (latitude and longitude) into a human-readable address or location information. This is useful in scenarios where you have GPS coordinates from devices or services and want to find the corresponding address or place name.
Practical examples include:
- Converting user device GPS coordinates into addresses for display in apps.
- Mapping locations of events or incidents based on latitude and longitude.
- Enriching datasets containing coordinates with location names for reporting or analysis.
Properties
| Name | Meaning |
|---|---|
| Latetude | Latitude coordinate (number) |
| Longitude | Longitude coordinate (number) |
Note: The properties are used as query parameters (lat and lon) in the reverse geocoding API request.
Output
The node outputs JSON data representing the location information corresponding to the provided latitude and longitude. The exact structure follows the response format of Yahoo! Maps Reverse Geocoder API, typically including address components, administrative areas, and other local information.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Yahoo! Maps Developer API.
- The node makes HTTP GET requests to
https://map.yahooapis.jp/geoapi/V1/reverseGeoCoder. - Proper configuration of the API key credential within n8n is necessary for authentication.
Troubleshooting
- Invalid or missing API key: The node will fail if the Yahoo! Maps API key is not set or invalid. Ensure the API key credential is correctly configured.
- Incorrect latitude or longitude values: Providing out-of-range or non-numeric values may cause errors or empty results. Verify that latitude is between -90 and 90, and longitude between -180 and 180.
- API rate limits exceeded: If too many requests are made in a short time, the API may reject calls. Implement throttling or check usage limits.
- Network issues: Connectivity problems can cause request failures. Check network access and proxy settings if applicable.