- Home
- Skills
- Sickn33
- Antigravity Awesome Skills
- Azure Maps Search Dotnet
azure-maps-search-dotnet_skill
- Python
10.4k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill sickn33/antigravity-awesome-skills --skill azure-maps-search-dotnet- SKILL.md14.9 KB
Overview
This skill provides a concise guide to using the Azure Maps SDK for .NET to add location-based services to .NET applications. It covers installation, authentication methods, core clients (Search, Routing, Rendering, Geolocation, Weather), and common workflows like geocoding, routing, map tiles, IP lookup, and weather retrieval. The content focuses on practical examples and production best practices.
How this skill works
The SDK exposes dedicated clients: MapsSearchClient for geocoding and polygons, MapsRoutingClient for directions and route matrices, MapsRenderingClient for map tiles and static images, MapsGeolocationClient for IP-to-location, and MapsWeatherClient for weather data. Authenticate with a subscription key, SAS token, or Microsoft Entra ID (recommended for production), then call the relevant methods (e.g., GetGeocoding, GetDirections, GetMapTile) to retrieve typed responses. Examples show synchronous and asynchronous patterns and options for batching, traffic-aware routing, and isochrones.
When to use it
- Convert addresses to coordinates or batch-geocode many locations
- Calculate routes, travel time, and route matrices (sync ≤100, async ≤700)
- Render map tiles or static images for UI or exporting
- Determine client location from IP addresses for localization or compliance
- Fetch current weather, hourly/daily forecasts, and severe alerts
- Generate reachable-area polygons (isochrones) for coverage analysis
Best practices
- Use Microsoft Entra ID (DefaultAzureCredential) in production instead of subscription keys
- Batch geocode where possible and cache results to reduce cost and latency
- Respect rate limits: implement exponential backoff and retry logic
- Use async route matrix for large computations and sync for small sets (≤100)
- Include traffic data for accurate ETAs when available and appropriate
Example use cases
- Address autocomplete and geocoding in a checkout or CRM workflow
- Turn-by-turn directions, multi-leg route planning, and distance matrices for logistics apps
- Serve map tiles or static map snapshots for dashboards and reporting
- IP-based country detection to tailor content or enforce geo-restrictions
- Show current weather overlays or fetch forecasts to plan routes or notify users
FAQ
Prefer Microsoft Entra ID (DefaultAzureCredential) for best security and manageability; use SAS tokens for scoped short-term access and subscription keys only for quick tests.
When should I use the async route matrix vs immediate route matrix?
Use the immediate route matrix for up to 100 origin-destination pairs when you need quick synchronous results. Use the async GetRouteMatrix for larger workloads (up to 700 combinations) to avoid timeouts and distribute processing.