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
text-unique: true: uses label text to dedupe down to only a single label for a given string within a tile
symbol-mode: guidance: switches label placement mode to use the "guidance" approach
Guidance approach:
Places labels close to the viewport center
Filtering labels for lines by an angle threshold (e.g. emphasizing cross streets)
Defined placement events at major changes to camera angle and aggressive label lockdown in-between to reduce popping/flickering
What I feel confident in at this point
Guidance labelling is sufficiently different from basemap map labelling to have have a separate label placement mode.
The approach in this branch is usable and a significant improvement over basemap labelling when designing guidance maps.
It doesn't make sense to expose customizability to this in the style spec or our renderers beyond an on/off switch. I think we'll want to at least land cross-tile label placement before reconsidering this but for now exposing minimal API surface area on the feature makes most sense.
At the moment I've not given much attention to cleanliness of implementation. My next goals will be to clean up the code and add tests.
Most of the testing at this point has been through using http://github.com/mapbox/guidance-sim and using 👀 which isn't going to be a sustainable approach to prevent regression going forward. I'll focus on setting up unit tests that can stress test the guidance approach, especially the strategies that prevent label flickering/popping.
Capturing where I'm at with the experiments with guidance labelling.
What it does
text-unique: true
: uses label text to dedupe down to only a single label for a given string within a tilesymbol-mode: guidance
: switches label placement mode to use the "guidance" approachWhat I feel confident in at this point
At the moment I've not given much attention to cleanliness of implementation. My next goals will be to clean up the code and add tests.
Most of the testing at this point has been through using http://github.com/mapbox/guidance-sim and using 👀 which isn't going to be a sustainable approach to prevent regression going forward. I'll focus on setting up unit tests that can stress test the guidance approach, especially the strategies that prevent label flickering/popping.
Next actions
The text was updated successfully, but these errors were encountered: