Amazon Location Service
ClineOfficialCreated by aws-geospatialDistributed by Cline
- Skill
- Tool integration
- Cloud and DevOps
- MIT-0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Amazon Location Service provides a suite of geospatial APIs for web and mobile applications. This skill covers the integration of maps, geocoding, routing, places search, geofencing, and device tracking. It emphasizes using the bundled JavaScript client for web development and leveraging resourceless API operations to simplify deployment and IAM management. The skill provides guidance on authentication via API keys or Cognito, proper MapLibre configuration, and best practices for address input and verification.
What it does
- Provides interactive maps using MapLibre or static map images.
- Converts addresses to coordinates (geocoding) and coordinates to addresses (reverse geocoding).
- Calculates routes, travel times, and service areas with traffic estimation.
- Enables text-based place search, nearby search, and autocomplete suggestions.
- Monitors geographical boundaries with geofences and tracks device locations.
- Simplifies authentication using API keys for public apps or Cognito for secure resources.
When to use it
- When building location-aware web or mobile applications on AWS.
- When you need to implement address autocomplete, validation, or standardization.
- When integrating interactive maps or route calculation into your software.
- When you need to track assets or monitor geofence entry and exit events.
- When migrating existing geospatial features to Amazon Location Service.
Advantages
- Reduces complexity by supporting resourceless API operations.
- Simplifies web integration with a pre-bundled JavaScript client.
- Provides granular control over authentication via IAM or API keys.
- Ensures consistent data quality through standardized address verification.
- Optimizes performance by using direct URL passing for map styles.
Usage examples
- “How do I implement an address autocomplete field for my web form?”
- The agent will guide you to use the Autocomplete API, display Address.Label instead of Title, and use GetPlace to retrieve full details once a user selects a suggestion.
- “How should I authenticate my map component for a public website?”
- The agent will recommend using an API Key with restricted AllowActions (e.g., geo-maps:GetTile) to avoid exposing AWS credentials while enabling map rendering.
- “What is the best way to verify a user-submitted address before saving it to my database?”
- The agent will advise using the Geocode API to validate and standardize the address string, checking for multiple matches to handle ambiguity.
- “How do I initialize a MapLibre map with Amazon Location Service?”
- The agent will provide the configuration steps, including passing the style descriptor URL directly and setting validateStyle to false for faster loading.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/cline/amazon-location-service/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip amazon-location-service.zip -d .agents/skills
Documentation by aws-geospatial
Overview
Amazon Location Service provides geospatial APIs for maps, geocoding, routing, places search, geofencing, and tracking. Prefer the bundled JavaScript client (@aws/amazon-location-client) for web development and use resourceless API operations to avoid managing AWS resources.
When to Use This Skill
Use this skill when:
Building location-aware web or mobile applications
Working with Amazon Location Service projects
Implementing maps, geocoding, routing, or places search
Adding geofencing or device tracking functionality
Integrating geospatial features into AWS applications
Do NOT use this skill for:
Google Maps, Mapbox, or Leaflet-with-OSM projects (unless migrating to Amazon Location)
Generic GIS operations without AWS context
Non-AWS geospatial services
Amazon Location Service API Overview
Places (SDK: geo-places, JS: @aws-sdk/client-geo-places)
Geocode (Forward/Reverse): Convert addresses to coordinates and vice versa
Search (Text/Nearby): Find points of interest with contact and hours info
Autocomplete: Predict addresses based on user input
Suggest: Predict places and points of interest based on partial or misspelled user input
Get Place: Retrieve place details by place ID
Maps (SDK: geo-maps, JS: @aws-sdk/client-geo-maps)
Dynamic Maps: Interactive maps using tiles with MapLibre rendering
Static Maps: Pre-rendered, non-interactive map images, good for including an image into a web page, or for thumbnail images
Routes (SDK: geo-routes, JS: @aws-sdk/client-geo-routes)
Route calculation with traffic and distance estimation
Service area/isoline creation
Matrix calculations for multiple origins/destinations
GPS trace alignment to road segments
Route optimization (traveling salesman problem)
Geofences & Trackers (SDK: location, JS: @aws-sdk/client-location)
Geofences: Detect entry/exit from geographical boundaries
Trackers: Current and historical device location tracking
API Keys (SDK: location, JS: @aws-sdk/client-location)
API Keys: Grant access to public applications without exposing AWS credentials
Common Mistakes
Avoid these frequent errors:
Using
Titleinstead ofAddress.Labelfor display: In Autocomplete results, always displayAddress.Label. TheTitlefield may show components in reverse order and is not suitable for user-facing text.Using GetStyleDescriptor API for map initialization: MUST use direct URL passing to MapLibre (
https://maps.geo.{region}.amazonaws.com/v2/styles/Standard/descriptor?key={apiKey}) instead of making GetStyleDescriptor API calls. The direct URL method is required for proper map rendering.Forgetting
validateStyle: falsein MapLibre config: Always setvalidateStyle: falsein the MapLibre Map constructor for faster map load times with Amazon Location styles.Mixing resource-based and resourceless operations: When possible, prefer resourceless operations (direct API calls without pre-created resources) for simpler deployment and permissions.
Inconsistent API operation naming: Use the format
service:Operationwhen referencing APIs (e.g.,geo-places:Geocode,geo-maps:GetStyleDescriptor). SDK clients use@aws-sdk/client-*format.Not handling nested Address objects correctly: The Address object from GetPlace contains nested objects (
Region.Code,Region.Name,Country.Code2, etc.), not flat strings. Access nested properties correctly.Wrong action names in API Key permissions: API key
AllowActionsusegeo-maps:,geo-places:,geo-routes:prefixes (e.g.,geo-places:Geocode,geo-routes:CalculateRoutes). Do NOT use SDK client names (@aws-sdk/client-geo-places) or IAM-style actions. See the Authentication and Permissions section for the complete list.
Defaults
Use these default choices unless the user explicitly requests otherwise:
JavaScript SDK: Bundled client (CDN) for browser-only apps; npm modular SDKs (@aws-sdk/client-geo-*) for React and build tool apps
API operations: Resourceless for Maps/Places/Routes (Geofencing/Tracking always require pre-created resources)
Authentication: API Key for Maps/Places/Routes; Cognito for Geofencing/Tracking
Map style: Standard
Coordinate format: [longitude, latitude] (GeoJSON order)
Override: User can specify "use Cognito for Maps/Places/Routes" or "use bundled client for React".
API Selection Guidance
Choose the right API for your use case:
Address Input & Validation
Autocomplete → Type-ahead in address forms (partial input: "123 Main")
GetPlace → Get full details after user selects autocomplete result (by PlaceId)
Geocode → Validate complete user-typed address or convert address to coordinates
Finding Locations
SearchText → General text search ("pizza near Seattle")
SearchNearby → Find places near a coordinate (restaurants within 5km)
Suggest → Predict places/POIs from partial or misspelled input
Autocomplete → Address-specific predictions (not for general POI search)
Geocoding
Geocode (Forward) → Address string → Coordinates
ReverseGeocode → Coordinates → Address
Maps
Dynamic Maps (tiles + MapLibre) → Interactive maps requiring pan, zoom, markers
Static Maps (image) → Non-interactive map images for thumbnails or email
Routing
CalculateRoutes → Single route between origin and destination
CalculateRouteMatrix → Multiple origins/destinations travel times
CalculateIsolines → Service areas (all locations reachable within time/distance)
LLM Context Files
When you need detailed API parameter specifications or service capabilities not covered in the reference files, fetch these llms.txt resources:
Developer Guide: https://docs.aws.amazon.com/location/latest/developerguide/llms.txt
API Reference: https://docs.aws.amazon.com/location/latest/APIReference/llms.txt
Key Guidance for Better Recommendations
Prefer the Bundled JavaScript Client for Web Development
For convenient web application development, Amazon Location Service provides a bundled JavaScript client that simplifies integration and provides optimized functionality without custom bundling. This bundled client includes all libraries required to build client side web applications with Amazon Location Service.
Features included in the bundled client:
Enables direct pre-bundled dependency inclusion without custom bundle / build
Simplified authentication and API integration
TypeScript support with comprehensive type definitions
Support for all Amazon Location SDKs
Included SDKs and Libraries:
@aws-sdk/client-geo-maps
@aws-sdk/client-geo-places
@aws-sdk/client-geo-routes
@aws-sdk/client-location
@aws-sdk/credential-providers
https://github.com/aws-geospatial/amazon-location-utilities-auth-helper-js
Resources:
NPM Package: @aws/amazon-location-client
GitHub Repository: aws-geospatial/amazon-location-client-js
Prefer Resourceless Operations
Amazon Location Places, Maps and Routes services offer both resource-based and resourceless API operations. Resourceless operations are often simpler and more appropriate for many use cases.
Resource-based operations require you to:
Create and configure Amazon Location Service resources (maps, place indexes, route calculators)
Manage resource lifecycle and permissions
Handle resource naming and organization
Resourceless operations allow you to:
Make API calls directly without pre-creating resources
Reduce deployment complexity
Simplify IAM permissions and API Key permissions
Authentication and Permissions
When discussing permissions for Amazon Location Places, Maps and Routes services, always include both IAM permissions and API Key permissions in your guidance. If the type of application being developed is clear, recommend the appropriate authorization tool as described below:
IAM Permissions - Recommended for server-side applications and AWS SDK usage:
Used with AWS credentials (access keys, roles, etc.)
Provide fine-grained access control
Required for resource management operations
API Key Permissions - Alternative authentication method, especially useful for client-side applications or applications deployed to unauthenticated (public) users:
Simplified authentication without exposing AWS credentials
Can be configured with specific allowed operations
Useful for web and mobile applications
Supports both resource-based and resourceless operations
Enables faster subsequent map loads through CDN caching
API Key Action Names - API keys use their own action naming convention. Do NOT use SDK client names or IAM action names — they will be rejected.
Resourceless API key actions (recommended):
| Service | AllowActions | AllowResources |
|---|---|---|
| Maps | geo-maps:GetTile, geo-maps:GetStaticMap | arn:aws:geo-maps:REGION::provider/default |
| Places | geo-places:Autocomplete, geo-places:Geocode, geo-places:ReverseGeocode, geo-places:SearchText, geo-places:SearchNearby, geo-places:Suggest, geo-places:GetPlace | arn:aws:geo-places:REGION::provider/default |
| Routes | geo-routes:CalculateRoutes, geo-routes:CalculateRouteMatrix, geo-routes:CalculateIsolines, geo-routes:OptimizeWaypoints, geo-routes:SnapToRoads | arn:aws:geo-routes:REGION::provider/default |
Do NOT use legacy geo: prefixed actions (e.g., geo:GetMap*, geo:CalculateRoute) — these are for pre-created resources only and will not work with resourceless APIs.
MCP Server Integration
Integrates with the AWS MCP Server (Apache-2.0 license) which provides access to AWS documentation, API references, and direct API interactions. See the Getting Started Guide for setup and credential configuration. To use a non-default region, add "--metadata", "AWS_REGION=<your-region>" to your MCP config args.
Additional Resources
Reference Files
Load these resources as needed for specific implementation guidance:
Address Input - Create effective address input forms for users with address type ahead completion improving input speed and accuracy
Address Verification - Validate addresses input from users before taking actions or persisting to databases
Calculate Routes - Calculate routes between locations with customizable travel options and display them on maps
Dynamic Map Rendering - Render dynamic maps with MapLibre
Places Search - Search for places or points of interest
Web JavaScript - Integrate Amazon Location services into web browser applications
Files
- ATTRIBUTION.mdAdded by AutoGineer883 B
- SKILL.md12.5 KiB
- references/address-input.md8.9 KiB
- references/address-verification.md15.9 KiB
- references/calculate-routes.md40.6 KiB
- references/dynamic-map.md10.6 KiB
- references/places-search.md17.4 KiB
- references/web-javascript.md14.9 KiB
references/places-search.md
Places Search
Audience Note: Keywords MUST, SHOULD, MAY in this document indicate requirements for agent recommendations to users, following RFC 2119.
Search for places, points of interest, businesses, and addresses using Amazon Location Service Places APIs.
Table of Contents
Overview
API Selection Guide
Additional Features
SearchText Examples
SearchNearby Examples
Suggest Examples
Response Handling
Error Handling
Best Practices
Overview
Amazon Location provides three main search APIs:
SearchText - General text-based search ("tacos in Austin")
SearchNearby - Location-proximity search (find restaurants within 5km)
Suggest - Predictive search with partial/misspelled input
GetPlace - Fetch complete details by PlaceId
API Selection Guide
| Use Case | API | Example |
|---|---|---|
| User searches for business/POI by name | SearchText | "Starbucks near downtown" |
| User searches by category | SearchText | "restaurants in Vancouver" |
| Find places near a point on map | SearchNearby | Find gas stations within 10km of current location |
| Type-ahead for place names (not addresses) | Suggest | "star" → Starbucks, Starwood Hotel |
| Type-ahead for addresses | Autocomplete | Use address-input reference instead |
| Get full details after search | GetPlace | Fetch hours, contact info by PlaceId |
Additional Features
Places APIs support an AdditionalFeatures parameter that returns extra details beyond the default response. Request them by adding AdditionalFeatures: ["Contact", "TimeZone", ...] to your API call.
Pricing note: Requesting additional features moves the request into the Advanced pricing bucket, which is priced higher than the default Core bucket. Review Places pricing before enabling them in production.
| Feature | GetPlace | SearchText | SearchNearby | Suggest |
|---|---|---|---|---|
| Contact | Yes | Yes | Yes | No |
| Opening Hours | Yes | Yes | Yes | No |
| Time Zone | Yes | Yes | Yes | Yes |
| Phonemes | Yes | Yes | Yes | Yes |
| Access Points | Yes | Yes | Yes | Yes |
For the full feature-by-API matrix (including Geocode, ReverseGeocode, and Autocomplete), see Additional features.
Contacts and Opening Hours
Contact and opening hours data is available on GetPlace, SearchText, and SearchNearby. Request both by including "Contact" in the AdditionalFeatures array. The valid AdditionalFeatures enum values are TimeZone, Phonemes, Access, and Contact (GetPlace also supports SecondaryAddresses). There is no separate "OpeningHours" enum value — requesting "Contact" returns both contact details and opening hours.
Contacts can include:
Phone number — primary contact number, may include international dialing codes
Email address — primary contact email from the public listing
Website — link to the official site
Opening hours can include:
Regular hours — standard weekly schedule (e.g., Mon–Fri 9 AM–5 PM)
Special hours — holiday or event overrides to the regular schedule
Open now — whether the location is currently open based on local time
// Request contacts and opening hours
const command = new amazonLocationClient.places.SearchTextCommand({
QueryText: "coffee shops in Austin",
AdditionalFeatures: ["Contact"],
MaxResults: 5,
});
const response = await client.send(command);
response.ResultItems.forEach((place) => {
console.log(place.Title);
console.log("Phone:", place.Contacts?.Phones?.[0]?.Value);
console.log("Website:", place.Contacts?.Websites?.[0]?.Value);
console.log("Hours:", place.OpeningHours);
});For more details, see Contacts and opening hours.
SearchText Examples
For exact request parameters and response structure, see the SearchText API Reference.
Basic Text Search
const authHelper = amazonLocationClient.withAPIKey(API_KEY, REGION);
const client = new amazonLocationClient.GeoPlacesClient(
authHelper.getClientConfig(),
);
async function searchPlaces(query) {
try {
const command = new amazonLocationClient.places.SearchTextCommand({
QueryText: query,
MaxResults: 10,
});
const response = await client.send(command);
// Display results
response.ResultItems.forEach((place) => {
console.log(place.Title); // "Starbucks"
console.log(place.Address?.Label); // "123 Main St, Austin, TX"
console.log(place.Position); // [lon, lat]
// Categories are objects: { Id: string, Name: string, LocalizedName?: string, Primary?: boolean }
console.log(place.Categories); // [{ Id: "9000", Name: "Coffee Shop" }, { Id: "5814", Name: "Café" }]
console.log(place.PlaceId); // For fetching details
});
return response.ResultItems;
} catch (error) {
console.error("Search error:", error);
return [];
}
}
// Usage
searchPlaces("coffee shops in Austin");Search with Geographic Bias
// Bias results toward a specific location
async function searchNear(query, biasPosition) {
const command = new amazonLocationClient.places.SearchTextCommand({
QueryText: query,
BiasPosition: biasPosition, // [lon, lat] - prefer results near here
MaxResults: 10,
});
const response = await client.send(command);
return response.ResultItems;
}
// Usage - find tacos near Austin
searchNear("tacos", [-97.7431, 30.2747]);Search with Category Filter
async function searchByCategory(query, categories) {
const command = new amazonLocationClient.places.SearchTextCommand({
QueryText: query,
Filter: {
Categories: categories, // Filter by category codes
},
MaxResults: 20,
});
const response = await client.send(command);
return response.ResultItems;
}
// Usage - find only restaurants
searchByCategory("food near downtown", ["Restaurant"]);Search with Bounding Box
// Restrict search to specific geographic area
async function searchInBounds(query, boundingBox) {
const command = new amazonLocationClient.places.SearchTextCommand({
QueryText: query,
Filter: {
BoundingBox: boundingBox, // [west, south, east, north]
},
MaxResults: 10,
});
const response = await client.send(command);
return response.ResultItems;
}
// Usage - find hotels in downtown Austin area
const austinDowntown = [-97.7535, 30.2586, -97.7327, 30.2747];
searchInBounds("hotels", austinDowntown);SearchNearby Examples
For exact request parameters and response structure, see the SearchNearby API Reference.
Basic Proximity Search
async function searchNearby(position, radius, categories = null) {
const params = {
QueryPosition: position, // [lon, lat]
MaxResults: 20,
};
// Optional: filter by categories
if (categories) {
params.Filter = { Categories: categories };
}
// Optional: specify radius (default is context-dependent)
if (radius) {
params.MaxDistance = radius; // in meters
}
const command = new amazonLocationClient.places.SearchNearbyCommand(params);
try {
const response = await client.send(command);
// Results are already sorted by distance
response.ResultItems.forEach((place) => {
console.log(place.Title);
console.log(place.Distance, "meters away");
console.log(place.Position);
});
return response.ResultItems;
} catch (error) {
console.error("Nearby search error:", error);
return [];
}
}
// Usage - find restaurants within 5km
const userLocation = [-97.7431, 30.2747];
searchNearby(userLocation, 5000, ["Restaurant"]);Find Nearest of Type
// Find single nearest place of a specific type
async function findNearest(position, category) {
const command = new amazonLocationClient.places.SearchNearbyCommand({
QueryPosition: position,
Filter: { Categories: [category] },
MaxResults: 1, // Just the nearest
});
const response = await client.send(command);
if (response.ResultItems.length === 0) {
return null;
}
return response.ResultItems[0];
}
// Usage - find nearest gas station
const nearest = await findNearest([-97.7431, 30.2747], "Gas Station");
if (nearest) {
console.log(`Nearest: ${nearest.Title}, ${nearest.Distance}m away`);
}Search with Map Integration
// Display nearby search results on map
async function showNearbyOnMap(map, position, category) {
const results = await searchNearby(position, 2000, [category]);
// Clear existing markers
document.querySelectorAll(".nearby-marker").forEach((el) => el.remove());
// Add markers for each result
results.forEach((place, index) => {
const marker = new maplibregl.Marker({ color: "#FF0000" })
.setLngLat(place.Position)
.setPopup(
new maplibregl.Popup().setHTML(`
<h4>${place.Title}</h4>
<p>${place.Address?.Label || ""}</p>
<p>${Math.round(place.Distance)}m away</p>
`),
)
.addTo(map);
marker.getElement().classList.add("nearby-marker");
});
// Fit map to show all results
if (results.length > 0) {
const bounds = new maplibregl.LngLatBounds();
results.forEach((place) => bounds.extend(place.Position));
bounds.extend(position); // Include search center
map.fitBounds(bounds, { padding: 50 });
}
}Suggest Examples
For exact request parameters and response structure, see the Suggest API Reference.
Suggest Response Structure
Suggest returns items with a SuggestResultItemType that can be "Place" or "Query":
Place results: Have
item.Place.PlaceId,item.Place.Position,item.Place.Address— usePlaceIdwithGetPlacefor full detailsQuery results: Have
item.Query.QueryText— these are search refinement suggestions, not actual places
Always check item.Place?.PlaceId before attempting to call GetPlace.
Predictive Place Search
// Like Autocomplete but for places/POIs (not just addresses)
async function suggestPlaces(partialQuery, biasPosition = null) {
const params = {
QueryText: partialQuery,
MaxResults: 5,
};
if (biasPosition) {
params.BiasPosition = biasPosition;
}
const command = new amazonLocationClient.places.SuggestCommand(params);
try {
const response = await client.send(command);
response.ResultItems.forEach((item) => {
console.log(item.Title); // "Starbucks"
console.log(item.Place?.PlaceId); // For fetching full details
console.log(item.SuggestResultItemType); // "Place" or "Query"
});
return response.ResultItems;
} catch (error) {
console.error("Suggest error:", error);
return [];
}
}
// Usage - type-ahead for place search
document.getElementById("place-search").addEventListener("input", async (e) => {
const query = e.target.value;
if (query.length < 3) return;
const suggestions = await suggestPlaces(query);
// Display suggestions (similar to autocomplete)
displaySuggestions(suggestions);
});Response Handling
For exact request parameters and response structure for fetching place details, see the GetPlace API Reference.
Parse Place Details
function parsePlaceResult(place) {
return {
id: place.PlaceId,
name: place.Title,
address: place.Address?.Label || "Address not available",
coordinates: {
lat: place.Position[1],
lon: place.Position[0],
},
categories: (place.Categories || []).map((c) => c.Name), // Category is { Id, Name, LocalizedName?, Primary? }
primaryCategory: place.Categories?.find((c) => c.Primary)?.Name,
distance: place.Distance, // Only in SearchNearby results
// Optional fields - check before using
phone: place.Contacts?.Phones?.[0]?.Value,
website: place.Contacts?.Websites?.[0]?.Value,
// Use GetPlace for more details
hasMoreDetails: !!place.PlaceId,
};
}
// Usage
const results = await searchPlaces("coffee");
const parsed = results.map(parsePlaceResult);Fetch Complete Details
// Get full details including hours, contact info
async function getPlaceDetails(placeId) {
const command = new amazonLocationClient.places.GetPlaceCommand({
PlaceId: placeId,
});
try {
const response = await client.send(command);
return {
name: response.Title,
address: response.Address,
position: response.Position,
categories: response.Categories,
contacts: {
phones: response.Contacts?.Phones || [],
websites: response.Contacts?.Websites || [],
emails: response.Contacts?.Emails || [],
},
openingHours: response.OpeningHours || [],
accessPoints: response.AccessPoints || [], // Entrances
timeZone: response.TimeZone,
};
} catch (error) {
console.error("GetPlace error:", error);
return null;
}
}
// Usage - user clicks on search result to see details
async function showPlaceDetails(placeId) {
const details = await getPlaceDetails(placeId);
if (details) {
console.log("Phone:", details.contacts.phones[0]?.Value);
console.log("Hours:", details.openingHours);
}
}Error Handling
Common Errors
async function searchWithErrorHandling(query) {
try {
const command = new amazonLocationClient.places.SearchTextCommand({
QueryText: query,
MaxResults: 10,
});
const response = await client.send(command);
if (response.ResultItems.length === 0) {
// No results found
showMessage("No places found. Try a different search.");
return [];
}
return response.ResultItems;
} catch (error) {
// API errors
if (error.name === "ValidationException") {
showMessage("Invalid search query. Please check your input.");
} else if (error.name === "AccessDeniedException") {
showMessage("API key lacks permission for place search.");
} else if (error.name === "ThrottlingException") {
showMessage("Too many requests. Please wait and try again.");
} else {
showMessage("Search failed. Please try again.");
}
console.error("Search error:", error);
return [];
}
}Retry with Fallback
// Try nearby search, fall back to text search if no results
async function searchWithFallback(query, position) {
// Try nearby search first
let results = await searchNearby(position, 5000);
if (results.length === 0) {
console.log("No nearby results, trying text search...");
// Fall back to text search with position bias
results = await searchNear(query, position);
}
return results;
}Best Practices
Performance
Debounce search input: Wait 300ms after user stops typing
Consider pricing for caching: If storing results beyond temporary session caching, review Places API Stored Pricing and use
IntendedUse: "Storage"parameter.Limit MaxResults: Request only what you'll display (10-20 typically)
Cancel in-flight requests: Cancel previous search when user types new query
User Experience
Show loading state: Spinner or skeleton UI during search
Display distance: Show distance for SearchNearby results
Group by category: Organize results by Categories
Pagination: Load more results as user scrolls
Empty states: Helpful message when no results ("Try different keywords")
Data Quality
Validate coordinates: Ensure Position is valid [lon, lat]
Handle missing fields: Not all places have phone/website/hours
Use PlaceId: Store PlaceId for future GetPlace calls, not full details
Respect Categories: Use Categories array for filtering and display
Search Optimization
Use BiasPosition: Improves relevance for location-aware searches
Combine filters: Use Categories + BoundingBox for precise results
Choose right API: SearchText for queries, SearchNearby for proximity
Prefer SearchNearby: For "near me" features (faster, more relevant)
Error Handling
Handle no results: Suggest alternative searches or expand radius
Show partial results: Display what you have even if some fail
Retry on network errors: Retry once after brief delay
Log for debugging: Log errors with search parameters for troubleshooting
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server, Needs an API key
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Created by
- aws-geospatial
- Publisher
- Cline (Official)
- Distributed by
- Cline
- Source
- cline/skills · skills/amazon-location-service · commit 2637846
- Licence
- MIT No Attribution (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by aws-geospatial or Cline.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download amazon-location-service.zip