Actions6
- Search Actions
- Query Actions
- Spatial Actions
- Route Actions
Overview
The node provides a "Search Places" operation under the "Search" resource, enabling users to find places of interest using either free-form queries or structured address components. This is useful for applications that require location intelligence, such as finding landmarks, businesses, or specific addresses.
Common scenarios include:
- Searching for a famous landmark by name (e.g., "Eiffel Tower").
- Finding a type of amenity in a specific city (e.g., "Starbucks" in "New York").
- Looking up detailed addresses with multiple components like street, city, state, and postal code.
Practical examples:
- A travel app searching for tourist attractions by name.
- A delivery service locating restaurants or stores based on structured address input.
- An analytics tool querying points of interest within a certain region.
Properties
| Name | Meaning |
|---|---|
| Search Type | Type of search to perform: - Free-Form Query: Search using a free-form query string. - Structured Address: Search using structured address components. |
| Query | Free-form search query string (e.g., "Eiffel Tower"). Required if Search Type is Free-Form Query. |
| Amenity | Name and/or type of point of interest (POI) (e.g., "restaurant", "Starbucks"). Used if Search Type is Structured Address. |
| Street | Street name with optional house number (e.g., "123 Main Street"). Used if Search Type is Structured Address. |
| City | City name (e.g., "Paris", "New York"). Used if Search Type is Structured Address. |
| County | County name. Used if Search Type is Structured Address. |
| State | State or province name (e.g., "California", "Ontario"). Used if Search Type is Structured Address. |
| Country | Country name (e.g., "France", "United States"). Used if Search Type is Structured Address. |
| Postal Code | Postal or ZIP code (e.g., "10001", "75001"). Used if Search Type is Structured Address. |
| Limit | Maximum number of results to return. Minimum value is 1. Default is 50. |
Output
The node outputs JSON data containing the search results for places matching the query parameters. The structure typically includes details about each place found, such as name, address components, coordinates, and possibly other metadata relevant to the location.
If binary data output is supported (not explicitly shown in the provided code), it would likely represent media or map images related to the places found, but this is not indicated here.
Dependencies
- Requires an API key credential for authentication with the external Camino AI service.
- The base URL for API requests is configured dynamically from the user's credentials/environment settings.
- The node sends HTTP requests with JSON content type and expects JSON responses.
Troubleshooting
- Missing or invalid API key: Ensure the API key credential is correctly set up and valid.
- Empty or no results returned: Verify that the query parameters are correctly specified and that the search terms are valid.
- Invalid parameter combinations: For example, providing structured address fields when the search type is set to free-form may cause unexpected behavior.
- Limit parameter issues: Setting the limit below 1 will be rejected; ensure it is at least 1.
- Network or connectivity errors: Check network access and endpoint availability.
Links and References
- No direct links provided in the source code. Users should refer to the official Camino AI documentation for detailed API usage and authentication setup.