Replies: 4 comments
-
@RyanTG |
Beta Was this translation helpful? Give feedback.
-
I suspected as much. But then when I saw
https://docs.mapbox.com/android/maps/api/10.16.0/mapbox-maps-android/com.mapbox.maps.plugin.annotation.generated/-point-annotation/ I thought perhaps there was a chance it was available to PointAnnotations. From looking here, it seems like |
Beta Was this translation helpful? Give feedback.
-
I don't exactly know what the conversion of this from an Issue to a Discussion (from Bug to Feature Request) spells for the future. I assume it confirms that "none of these work" and from here we discuss a path forward. Personally, I don't care what the path is, as long as there is some methodology available for managing order :D For reference, here's a previous issue on this topic. #1627 |
Beta Was this translation helpful? Give feedback.
-
Why can we not just give a zIndex? :/ This is a pretty big issue imo, especially for apps with lots of users who may be around the same location. |
Beta Was this translation helpful? Give feedback.
-
Mapbox Implementation
Mapbox
Mapbox Version
default
Platform
iOS
@rnmapbox/maps
version10.0.13
Standalone component to reproduce
This is something of a general Issue. Is it a bug report or a feature request? It is a request to identify, or create, some method to manage the order of Point Annotations.
Observed behavior and steps to reproduce
Example contains 3 PointAnnotation markers situated near one another. Zoom in a little and you can see how they overlap each other.
The observed behavior is that the order of the markers (how they overlap each others) is based on an unknown methodology (though my seems like it might be based on painting from lower right to upper left), and various attempts to manage the order are not working.
Expected behavior
I would expect
symbolSortKey
orzIndex
or even the sorting of the PointAnnotations to affect the order.Notes / preliminary analysis
Methods include:
id
that denotes orderkey
that denotes orderzIndex
to the style that denotes ordersymbolSortKey
(which is a prop that appears to be available in both the Android and iOS code) that denotes order.Other observed behavior is that when
pitchEnabled
orrotateEnabled
aretrue
, playing with those will end up changing the order (markers will suddenly hop on top of another).In summary, there seems to be no clear way to manage the order of the markers when using Point Annotation.
Beta Was this translation helpful? Give feedback.
All reactions