Filters

Filters help you narrow a layer down to the features you want to keep on the map.

You configure filters in the project editor, inside the Data tab. Filters belong to layers, and views decide which of those filters apply in a specific published map.

How filters work

Every filter belongs to a single layer. A filter stores:

• A name
• An active or inactive state
• A target field
• A filter type and condition

This makes filters reusable inside the project. You can keep several filters on the same layer, turn them on or off, rename them, and use views to control how they appear in different map outputs.

Create a filter

Topologis supports two practical ways to create a filter from the layer list in the Data tab:

• Create a blank filter
• Create a filter from a field

A blank filter starts as a numeric filter. If you create a filter from a field, Topologis chooses the filter type from that field’s data type and pre-fills the field name. This is usually the fastest way to create a usable filter because it starts from the layer schema that already exists in the project.

After a filter is created, you can rename it, change its field, adjust its condition, or delete it if you no longer need it.

Filter types

Topologis currently supports five filter types:

• Numeric
• Categorical
• Date
• Text Search
• Boolean

The right choice depends on the field you are filtering. Numeric and date filters work best for ranges and thresholds. Categorical filters work best for known values such as statuses or categories. Text search is useful for free-form string matching. Boolean filters are useful for true or false logic and for checking null or missing values.

Numeric filters

Numeric filters are used for fields such as counts, scores, prices, or measurements.

The current numeric operations are:

• Equals
• Not Equals
• Greater Than
• Greater Than or Equals
• Less Than
• Less Than or Equals
• Between
• In List

Use a numeric filter when you want to keep features above a threshold, between two values, or inside a specific list of numbers.

Categorical filters

Categorical filters are used for fields with a known set of text values, such as region names, statuses, or asset types.

The current categorical operations are:

• In
• Not In

When the layer has a known category domain, Topologis shows those values directly in the filter settings so you can add or remove them without typing each one manually.

Date filters

Date filters are used for fields that contain date or datetime values.

The current date operations are:

• Before
• After
• On
• Between

The date input UI uses UTC. If your data depends on time, make sure you interpret the filter values in UTC as well.

Text search filters

Text search filters are used for string fields such as names, labels, codes, or keywords.

The current text search operations are:

• Contains
• Not Contains
• Starts With
• Ends With
• Equals
• Not Equals

Text search filters also support a Case Sensitive option. Use this type when you want flexible string matching instead of exact category selection.

Boolean filters

Boolean filters are used for fields that represent yes or no style values or data completeness checks.

The current boolean operations are:

• Is True
• Is False
• Is Null
• Not Null
• Is Missing
• Not Missing

This makes boolean filters useful both for simple state checks and for identifying incomplete records.

Feature count preview

When a filter is active, Topologis shows a feature count preview in the filter settings.

This preview tells you whether the filter removes no features, removes all features, or removes a specific number out of the layer total. It is a quick way to validate that the condition is doing what you expect before you move on to styling, views, or sharing.

Using filters in views

Filters are defined on layers, but views control how those filters are used in a specific map output.

For each layer in a view, you can decide:

• Which filters are enabled in that view
• Which filters should appear as UI controls for viewers

This is an important separation. A project can keep the full set of available filters, while each view decides which of them should apply for that audience and whether viewers should be able to interact with them in a shared or embedded map. For the full view model, see Views.