Skip to content

Commit addf2fc

Browse files
authored
Merge pull request #102022 from farah-alyasari/freshnessreport5
Freshnessreport5
2 parents e89e664 + 8d7ffeb commit addf2fc

File tree

6 files changed

+534
-148
lines changed

6 files changed

+534
-148
lines changed

articles/azure-maps/how-to-render-custom-data.md

Lines changed: 19 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Render custom data on a raster map | Microsoft Azure Maps
33
description: In this article, you'll learn how to render custom data on a raster map by using Microsoft Azure Maps static image Service.
44
author: walsehgal
55
ms.author: v-musehg
6-
ms.date: 07/29/2019
6+
ms.date: 01/23/2020
77
ms.topic: conceptual
88
ms.service: azure-maps
99
services: azure-maps
@@ -24,7 +24,7 @@ To render custom pushpins, labels, and geometry overlays, you can use the Postma
2424

2525
### Create an Azure Maps account
2626

27-
To complete the procedures in this article, you first need to create an Azure Maps account and get you maps account key. Follow instructions in [Create an account](quick-demo-map-app.md#create-an-account-with-azure-maps) to create an Azure Maps account subscription and follow the steps in [get primary key](quick-demo-map-app.md#get-the-primary-key-for-your-account) to get the primary key for your account. For more details on authentication in Azure Maps, see [manage authentication in Azure Maps](./how-to-manage-authentication.md).
27+
To complete the procedures in this article, you first need to create an Azure Maps account and get your maps account key. Follow instructions in [Create an account](quick-demo-map-app.md#create-an-account-with-azure-maps) to create an Azure Maps account subscription and follow the steps in [get primary key](quick-demo-map-app.md#get-the-primary-key-for-your-account) to get the primary key for your account. For more information on authentication in Azure Maps, see [manage authentication in Azure Maps](./how-to-manage-authentication.md).
2828

2929

3030
## Render pushpins with labels and a custom image
@@ -38,7 +38,7 @@ To render pushpins with labels and a custom image, complete these steps:
3838

3939
1. Create a collection in which to store the requests. In the Postman app, select **New**. In the **Create New** window, select **Collection**. Name the collection and select the **Create** button.
4040

41-
2. To create the request, select **New** again. In the **Create New** window, select **Request**. Enter a **Request name** for the pushpins, select the collection you created in the previous step as the location in which to save the request, and then select **Save**.
41+
2. To create the request, select **New** again. In the **Create New** window, select **Request**. Enter a **Request name** for the pushpins. Select the collection you created in the previous step as the location in which to save the request, and then select **Save**.
4242

4343
![Create a request in Postman](./media/how-to-render-custom-data/postman-new.png)
4444

@@ -137,21 +137,21 @@ You can also obtain the path and pin location information by using the [Data Upl
137137
https://atlas.microsoft.com/mapData/{uploadStatusId}/status?api-version=1.0
138138
```
139139

140-
5. Copy your status URI and append the subscription-key parameter to it with its value being your Azure Maps account subscription key that you used to upload the data. The status URI format should look like the one below:
140+
5. Copy your status URI and append the subscription-key parameter to it with the value of your Azure Maps account subscription key. Use the same account subscription key that you used to upload the data. The status URI format should look like the one below:
141141

142142
```HTTP
143143
https://atlas.microsoft.com/mapData/{uploadStatusId}/status?api-version=1.0&subscription-key={Subscription-key}
144144
```
145145

146-
6. To get the, udId open a new tab in the Postman app and select GET HTTP method on the builder tab and make a GET request at the status URI. If your data upload was successful, you will receive a udId in the response body. Copy the udId.
146+
6. To get the udId, open a new tab in the Postman app and select GET HTTP method on the builder tab and make a GET request at the status URI. If your data upload was successful, you will receive a udId in the response body. Copy the udId.
147147

148148
```JSON
149149
{
150150
"udid" : "{udId}"
151151
}
152152
```
153153

154-
7. Use the `udId` value received from the Data Upload API to render features on the map. To do so, open a new tab in the collection you created in the preceding section. Select the GET HTTP method on the builder tab and enter this URL to make a GET request:
154+
7. Use the `udId` value received from the Data Upload API to render features on the map. To do so, open a new tab in the collection you created in the preceding section. Select the GET HTTP method on the builder tab, replace the {subscription-key} and {udId} with your values, and enter this URL to make a GET request:
155155

156156
```HTTP
157157
https://atlas.microsoft.com/map/static/png?subscription-key={subscription-key}&api-version=1.0&layer=basic&style=main&zoom=12&center=-73.96682739257812%2C40.78119135317995&pins=default|la-35+50|ls12|lc003C62|co9B2F15||'Times Square'-73.98516297340393 40.758781646381024|'Central Park'-73.96682739257812 40.78119135317995&path=lc0000FF|fc0000FF|lw3|la0.80|fa0.30||udid-{udId}
@@ -187,7 +187,7 @@ You can modify the appearance of a polygon by using style modifiers with the [pa
187187
> The procedure in this section requires an Azure Maps account in pricing tier S1.
188188
189189
190-
You can make pushpins and their labels larger or smaller by using the `sc` scale style modifier. This modifier takes a value that's greater than zero. A value of 1 is the standard scale. Values larger than 1 will make the pins larger, and values smaller than 1 will make them smaller. For more information about style modifiers, see [static image service path parameters](https://docs.microsoft.com/rest/api/maps/render/getmapimage#uri-parameters).
190+
You can modify the appearance of the pins by adding style modifiers. For example, to make pushpins and their labels larger or smaller, use the `sc` "scale style" modifier. This modifier takes a value that's greater than zero. A value of 1 is the standard scale. Values larger than 1 will make the pins larger, and values smaller than 1 will make them smaller. For more information about style modifiers, see [static image service path parameters](https://docs.microsoft.com/rest/api/maps/render/getmapimage#uri-parameters).
191191
192192
193193
Follow these steps to render a circle and pushpins with custom labels:
@@ -202,6 +202,18 @@ Follow these steps to render a circle and pushpins with custom labels:
202202
203203
![Render a circle with custom pushpins](./media/how-to-render-custom-data/circle-custom-pins.png)
204204
205+
2. To change the color of the pushpins from the last step, change the "co" style modifier. Look at `pins=default|la15+50|al0.66|lc003C62|co002D62|`, the current color would be specified as #002D62 in CSS. Let's say you want to change it to #41d42a. Write the new color value after the "co" specifier, like this: `pins=default|la15+50|al0.66|lc003C62|co41D42A|`. Make a new GET request:
206+
207+
```HTTP
208+
https://atlas.microsoft.com/map/static/png?api-version=1.0&style=main&layer=basic&zoom=14&height=700&Width=700&center=-122.13230609893799,47.64599069048016&path=lcFF0000|lw2|la0.60|ra1000||-122.13230609893799 47.64599069048016&pins=default|la15+50|al0.66|lc003C62|co41D42A||'Microsoft Corporate Headquarters'-122.14131832122801 47.64690503939462|'Microsoft Visitor Center'-122.136828 47.642224|'Microsoft Conference Center'-122.12552547454833 47.642940335653996|'Microsoft The Commons'-122.13687658309935 47.64452336193245&subscription-key={subscription-key}
209+
```
210+
211+
Here's the response image after changing the colors of the pins:
212+
213+
![Render a circle with updated pushpins](./media/how-to-render-custom-data/circle-updated-pins.png)
214+
215+
Similarly, you can change, add, and remove other style modifiers.
216+
205217
## Next steps
206218
207219

0 commit comments

Comments
 (0)