Data: Open Files Panel

Open Files panel

The Open Files panel is a tree-like overview of all tags/individuals or deployments in an open dataset.

Selecting Individuals

To show which individuals/tags are shown in the map Firetail provides the Open File panel. It can be used to select subsets of the data or the complete dataset (default).

Click on the checkbox next to each individual to de-/select the associated data. The triangle symbol will show you the number of GPS and acceleration samples available.

subset selection

focus regions containing data

For each track, you can focus the current map on the set of selected points by clicking the respective checkbox below the ‘eye’ symbol.

subset selection

Select sensors to show

Firetail allows you to focus on specific lanes in the burst view and hide data that is not currently of interest.

sensors selection

Context menu

Right-click on a grouping to show the context menu

Redefine the track color

Change the color of the selected grouping.

Select by name

Enter a search string to select all matching grouping names.

Show/Hide groupings of the same color

Show or hide all grouping that share the same color with the context menu entity. This is particularly useful when reference data is used to color trajectories by their metadata.

Create empty burst space

This option will create an empty layer of acceleration data that can be used to annotated GPS fixes using Firetail’s annotation mechanism

Event Editor

Firetail 8 introduces a tabular event viewer. Right-click on an individual/tag in the Open Files panel and select Show Event Editor. Here you can inspect the raw event data as a table.

Select/Deselect lanes and derived measurements

Clicking on the triangle symbol next to a tag or individual reveals available burst sensor types. These can be

  • loaded along with the dataset
  • generated from the data (like ODBA, IMU calibration, Euler angles or FFT previews)

Toggle the associated checkboxes to hide or show the respective burst lanes.

When you toggle a sensor type, this will affect the start and end timestamp and reset the burst viewport. In this case bookmarks provides a simple way to remember start and end timestamps to return to a region of interest. Using the option keep sensor states you may also keep the current selection of sensors when loading a bookmark (e.g. if only IMU data was enabled).