Styles
Styles control how layers look on the map.
In Topologis, styles are project-level objects that you create once and reuse across layers. A layer points to a style, and a view can optionally swap that layer to a different existing style for that specific output.
How styles work
Every project starts with a Default Style.
Styles are stored separately from layers. This means you can:
- Reuse the same style across multiple layers
- Duplicate a style and make a variation
- Keep several styles in the same project and assign them as needed
This is useful when several layers should share the same visual treatment, or when you want a stable base style and a few controlled alternatives.
Create and manage styles
You create and manage styles from the Styles list in the project editor.
The current style workflow supports:
- Creating a new style
- Renaming a style
- Duplicating a style
- Deleting a style
- Turning a style active or inactive
Each project also includes the system Default Style. That style is created with the project and acts as the fallback style if a layer’s assigned style is missing or inactive.
Assign styles to layers
Layers use a style through the layer settings in the Data tab.
You can assign a style directly to a layer, and you can also assign a style from the Styles list. The style list shows which layers currently use each style, which makes it easier to manage shared styles across a larger project.
For point cluster layers, Topologis also supports a separate cluster style setting. That lets the cluster symbols use a different style from the underlying layer if needed.
Fill settings
The Fill tab controls polygon and area fill behavior.
The current fill controls are:
- Enable or disable fill
- Set a fixed fill color
- Turn on dynamic color rules for the fill color
If you only need a straightforward polygon appearance, a fixed fill color is enough. If the fill should respond to data values, use a dynamic color rule instead.
Stroke settings
The Stroke tab controls line and outline appearance.
The current stroke controls are:
- Enable or disable stroke
- Set line color
- Set width in
pixelsormeters - Set minimum and maximum pixel width
- Round line caps
- Round line joints
- Enable line billboard
This gives you control over both the line’s base appearance and how it behaves across zoom levels.
Point settings
The Points tab controls point radius and point drawing behavior.
The current point controls are:
- Set point radius
- Set size units in
pixelsormeters - Set minimum and maximum pixel radius
- Toggle antialiasing
- Toggle billboard
These settings are most useful for direct point rendering, where symbol size and screen behavior need to be tuned without switching to an aggregated render mode.
Dynamic color rules
Dynamic color rules let a style change color based on data.
Topologis currently supports dynamic color for numeric and categorical fields. The editor lets you choose a field, then build the color logic in one of two ways:
- Use a preset ramp
- Define custom color steps
For numeric fields, you can also choose continuous or discrete interpolation, adjust the focus range, change the number of steps in preset mode, invert the ramp, and set a no-data color. For categorical fields, you can assign colors from a preset ramp or define custom colors per category.
Because styles are reusable, dynamic color rules work best when the target layers share the same field names and compatible field types.
Dynamic size and width rules
Dynamic number rules let a style change line width or point radius from data.
Topologis currently supports dynamic numeric and categorical mapping for:
- Line width
- Point radius
You choose a field and then define output values as steps. Numeric mappings also support continuous or discrete interpolation. Both line width and point radius include a default value for records that do not produce a usable match.
This is useful when symbol size should reflect magnitude, category, or a controlled ranking instead of staying fixed.
Style overrides in views
Views do not edit a style’s settings directly. Instead, a view can assign a different existing style to a layer for that view.
This is a narrower override model than editing the style itself. The project keeps the reusable style definitions, while the view decides whether a specific layer should keep its current style or switch to another one in that published output. For the full view model, see Views.