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
how to specify which feature labels should show up at which zoom levels?
how to specify at a zoom level, which labels should have priority (aka be bigger). (engine expects to receive labels sorted by number. whoever has higher priority will be rendered first)
more label style considerations:
labels can be styled as such:
size
fill and stroke color
font (incl. bold, italic, etc.)
spacing between the feature & the text
repeat (how far apart the label should repeat, like for a road or river)
follow feature (eg river)
whether it should be rendered at x zoom levels
priority list for where label should appear in relation to dot/sprite (eg: top, left, right, bottom). it will have a default priority list, but you should be able to specify a diff priority. also "only top and bottom, never left and right" for example.
rotations: example: always 45 degrees, upper right in relation to point" or "going up to the right from the point" (possible if you specify "always render on right of point, then rotate." rotations happen about the point.
padding around label (outside the box, aka margin)
padding around label (inside the box)
padding around point/sprite (maybe belongs in another doc?)
box fill/box stroke (rgba)
orientation for characters (eg: japanese characters going vertical). default is horizontal.
in some separate doc:
how many labels you want to display, which ones, all, etc.
The text was updated successfully, but these errors were encountered:
how to specify which feature labels should show up at which zoom levels?
how to specify at a zoom level, which labels should have priority (aka be bigger). (engine expects to receive labels sorted by number. whoever has higher priority will be rendered first)
more label style considerations:
labels can be styled as such:
in some separate doc:
The text was updated successfully, but these errors were encountered: