Skip to main content
How to filter your data

Learn how to use filters to gain and export useful insights.

Updated over 8 months ago

Introduction

The Sitemark platform contains a multitude of data. Using filters can help you dig deeper and focus on the right areas to better understand your data.


How does it work?

When you analyze an operation, you will find the Filters feature at the top right of the detail page of a completed operation, as shown below:

Clicking the button opens the Filters pop-up window, where you can set filters on the different data layers that are available in that operation.

Empty filter modal for thermal anomalies

Pressing the Apply button will apply the filters and close the pop-up window. You'll see that the Sitemark platform updates the map content, only showing the filtered items.

Combining filters with AND and OR

You can create powerful filters by combing AND and OR filters. Filter rules within each block are combined with AND operators. Every filter block can be combined with an OR operator to another filter block. Let's look at an example to show what that means.

The screenshot above shows a typical use case for warranty claims, where you can claim two types of problems. All bypassed substring issues are eligible for the claim, while modules with hotspots are only eligible if they have a delta temperature greater than or equal to 15โ„ƒ.


What filters can I use?

Every Layer has its own properties and, thus its own filters. For solar anomalies for example you'll see filters for type, cause, severity, delta temperatures, etc. For annotations, you'll see filter options for the different measurements: length, area, volume, etc.

In general, there are three kinds of filters you can apply:

  1. You can filter on any of the properties of the layer.

  2. You can filter on regions.

  3. You can filter on the ID of the feature, which is the number you see on the map.

Note that you'll only see a certain filter if the data on your operation contains that property. If you didn't make any measurements for example, you won't see any filters for annotations.


Saving Filters

When handling large amounts of data, the filters become very useful for narrowing down what you're looking at and focusing your analysis on certain aspects of the data.

However, spending time getting the right filter and then needing to switch to a different view that requires another filter will mean you're spending your time making sure the filters are correct and not what you want to be doing: your analysis.

Using the save filter feature could save you a large amount of time. Instead of having to re-do the filter each time, you can save your current view and then revisit that data view whenever you like. This is also visible to the other users on the platform, meaning that you can share your views with your teammates so they can see what you can.

Active filters pop-up

What can I use it for?

You can use the filters for a lot of different things:

  • Focus on a subset of anomalies or annotations on the map. It makes it easier to find specific problems and analyze them in more detail.

  • Export a PDF report containing a subset of anomalies or annotations. Make a report containing only severe anomalies for example, or report on the stockpiles that are running low.

  • Export a CSV containing a subset of anomalies or annotations.
    Want to learn more about exporting and sharing data? Check out this article.

  • Push a list of anomalies to the Sitemark Field App to let your technicians know what to solve. Want to learn more about the Sitemark Field App? Check out this article.

  • Zoom in on your data in statistics mode. See what's causing all those hotspots, or find out how much you're losing because of vegetation. Want to learn more about statistics mode? Check out this article.

  • Filtered share links grant someone restricted access to your data. Just save the filters you want and use the filter button next to the share link to apply them.
    Want to learn more about share links? Check out this article.

Did this answer your question?