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/migrate-from-google-maps-web-app.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -81,7 +81,7 @@ The table lists key API features in the Google Maps V3 JavaScript SDK and the su
81
81
82
82
The following are some key differences between the Google Maps and Azure Maps Web SDKs, to be aware of:
83
83
84
-
* In addition to providing a hosted endpoint for accessing the Azure Maps Web SDK, an npm package is available. Embed the Web SDK package into apps. For more information, see this [documentation](how-to-use-map-control.md). This package also includes TypeScript definitions.
84
+
* In addition to providing a hosted endpoint for accessing the Azure Maps Web SDK, an npm package is available. For more information on how to Embed the Web SDK package into apps, see [Use the Azure Maps mapcontrol]. This package also includes TypeScript definitions.
85
85
* You first need to create an instance of the Map class in Azure Maps. Wait for the maps `ready` or `load` event to fire before programmatically interacting with the map. This order ensures that all the map resources have been loaded and are ready to be accessed.
86
86
* Both platforms use a similar tiling system for the base maps. The tiles in Google Maps are 256 pixels in dimension; however, the tiles in Azure Maps are 512 pixels in dimension. To get the same map view in Azure Maps as Google Maps, subtract Google Maps zoom level by the number one in Azure Maps.
87
87
* Coordinates in Google Maps are referred to as `latitude,longitude`, while Azure Maps uses `longitude,latitude`. The Azure Maps format is aligned with the standard `[x, y]`, which is followed by most GIS platforms.
@@ -439,7 +439,7 @@ For a Symbol layer, add the data to a data source. Attach the data source to the
439
439
*[Create a data source]
440
440
*[Add a Symbol layer]
441
441
*[Add a Bubble layer]
442
-
*[Cluster point data]
442
+
*[Clustering point data in the Web SDK]
443
443
*[Add HTML Markers]
444
444
*[Use data-driven style expressions]
445
445
*[Symbol layer icon options]
@@ -956,7 +956,7 @@ GeoJSON is the base data type in Azure Maps. Import it into a data source using
956
956
957
957
*[Add a Symbol layer]
958
958
*[Add a Bubble layer]
959
-
*[Cluster point data]
959
+
*[Clustering point data in the Web SDK]
960
960
*[Use data-driven style expressions]
961
961
962
962
### Marker clustering
@@ -1053,7 +1053,7 @@ The `DataSource` class has the following helper function for accessing additiona
1053
1053
|`getClusterExpansionZoom(clusterId: number)`| Promise<number>| Calculates a zoom level at which the cluster starts expanding or break apart. |
1054
1054
|`getClusterLeaves(clusterId: number, limit: number, offset: number)`| Promise<Array<Feature<Geometry, any>\| Shape>>| Retrieves all points in a cluster. Set the `limit` to return a subset of the points, and use the `offset` to page through the points. |
1055
1055
1056
-
When rendering clustered data on the map, it's often best to use two or more layers. The following example uses three layers. A bubble layer for drawing scaled colored circles based on the size of the clusters. A symbol layer to render the cluster size as text. And, it uses a second symbol layer for rendering the unclustered points. There are many other ways to render clustered data. For more information, see the [Cluster point data] documentation.
1056
+
When rendering clustered data on the map, it's often best to use two or more layers. The following example uses three layers. A bubble layer for drawing scaled colored circles based on the size of the clusters. A symbol layer to render the cluster size as text. And, it uses a second symbol layer for rendering the unclustered points. For more information on other ways to render clustered data, see [Clustering point data in the Web SDK].
1057
1057
1058
1058
Directly import GeoJSON data using the `importDataFromUrl` function on the `DataSource` class, inside Azure Maps map.
1059
1059
@@ -1157,7 +1157,7 @@ Directly import GeoJSON data using the `importDataFromUrl` function on the `Data
1157
1157
1158
1158
*[Add a Symbol layer]
1159
1159
*[Add a Bubble layer]
1160
-
*[Cluster point data]
1160
+
*[Clustering point data in the Web SDK]
1161
1161
*[Use data-driven style expressions]
1162
1162
1163
1163
### Add a heat map
@@ -1789,7 +1789,7 @@ Learn more about migrating to Azure Maps:
1789
1789
[Create a data source]: create-data-source-web-sdk.md
1790
1790
[Add a Symbol layer]: map-add-pin.md
1791
1791
[Add a Bubble layer]: map-add-bubble-layer.md
1792
-
[Cluster point data]: clustering-point-data-web-sdk.md
1792
+
[Clustering point data in the Web SDK]: clustering-point-data-web-sdk.md
0 commit comments