amazon-location-service
Skill8 starsChanged 42 days agoApache-2.0View on GitHub
Amazon Location Service. Reference skill (loaded via skill:// from the ios agent).
2 other projects use a version of this.
Adopted by
Most recently taken up by
- awslabs/agent-pluginstheir own version, first seen Oct 13, 2026
- cline/skillstheir own version, first seen Jun 18, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- awslabs/agent-plugins★ 918same name
- cline/skills★ 35same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository17 other files it gives its agents.
- AGENTSAGENTS.md
- amazon-bedrockSkill
- amazon-polly-generativeSkill
- aws-architecture-diagramSkill
- aws-diagram-htmlSkill
- aws-diagram-pngSkill
- aws-serverless-patternsSkill
- cdk-infrastructure-patternsSkill
- cognito-email-migrationSkill
- cognito-passkey-authSkill
- deploy-on-awsSkill
- email-template-renderingSkill
- mcp-tool-discoverySkill
- personal-rules-managementSkill
- react-frontend-patternsSkill
- reinvent-stack-toolkitSkill
- testing-patternsSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 296
Use DepartNow=True for live traffic-aware routing
- Very specific: line 298
Use AccuracyBased position filtering on trackers to reduce noise/costs
- Distinctive: line 300
Use EventBridge for geofence events (serverless, no polling)
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Amazon Location Service
Overview
Amazon Location Service provides maps, routing, geofencing, geocoding, and tracking — all AWS-native, cost-effective, and privacy-preserving. It uses HERE and Esri as data providers under the hood.
Core Capabilities for Navigation Apps
| Feature | API | Use Case |
| Route Calculation | CalculateRoute | Turn-by-turn directions with traffic |
| Geofencing | CreateGeofenceCollection + PutGeofence | Trigger podcast content at locations |
| Geocoding | SearchPlaceIndex | Convert addresses to coordinates |
| Reverse Geocoding | SearchPlaceIndex | Convert coordinates to addresses |
| Place Search | SearchPlaceIndex | Find POIs (restaurants, gas, etc.) |
| Tracking | CreateTracker + BatchUpdateDevicePosition | Track driver position |
| Maps | GetMapTile | Map display (if not using MapKit) |
Route Calculation
Basic Route
import boto3
location = boto3.client('location', region_name='us-east-1')
response = location.calculate_route(
CalculatorName='RoadCastRouteCalculator',
DeparturePosition=[-114.0719, 51.0447], # Calgary [lng, lat]
DestinationPosition=[-115.5708, 51.1784], # Banff [lng, lat]
WaypointPositions=[
[-114.4632, 51.0486], # Cochrane
],
IncludeLegGeometry=True,
TravelMode='Car',
DepartNow=True,
CarModeOptions={
'AvoidFerries': False,
'AvoidTolls': False
}
)
# Response includes:
# - Legs[].Steps[] (turn-by-turn instructions)
# - Legs[].Geometry.LineString (polyline for map)
# - Summary.Distance, Summary.DurationSeconds
# - Summary.DataSource (HERE or Esri)Traffic-Aware Routing
response = location.calculate_route(
CalculatorName='RoadCastRouteCalculator',
DeparturePosition=[-114.0719, 51.0447],
DestinationPosition=[-115.5708, 51.1784],
DepartNow=True, # Uses live traffic
# OR
DepartureTime=datetime(2026, 8, 1, 8, 0, 0), # Predictive traffic
OptimizeFor='FastestRoute' # vs 'ShortestRoute'
)
# Traffic-aware ETA
eta_seconds = response['Summary']['DurationSeconds']Route with Avoidances
response = location.calculate_route(
CalculatorName='RoadCastRouteCalculator',
DeparturePosition=start,
DestinationPosition=end,
TravelMode='Car',
CarModeOptions={
'AvoidFerries': True,
'AvoidTolls': True
}
)Geofencing (Content Triggers)
Create Geofence Collection
location.create_geofence_collection(
CollectionName='RoadCastContentTriggers',
PricingPlan='RequestBasedUsage'
)Add Geofences (Batch)
location.batch_put_geofence(
CollectionName='RoadCastContentTriggers',
Entries=[
{
'GeofenceId': 'segment-001-banff-springs',
'Geometry': {
'Circle': {
'Center': [-115.5560, 51.1635],
'Radius': 2000 # 2km radius trigger
}
}
},
{
'GeofenceId': 'segment-002-castle-mountain',
'Geometry': {
'Circle': {
'Center': [-115.9225, 51.2641],
'Radius': 3000
}
}
}
]
)Evaluate Position Against Geofences
response = location.batch_evaluate_geofences(
CollectionName='RoadCastContentTriggers',
DevicePositionUpdates=[
{
'DeviceId': 'trip-abc-user-123',
'Position': [-115.5400, 51.1600],
'SampleTime': datetime.now()
}
]
)
# Returns: which geofences were ENTERED or EXITEDEventBridge Integration (Serverless Geofence Events)
# When a device enters/exits a geofence, Location Service emits an EventBridge event:
# Source: aws.geo
# Detail-type: "Location Geofence Event"
# Detail: { EventType: "ENTER"/"EXIT", GeofenceId: "...", DeviceId: "..." }
# CDK rule:
from aws_cdk import aws_events as events, aws_events_targets as targets
events.Rule(self, 'GeofenceEntryRule',
event_pattern=events.EventPattern(
source=['aws.geo'],
detail_type=['Location Geofence Event'],
detail={'EventType': ['ENTER']}
),
targets=[targets.LambdaFunction(content_trigger_lambda)]
)Place Search (POI Discovery)
Search Nearby
response = location.search_place_index_for_position(
IndexName='RoadCastPlaceIndex',
Position=[-115.5708, 51.1784],
MaxResults=10,
Language='en'
)
for result in response['Results']:
place = result['Place']
print(f"{place['Label']} - {place['Categories']}")Search by Text
response = location.search_place_index_for_text(
IndexName='RoadCastPlaceIndex',
Text='coffee shop near Banff',
BiasPosition=[-115.5708, 51.1784],
MaxResults=5,
FilterCategories=['CoffeeShop', 'Restaurant']
)Category Filters (for suggested stops)
Available categories: Restaurant, CoffeeShop, GasStation, Hotel, Park, Museum, Hospital, Pharmacy, ATM, Shopping, Entertainment, Parking
Device Tracking
# Update driver position (called from mobile app every 30 seconds)
location.batch_update_device_position(
TrackerName='RoadCastDriverTracker',
Updates=[{
'DeviceId': 'trip-abc-user-123',
'Position': [-115.2000, 51.1500],
'SampleTime': datetime.now(),
'PositionProperties': {
'speed': '95', # km/h
'heading': '270' # degrees
}
}]
)Link Tracker to Geofence Collection
location.associate_tracker_consumer(
TrackerName='RoadCastDriverTracker',
ConsumerArn='arn:aws:geo:us-east-1:123456789:geofence-collection/RoadCastContentTriggers'
)
# Now position updates automatically evaluate against geofences!CDK Infrastructure
from aws_cdk import (
aws_location as location,
aws_iam as iam,
)
# Route Calculator
route_calc = location.CfnRouteCalculator(self, 'RouteCalc',
calculator_name='RoadCastRouteCalculator',
data_source='Here', # or 'Esri'
pricing_plan='RequestBasedUsage'
)
# Place Index (for geocoding + POI search)
place_index = location.CfnPlaceIndex(self, 'PlaceIndex',
index_name='RoadCastPlaceIndex',
data_source='Here',
pricing_plan='RequestBasedUsage',
data_source_configuration={
'intendedUse': 'Storage' # 'SingleUse' if not caching results
}
)
# Geofence Collection
geofence_collection = location.CfnGeofenceCollection(self, 'GeofenceCollection',
collection_name='RoadCastContentTriggers',
pricing_plan='RequestBasedUsage'
)
# Tracker
tracker = location.CfnTracker(self, 'DriverTracker',
tracker_name='RoadCastDriverTracker',
pricing_plan='RequestBasedUsage',
position_filtering='AccuracyBased' # Filters GPS noise
)
# Associate tracker with geofence collection
location.CfnTrackerConsumer(self, 'TrackerConsumer',
tracker_name=tracker.tracker_name,
consumer_arn=geofence_collection.attr_collection_arn
)iOS Client Integration
On the iOS side, you do NOT use Amazon Location SDK for map display (you use MapKit). But you DO call Amazon Location APIs for:
- Route calculation (via API Gateway -> Lambda -> Location Service)
- Position updates (via API Gateway -> Lambda -> Tracker)
- Geofence evaluation results come back via push notification or WebSocket
The mobile app sends position updates to your backend API every 30 seconds. The backend forwards to Location Service tracker, which auto-evaluates geofences and fires EventBridge events.
Free Tier
- Routes: 10,000 route calculations/month free (first 3 months)
- Geocoding: 10,000 requests/month free (first 3 months)
- Geofencing: 100,000 geofence evaluations/month free (first 3 months)
- Tracking: 200,000 position updates/month free (first 3 months)
- Maps: 500,000 map tile requests/month free (first 3 months)
After free tier:
- Routes: $0.50 per 1,000 requests
- Geofencing: $0.05 per 1,000 evaluations
- Tracking: $0.05 per 1,000 positions
Best Practices
- Use
DepartNow=Truefor live traffic-aware routing - Batch geofence puts (up to 10 per call) for efficiency
- Use
AccuracyBasedposition filtering on trackers to reduce noise/costs - Cache route results locally (routes don't change frequently)
- Use EventBridge for geofence events (serverless, no polling)
- Coordinates are ALWAYS [longitude, latitude] (GeoJSON order) — not [lat, lng]!
- HERE provider gives better road-level accuracy; Esri gives better POI coverage
- For offline: pre-calculate and cache the full route response client-side
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

