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
| Operator | Description | Use Cases | Data Types |
|---|---|---|---|
| Equals | Exact match - field value must be identical to the specified value | ID lookups, status codes, exact category matching | All types |
| Not Equals | Excludes records where field value matches the specified value | Removing specific statuses, excluding certain categories | All types |
| Contains | Field value contains the specified text (case-insensitive partial match) | Name searches, address filtering, description text searches | Text/String |
| Not Contains | Field value does not contain the specified text | Excluding records with specific keywords or phrases | Text/String |
Numeric Operators
| Operator | Description | Use Cases | Data Types |
|---|---|---|---|
| Greater Than | Field value is numerically greater than specified value | Age limits, price thresholds, date ranges | Number/Date |
| Greater Than or Equals | Field value is greater than or equal to specified value | Minimum requirements, inclusive ranges | Number/Date |
| Less Than | Field value is numerically less than specified value | Maximum limits, upper bounds, early date filtering | Number/Date |
| Less Than or Equals | Field value is less than or equal to specified value | Maximum inclusive limits, budget caps, deadline filtering | Number/Date |
Data Presence Operators
| Operator | Description | Use Cases | Data Types |
|---|---|---|---|
| Contains Data | Field has a value (not null/empty) | Finding records with complete information | All types |
| Not Contains Data | Field is empty or null | Identifying incomplete records, missing data | All types |
List Operators
| Operator | Description | Use Cases | Data Types |
|---|---|---|---|
| Is In List | Field value matches any item in a predefined list of values in a field | Multi-select filtering, category groups, bulk matching | All types |
| Not In List | Field value does not match any item in a predefined list in a field | Excluding multiple categories, bulk exclusion filtering | All 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
Layer Gallery Filtering
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