Skip to main content
Version: Release 1 - 1.1.3.X

Filtering Operators

Overview

Maptaskr Power Maps provides various comparison operators for filtering data across different contexts. These operators are available when configuring filters in the Layer Gallery, Config Manager, Data Tab, and interactive map filtering. Understanding when and how to use each operator ensures you get the most accurate results from your data filtering.

Available Operators

Text and String Operators

OperatorDescriptionUse CasesData Types
EqualsExact match - field value must be identical to the specified valueID lookups, status codes, exact category matchingAll types
Not EqualsExcludes records where field value matches the specified valueRemoving specific statuses, excluding certain categoriesAll types
ContainsField value contains the specified text (case-insensitive partial match)Name searches, address filtering, description text searchesText/String
Not ContainsField value does not contain the specified textExcluding records with specific keywords or phrasesText/String

Numeric Operators

OperatorDescriptionUse CasesData Types
Greater ThanField value is numerically greater than specified valueAge limits, price thresholds, date rangesNumber/Date
Greater Than or EqualsField value is greater than or equal to specified valueMinimum requirements, inclusive rangesNumber/Date
Less ThanField value is numerically less than specified valueMaximum limits, upper bounds, early date filteringNumber/Date
Less Than or EqualsField value is less than or equal to specified valueMaximum inclusive limits, budget caps, deadline filteringNumber/Date

Data Presence Operators

OperatorDescriptionUse CasesData Types
Contains DataField has a value (not null/empty)Finding records with complete informationAll types
Not Contains DataField is empty or nullIdentifying incomplete records, missing dataAll types

List Operators

OperatorDescriptionUse CasesData Types
Is In ListField value matches any item in a predefined list of values in a fieldMulti-select filtering, category groups, bulk matchingAll types
Not In ListField value does not match any item in a predefined list in a fieldExcluding multiple categories, bulk exclusion filteringAll types

Operator Usage Examples

Text Filtering Examples

Equals

Field: Status
Operator: Equals
Value: "Active"
Result: Only shows records where Status is exactly "Active"

Contains

Field: Address
Operator: Contains
Value: "Perth"
Result: Shows records with addresses containing "Perth" (e.g., "123 Perth Street", "North Perth", "Perth CBD")

Numeric Filtering Examples

Greater Than

Field: Priority
Operator: Greater Than
Value: 3
Result: Shows records where Priority is 4, 5, 6, etc.

Greater Than or Equals

Field: Score
Operator: Greater Than or Equals
Value: 80
Result: Shows records where Score is 80, 81, 82, etc.

Less Than

Field: Age
Operator: Less Than
Value: 65
Result: Shows records where Age is 64, 63, 62, etc.

Less Than or Equals

Field: Budget
Operator: Less Than or Equals
Value: 10000
Result: Shows records where Budget is 10000, 9999, 9998, etc.

Data Presence Examples

Contains Data

Field: Email Address
Operator: Contains Data
Value: (no value needed)
Result: Shows only records that have an email address populated

List Filtering Examples

Is In List

Field: Status
Operator: Is In List
Value: ["Active", "Pending", "Review"]
Result: Shows records where Status matches any of the specified values

Not In List

Field: Category
Operator: Not In List
Value: ["Archived", "Deleted", "Suspended"]
Result: Shows records where Category does not match any of the excluded values

Context-Specific Usage

When configuring filters in the Layer Gallery Features tab:

  • Available operators depend on the field data type
  • Dynamic values can be used (e.g., {{recordId}})
  • Multiple filters can be combined with "Match All" or "Match Any" logic

Config Manager Map Filters

For Layer-type filters in the Config Manager:

  • Operators are available when defining layer conditions
  • Used to pre-filter data when the map loads
  • Works with dynamic variables from the current record context

Data Tab Filtering

In the interactive data table:

  • All operators are available based on column data types
  • Immediate filtering of visible data
  • Multiple criteria can be applied simultaneously

Interactive Layer Filtering

When using "Filter Layer" from the Layers panel:

  • Real-time filtering of map display
  • Operators automatically match the selected field type
  • Filter effects are immediately visible on the map

Performance Considerations

Efficient Operator Selection

Fast Operations

  • Equals: Fastest for exact matches, especially on indexed fields
  • Contains Data/Not Contains Data: Quick null/empty checks

Slower Operations

  • Contains/Not Contains: Text searches can be slower on large datasets
  • Is In List/Not In List: Performance depends on list size and field indexing

Best Practices

Use Specific Operators

  • Choose Equals over Contains when you need exact matches
  • Use Contains Data instead of testing for specific "empty" values

Optimize for Data Types

  • Text fields: Use Contains for partial matching, Equals for exact matching
  • Numeric fields: Use Greater Than/Less Than for range filtering, Greater Than or Equals/Less Than or Equals for inclusive ranges
  • Date fields: Leverage comparison operators for date range filtering
  • Multi-value fields: Use Is In List/Not In List for multiple options

Filter Combinations

  • Use "Match All" when you need precise results (AND logic)
  • Use "Match Any" when you want broader results (OR logic)
  • Start with more selective filters to reduce the dataset size early