You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/azure-maps/how-to-use-best-practices-for-routing.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ The Route Directions and Route Matrix APIs in Azure Maps [Route service] can be
30
30
31
31
For more information about the coverage of the Route service, see [Routing Coverage].
32
32
33
-
This article uses the [Postman]application to build REST calls, but you can choose any API development environment.
33
+
You can use any API development environment such as [Postman]or [bruno]to run the HTTP request samples shown in this article or to build REST calls.
34
34
35
35
## Choose between Route Directions and Matrix Routing
36
36
@@ -47,7 +47,7 @@ Consider calling Matrix Routing API if your scenario is to:
47
47
48
48
* Calculate the travel time or distance between a set of origins and destinations. For example, you have 12 drivers and you need to find the closest available driver to pick up the food delivery from the restaurant.
49
49
* Sort potential routes by their actual travel distance or time. The Matrix API returns only travel times and distances for each origin and destination combination.
50
-
* Cluster data based on travel time or distances. For example, your company has 50 employees, find all employees that live within 20 minute Drive Time from your office.
50
+
* Cluster data based on travel time or distances. For example, your company has 50 employees, find all employees that live within 20 minute drive time from your office.
51
51
52
52
Here's a comparison to show some capabilities of the Route Directions and Matrix APIs:
Copy file name to clipboardExpand all lines: articles/azure-maps/how-to-use-best-practices-for-search.md
+12-15Lines changed: 12 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ This article explains how to apply sound practices when you call data from Azure
27
27
* An [Azure Maps account]
28
28
* A [subscription key]
29
29
30
-
This article uses the [Postman]application to build REST calls, but you can choose any API development environment.
30
+
You can use any API development environment such as [Postman]or [bruno]to run the HTTP request samples shown in this article or to build REST calls.
31
31
32
32
## Best practices to geocode addresses
33
33
@@ -126,7 +126,6 @@ Use the `language` parameter to set the language for the returned search results
126
126
127
127
For more information, see [Azure Maps supported languages].
128
128
129
-
130
129
### Use predictive mode (automatic suggestions)
131
130
132
131
To find more matches for partial queries, set the `typeahead` parameter to `true`. This query is interpreted as a partial input, and the search enters predictive mode. If you don't set the `typeahead` parameter to `true`, then the service assumes that all relevant information has been passed in.
To find cross street addresses, you must encode the URI to handle special characters in the address. Consider this address example: *1st Avenue & Union Street, Seattle*. Here, encode the ampersand character (`&`) before you send the request.
By using the Search POI API, you can look for airports by using their official code. For example, you can use *SEA* to find the Seattle-Tacoma International Airport:
@@ -973,19 +970,19 @@ To learn more, please see:
973
970
> [!div class="nextstepaction"]
974
971
> [Search service API documentation](/rest/api/maps/search?view=rest-maps-1.0&preserve-view=true)
Copy file name to clipboardExpand all lines: articles/azure-maps/tutorial-iot-hub-maps.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ titleSuffix: Microsoft Azure Maps
4
4
description: Tutorial on how to Integrate IoT Hub with Microsoft Azure Maps service APIs
5
5
author: farazgis
6
6
ms.author: fsiddiqui
7
-
ms.date: 09/14/2023
7
+
ms.date: 08/14/2024
8
8
ms.topic: tutorial
9
9
ms.service: azure-maps
10
10
ms.subservice: spatial
@@ -36,11 +36,11 @@ If you don't have an Azure subscription, create a [free account] before you begi
36
36
* The [rentalCarSimulation] C# project
37
37
38
38
> [!TIP]
39
-
> You can download the entire [rentalCarSimulation] C# project from GitHub as a single ZIP file by going to [the root of the sample] and selecting the green **<> Code** button, then **Download ZIP**.
39
+
> You can download the entire [rentalCarSimulation] C# project from GitHub as a single ZIP file by going to [the root of the sample] and selecting the green **Code** button, then **Download ZIP**.
40
40
41
-
This tutorial uses the [Postman] application, but you can choose a different API development environment.
41
+
This tutorial uses the [bruno] application, but you can choose a different API development environment.
42
42
43
-
>[!IMPORTANT]
43
+
>[!IMPORTANT]
44
44
> In the URL examples, replace `{Your-Azure-Maps-Subscription-key}` with your Azure Maps subscription key.
45
45
46
46
## Use case: rental car tracking
@@ -150,7 +150,7 @@ Now, set up your Azure function.
150
150
151
151
1. After the app is created, you add a function to it. Go to the function app. Select the **Create in Azure Portal** button.
152
152
153
-
>[!IMPORTANT]
153
+
> [!IMPORTANT]
154
154
> The **Azure Event ***Hub*** Trigger** and the **Azure Event ***Grid*** Trigger** templates have similar names. Make sure you select the **Azure Event ***Grid*** Trigger** template.
155
155
156
156
:::image type="content" source="./media/tutorial-iot-hub-maps/function-create.png" alt-text="Screenshot of create a function in Azure Portal.":::
@@ -196,7 +196,7 @@ In your example scenario, you only want to receive messages when the rental car
196
196
197
197
:::image type="content" source="./media/tutorial-iot-hub-maps/hub-filter.png" alt-text="Screenshot of filter routing messages.":::
198
198
199
-
>[!TIP]
199
+
>[!TIP]
200
200
>There are various ways to query IoT device-to-cloud messages. To learn more about message routing syntax, see [IoT Hub message routing].
201
201
202
202
## Send telemetry data to IoT Hub
@@ -264,6 +264,7 @@ To learn more about how to send device-to-cloud telemetry, and the other way aro
[create a storage account]: ../storage/common/storage-account-create.md?tabs=azure-portal
269
270
[Create an Azure storage account]: #create-an-azure-storage-account
@@ -278,7 +279,6 @@ To learn more about how to send device-to-cloud telemetry, and the other way aro
278
279
[IoT Plug and Play]: ../iot/overview-iot-plug-and-play.md
279
280
[geofence JSON data file]: https://raw.githubusercontent.com/Azure-Samples/iothub-to-azure-maps-geofencing/master/src/Data/geofence.json?token=AKD25BYJYKDJBJ55PT62N4C5LRNN4
280
281
[Plug and Play schema for geospatial data]: https://github.com/Azure/opendigitaltwins-dtdl/blob/master/DTDL/v1-preview/schemas/geospatial.md
281
-
[Postman]: https://www.postman.com/
282
282
[register a new device in the IoT hub]: ../iot-hub/create-connect-device.md
0 commit comments