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
The geolocate control's accuracy circle isn't projected correctly at high pitch+zoom. It should remain attached to the surface. The accuracy circle needs to be rethought for instances when the geolocation is on a hill/slope.
This will eventually impact the various Mobile/Nav pucks as well.
Positioning (given that markers are used here), to follow hight pitch and terrain, is fixed with #148 and #183. It remains attached to surface. Related to that part, this bug could be considered as fixed.
The accuracy circle needs to be rethought for instances when the geolocation is on a hill/slope.
Related to behavior of accuracy circle:
Accuracy circle has a feel (as it is one) of an overlaid HTML element - width and height are not implemented to follow map precisely in 2D either, which is observable when panning map in < 60 degrees pitch. This gives it 3D feel as it is laid over horizon when pitch > 60.
An easy fix would implement the circle as a style circle layer, not an HTML element.
The problem is, at lest when I first contributed the geolocate dot, this will mutate the users style introducing extra layers and a style source. It might then break for existing applications which mutate the style or when using setStyle etc.
I still think so long as the user is made aware of this, it's probably okay, but it's no longer 100% taken care of by the SDK and the developer needs to manage these layers in their code (during setStyle).
Unless we implement internal style layers/sources to add to the map but are hidden from the user and survive setStyle etc... 💭
The geolocate control's accuracy circle isn't projected correctly at high pitch+zoom. It should remain attached to the surface. The accuracy circle needs to be rethought for instances when the geolocation is on a hill/slope.
This will eventually impact the various Mobile/Nav pucks as well.
cc @mapbox/mobile @d-prukop @avi-c
The text was updated successfully, but these errors were encountered: