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/display-feature-information-android.md
+21-11Lines changed: 21 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,9 +52,9 @@ source.add(feature)
52
52
53
53
::: zone-end
54
54
55
-
See the [Create a data source](create-data-source-android-sdk.md) documentation for ways to create and add data to the map.
55
+
For more information on how to create and add data to the map, see [Create a data source].
56
56
57
-
When a user interacts with a feature on the map, events can be used to react to those actions. A common scenario is to display a message made of the metadata properties of a feature the user interacted with. The `OnFeatureClick` event is the main event used to detect when the user tapped a feature on the map. There's also an `OnLongFeatureClick` event. When adding the `OnFeatureClick` event to the map, it can be limited to a single layer by passing in the ID of a layer to limit it to. If no layer ID is passed in, tapping any feature on the map, regardless of which layer it is in, would fire this event. The following code creates a symbol layer to render point data on the map, then adds an `OnFeatureClick` event and limits it to this symbol layer.
57
+
When a user interacts with a feature on the map, events can be used to react to those actions. A common scenario is to display a message made of the metadata properties of a feature the user interacted with. The `OnFeatureClick` event is the main event used to detect when the user tapped a feature on the map. There's also an `OnLongFeatureClick` event. When the `OnFeatureClick` event is added to the map, it can be limited to a single layer by passing in the ID of a layer to limit it to. If no layer ID is passed in, tapping any feature on the map, regardless of which layer it is in, would fire this event. The following code creates a symbol layer to render point data on the map, then adds an `OnFeatureClick` event and limits it to this symbol layer.
58
58
59
59
::: zone pivot="programming-language-java-android"
In addition to toast messages, There are many other ways to present the metadata properties of a feature, such as:
144
144
145
-
-[Snackbar widget](https://developer.android.com/training/snackbar/showing.html) - `Snackbars` provide lightweight feedback about an operation. They show a brief message at the bottom of the screen on mobile and lower left on larger devices. `Snackbars` appear above all other elements on screen and only one can be displayed at a time.
146
-
-[Dialogs](https://developer.android.com/guide/topics/ui/dialogs) - A dialog is a small window that prompts the user to make a decision or enter additional information. A dialog doesn't fill the screen and is normally used for modal events that require users to take an action before they can continue.
147
-
- Add a [Fragment](https://developer.android.com/guide/components/fragments) to the current activity.
145
+
-[Snackbar widget] - `Snackbars` provide lightweight feedback about an operation. They show a brief message at the bottom of the screen on mobile and lower left on larger devices. `Snackbars` appear above all other elements on screen and only one can be displayed at a time.
146
+
-[Dialogs] - A dialog is a small window that prompts the user to make a decision or enter additional information. A dialog doesn't fill the screen and is normally used for modal events that require users to take an action before they can continue.
147
+
- Add a [Fragment] to the current activity.
148
148
- Navigate to another activity or view.
149
149
150
150
## Display a popup
@@ -285,19 +285,29 @@ The following screen capture shows popups appearing when features are clicked an
285
285
To add more data to your map:
286
286
287
287
> [!div class="nextstepaction"]
288
-
> [React to map events](android-map-events.md)
288
+
> [React to map events]
289
289
290
290
> [!div class="nextstepaction"]
291
-
> [Create a data source](create-data-source-android-sdk.md)
291
+
> [Create a data source]
292
292
293
293
> [!div class="nextstepaction"]
294
-
> [Add a symbol layer](how-to-add-symbol-to-android-map.md)
294
+
> [Add a symbol layer]
295
295
296
296
> [!div class="nextstepaction"]
297
-
> [Add a bubble layer](map-add-bubble-layer-android.md)
297
+
> [Add a bubble layer]
298
298
299
299
> [!div class="nextstepaction"]
300
-
> [Add a line layer](android-map-add-line-layer.md)
300
+
> [Add a line layer]
301
301
302
302
> [!div class="nextstepaction"]
303
-
> [Add a polygon layer](how-to-add-shapes-to-android-map.md)
303
+
> [Add a polygon layer]
304
+
305
+
[Create a data source]: create-data-source-android-sdk.md
See the [Create a data source](create-data-source-ios-sdk.md) documentation for ways to create and add data to the map.
31
+
For more information on how to create and add data to the map, see [Create a data source].
32
32
33
-
When a user interacts with a feature on the map, events can be used to react to those actions. A common scenario is to display a message made of the metadata properties of a feature the user interacted with. The `azureMap(_:didTapOn:)` event is the main event used to detect when the user tapped a feature on the map. There's also an `azureMap(_:didLongPressOn:)` event. When adding a delegate to the map, it can be limited to a single layer by passing in the ID of a layer to limit it to. If no layer ID is passed in, tapping any feature on the map, regardless of which layer it is in, would fire this event. The following code creates a symbol layer to render point data on the map, then adds a delegate, limited to this symbol layer, which handles the `azureMap(_:didTapOn:)` event.
33
+
When a user interacts with a feature on the map, events can be used to react to those actions. A common scenario is to display a message made of the metadata properties of a feature the user interacted with. The `azureMap(_:didTapOn:)` event is the main event used to detect when the user tapped a feature on the map. There's also an `azureMap(_:didLongPressOn:)` event. When a delegate is added to the map, it can be limited to a single layer by passing in the ID of a layer to limit it to. If no layer ID is passed in, tapping any feature on the map, regardless of which layer it is in, would fire this event. The following code creates a symbol layer to render point data on the map, then adds a delegate, limited to this symbol layer, which handles the `azureMap(_:didTapOn:)` event.
The following screen capture shows popups appearing when features are tapped and staying anchored to their specified location on the map as it moves.
177
177
178
-
:::image type="content" source="./media/ios-sdk/display-feature-information/ios-popup.gif" alt-text="Animation of a popup being displayed and the map moved with the popup anchored to a position on the map.":::
178
+
:::image type="content" source="./media/ios-sdk/display-feature-information/ios-popup.gif" alt-text="Animation of a popup being displayed with the map moving while the popup is anchored.":::
179
179
180
180
## Additional information
181
181
@@ -187,3 +187,5 @@ To add more data to your map:
187
187
-[Add a bubble layer](add-bubble-layer-map-ios.md)
188
188
-[Add a line layer](add-line-layer-map-ios.md)
189
189
-[Add a polygon layer](add-polygon-layer-map-ios.md)
190
+
191
+
[Create a data source]: create-data-source-ios-sdk.md
0 commit comments