Loading...

Azure Maps REST SDKs

Azure Maps REST SDKs

Azure Maps is more than just a Map on your website. It is a complete enterprise solution for location-aware solutions. For example, you can do (reverse) geocoding of customer addresses and use an isochrone to find out withs customers a close to your store or get weather conditions for all your past sales data to know withs products sell best by rain or hot weather or get the correct time-zone for your customer by translating an IP-address to a location and get the time-zone information, or you need to know what the travel time is between two or more locations. So many scenarios and use cases you can make location aware with Azure Maps.

 

You can call the Azure Maps REST APIs directly from any programming language, which is not difficult but always needs extra work. With the introduction of the public preview Azure Maps REST SDKs for C# (.NET), Java, Phyton, and TypeScript (Node.js), you can earlier use the power of Azure Maps in your backend without the hassle of calling the APIs the correct way.

 

To give you a simple example in C#, we are searching for a Starbucks close to a customer's location in Seattle. Before we can begin, you need an Azure Maps key; see here how to get a free Azure Maps key.

 

The following code snippet creates a console program MapsDemo with .NET 7.0. You can use any .NET standard 2.0-compatible version as the framework.

 

dotnet add package Azure.Maps.Search --prerelease

 

The following code snippet demonstrates how, in a simple console application, to import the Azure.Maps.Search package and perform a fuzzy search on “Starbucks” near Seattle. In the Program.cs file add the following code:

 

using Azure; using Azure.Core.GeoJson; using Azure.Maps.Search; using Azure.Maps.Search.Models; // Use Azure Maps subscription key authentication var credential = new AzureKeyCredential("Azure_Maps_Subscription_key"); var client = new MapsSearchClient(credential); SearchAddressResult searchResult = client.FuzzySearch( "Starbucks", new FuzzySearchOptions { Coordinates = new GeoPosition(-122.31, 47.61), Language = SearchLanguage.EnglishUsa }); // Print the search results foreach (var result in searchResult.Results) { Console.WriteLine($""" * {result.PointOfInterest.Name} {result.Address.StreetNumber} {result.Address.StreetName} {result.Address.Municipality} {result.Address.CountryCode} {result.Address.PostalCode} Coordinate: ({result.Position.Latitude:F4}, {result.Position.Longitude:F4}) """); }

 

In the above code snippet, you create a MapsSearchClient object using your Azure credentials, then use that Search Client's FuzzySearch method passing in the point of interest (POI) name "Starbucks" and coordinates GeoPosition(-122.31, 47.61). This all gets wrapped up by the SDK and sent to the Azure Maps REST endpoints. When the search results are returned, they're written out to the screen.

 

To run your application, go to the project folder and execute dotnet run in PowerShell.

 

More information you can read in our Azure Maps REST SDK Developer Guide. Happy coding!

Published on:

Learn more
Azure Maps articles
Azure Maps articles

Azure Maps articles

Share post:

Related posts

Fabric Mirroring for Azure Cosmos DB: Public Preview Refresh Now Live with New Features

We’re thrilled to announce the latest refresh of Fabric Mirroring for Azure Cosmos DB, now available with several powerful new features that e...

1 day ago

Power Platform – Use Azure Key Vault secrets with environment variables

We are announcing the ability to use Azure Key Vault secrets with environment variables in Power Platform. This feature will reach general ava...

1 day ago

Validating Azure Key Vault Access Securely in Fabric Notebooks

Working with sensitive data in Microsoft Fabric requires careful handling of secrets, especially when collaborating externally. In a recent cu...

1 day ago

Azure Developer CLI (azd) – May 2025

This post announces the May release of the Azure Developer CLI (`azd`). The post Azure Developer CLI (azd) – May 2025 appeared first on ...

2 days ago

Azure Cosmos DB with DiskANN Part 4: Stable Vector Search Recall with Streaming Data

Vector Search with Azure Cosmos DB  In Part 1 and Part 2 of this series, we explored vector search with Azure Cosmos DB and best practices for...

2 days ago

General Availability for Data API in vCore-based Azure Cosmos DB for MongoDB

Title: General Availability for Data API in vCore-based Azure Cosmos DB for MongoDB We’re excited to announce the general availability of the ...

2 days ago

Efficiently and Elegantly Modeling Embeddings in Azure SQL and SQL Server

Storing and querying text embeddings in a database it might seem challenging, but with the right schema design, it’s not only possible, ...

3 days ago
Stay up to date with latest Microsoft Dynamics 365 and Power Platform news!
* Yes, I agree to the privacy policy