This repository has been archived by the owner on Aug 8, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
When map is tilted, flat annotation views should be skewed #5090
Labels
annotations
Annotations on iOS and macOS or markers on Android
bug
Google Maps parity
For feature parity with the Google Maps SDK for Android or iOS
iOS
Mapbox Maps SDK for iOS
Milestone
Comments
1ec5
added
bug
iOS
Mapbox Maps SDK for iOS
annotations
Annotations on iOS and macOS or markers on Android
labels
May 21, 2016
1ec5
changed the title
When map is tilted, flat annotation views should be skewed, not vertically scaled
When map is tilted, flat annotation views should be skewed
May 21, 2016
3 tasks
#5245 isn’t going to make iOS SDK v3.3.0, so we need to remove the |
1ec5
added a commit
that referenced
this issue
Jul 3, 2016
Removed MGLAnnotationView’s option to lie flat against a tilted map to work around #5090.
1ec5
added
the
Google Maps parity
For feature parity with the Google Maps SDK for Android or iOS
label
Aug 26, 2016
dennycd
added a commit
that referenced
this issue
Oct 12, 2016
dennycd
added a commit
that referenced
this issue
Oct 13, 2016
The commits above are from #6686. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
annotations
Annotations on iOS and macOS or markers on Android
bug
Google Maps parity
For feature parity with the Google Maps SDK for Android or iOS
iOS
Mapbox Maps SDK for iOS
Both the user dot/puck and the flat annotation views introduced in #5067 rely on
CATransform3DRotate()
to rotate the annotation view in 3D space. But the transform is based onCATransform3DIdentity
, so the annotations appear to be squashed, whereas the map is skewed with a perspective transform:Untilted
Tilted
Notice how the left and right edges of each annotation remain perpendicular to the top and bottom edges, even as the north-south roads come closer together towards the top of the view. (This is the same area depicted in #1266, by the way.)
/cc @boundsj @friedbunny
The text was updated successfully, but these errors were encountered: