Cette page explique comment contrôler le comportement d'un repère en cas de collision.
Définir le comportement d'un repère en cas de collision
Le comportement en cas de collision définit comment un repère s'affiche s'il entre en collision avec un autre repère (c'est-à-dire s'ils se chevauchent). La façon dont vous créez un repère avancé détermine comment il s'affiche en cas de collision :
Les repères avancés créés à l'aide de BitmapDescriptorFactory sont appelés "repères bitmap". Ils sont dessinés par la carte principale.
Tous les autres repères avancés, y compris ceux créés à l'aide de la méthode AdvancedMarkerOptions.iconView(), sont appelés "repères de vue" et sont dessinés sur un calque au-dessus de la carte principale.
CollisionBehavior.REQUIRED (par défaut) : Toujours afficher le repère, quelle que soit la collision.
CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL : Toujours afficher le repère, quelle que soit la collision, et masquer les repères ou libellés OPTIONAL_AND_HIDES_LOWER_PRIORITY qui le chevauchent.
CollisionBehavior.OPTIONAL_AND_HIDES_LOWER_PRIORITY : Afficher le repère uniquement s'il n'en chevauche pas d'autres.
Si deux repères bitmap se chevauchent, celui dont le zIndex est le plus élevé s'affiche.
S'ils ont le même zIndex, celui dont la position verticale à l'écran est la plus basse s'affiche. Pour en savoir plus sur le zIndex, consultez Z-index du repère.
Si deux repères de vue se chevauchent, celui dont le zIndex est le plus élevé s'affiche. S'ils ont le même zIndex, le repère créé en dernier chevauche tous ceux créés avant lui.
Comme les repères de vue sont dessinés sur un calque au-dessus des repères bitmap, les repères de vue chevauchent les repères bitmap. Pour optimiser le contrôle des collisions, vous devez donc essayer d'utiliser des repères du même type.
L'exemple suivant montre comment définir le comportement d'un repère en cas de collision :
Kotlin
// Collision behavior can only be changed in the AdvancedMarkerOptions object.
// Changes to collision behavior after a marker has been created are not possible
val collisionBehavior: Int = AdvancedMarkerOptions.CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL
val advancedMarkerOptions: AdvancedMarkerOptions = AdvancedMarkerOptions()
.position(latLng)
.collisionBehavior(collisionBehavior)
val marker: Marker = map.addMarker(advancedMarkerOptions)
Java
// Collision behavior can only be changed in the AdvancedMarkerOptions object.
// Changes to collision behavior after a marker has been created are not possible
int collisionBehavior = AdvancedMarkerOptions.CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL;
AdvancedMarkerOptions options =
new AdvancedMarkerOptions()
.position(latLng)
.collisionBehavior(collisionBehavior);
Marker marker = map.addMarker(options);
Sauf indication contraire, le contenu de cette page est régi par une licence Creative Commons Attribution 4.0, et les échantillons de code sont régis par une licence Apache 2.0. Pour en savoir plus, consultez les Règles du site Google Developers. Java est une marque déposée d'Oracle et/ou de ses sociétés affiliées.
Dernière mise à jour le 2024/05/09 (UTC).
[null,null,["Dernière mise à jour le 2024/05/09 (UTC)."],[[["\u003cp\u003eThis page explains how to manage marker collision behavior on maps using \u003ccode\u003eAdvancedMarkerOptions.collisionBehavior\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eCollision behavior dictates how markers are displayed when they overlap, with options including \u003ccode\u003eREQUIRED\u003c/code\u003e, \u003ccode\u003eREQUIRED_AND_HIDES_OPTIONAL\u003c/code\u003e, and \u003ccode\u003eOPTIONAL_AND_HIDES_LOWER_PRIORITY\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eMarker types (bitmap and view) influence collision behavior, with view markers drawn on top of bitmap markers, and zIndex playing a role in determining visibility during overlaps.\u003c/p\u003e\n"],["\u003cp\u003eFor consistent collision handling, it's recommended to use the same marker type (either all bitmap or all view) for all markers on the map.\u003c/p\u003e\n"]]],[],null,["# Collision behavior\n\nSelect platform: [Android](/maps/documentation/android-sdk/advanced-markers/collision-behavior \"View this page for the Android platform docs.\") [iOS](/maps/documentation/ios-sdk/advanced-markers/collision-behavior \"View this page for the iOS platform docs.\") [JavaScript](/maps/documentation/javascript/advanced-markers/collision-behavior \"View this page for the JavaScript platform docs.\")\n\n\u003cbr /\u003e\n\nThis page shows you how to control the collision behavior for a marker.\n\nSet collision behavior for a marker\n-----------------------------------\n\n\nCollision behavior controls how a marker displays if it collides (overlaps)\nwith another marker. The way you create an advanced markers\ndetermines how collision behavior works:\n\n- Advanced markers created by using\n [`BitmapDescriptorFactory`](/android/reference/com/google/android/gms/maps/model/BitmapDescriptorFactory)\n are referred to as *bitmap* markers. These markers are drawn by the\n core map.\n\n- All other advanced markers, including those created by\n using the `AdvancedMarkerOptions.iconView()` method, are referred to as\n *view* markers and are drawn on a layer above the core map.\n\n| **Note:** For optimal collision behavior, you should create all advanced markers of the same type. That is, if you are using a view marker for one marker then you should use view markers for all of them.\n\nTo set collision behavior, set\n[`AdvancedMarkerOptions.collisionBehavior`](/android/reference/com/google/android/gms/maps/model/AdvancedMarkerOptions#collisionBehavior(int))\nto one of the following:\n\n- `CollisionBehavior.REQUIRED`: (default) Always display the marker regardless of collision.\n- `CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL` Always display the marker regardless of collision, and hide any `OPTIONAL_AND_HIDES_LOWER_PRIORITY` markers or labels that would overlap with the marker.\n- `CollisionBehavior.OPTIONAL_AND_HIDES_LOWER_PRIORITY` Display the marker\n only if it does not overlap with other markers.\n\n - If two *bitmap* markers overlap, the one with the higher `zIndex` is\n shown.\n If they have the same `zIndex`, the one with the lower vertical screen\n position is shown. For more information about the `zIndex`, see [Marker\n z-index](/maps/documentation/android-sdk/marker#marker_z-index).\n\n - If two *view* markers overlap, the one with the higher `zIndex` is\n shown. If they have the same `zIndex`, the last created marker\n overlaps any markers created before it.\n\n - Because *view* markers are drawn on a layer above *bitmap* markers,\n *view* markers overlap *bitmap* markers. Therefore, you should try\n to use markers of the same type for better collision control.\n\nThe following example shows setting collision behavior for a marker: \n\n### Kotlin\n\n```kotlin\n// Collision behavior can only be changed in the AdvancedMarkerOptions object.\n// Changes to collision behavior after a marker has been created are not possible\nval collisionBehavior: Int = CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL\nval advancedMarkerOptions: AdvancedMarkerOptions = AdvancedMarkerOptions()\n .position(LatLng(10.0, 10.0))\n .collisionBehavior(collisionBehavior)\n\nval marker: Marker = map.addMarker(advancedMarkerOptions) ?: error(\"Failed to add marker\")\n\n \n```\n\n### Java\n\n```java\n// Collision behavior can only be changed in the AdvancedMarkerOptions object.\n// Changes to collision behavior after a marker has been created are not possible\nint collisionBehavior = AdvancedMarkerOptions.CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL;\nAdvancedMarkerOptions options = new AdvancedMarkerOptions()\n .position(new LatLng(10.0, 10.0))\n .collisionBehavior(collisionBehavior);\n\nMarker marker = map.addMarker(options);\n\n \n```\n\n\u003cbr /\u003e"]]