This article only applies to movement data
This article is only relevant when working with movement data, not when working with time series data.
You can read more about the differences between the two in this article.
By default, your records are shown in a gridded way. When zoomed out, the grid cells denote larger areas on the map ( e.g., 1km x 1km), when zoomed in the data points are aggregated in smaller cells (e.g., 20m x 20m). This gridded data representation has many benefits:
It allows quick aggregation by counting the number of records in a cell
It allows multi-resolution representations
It shows the data as is, without assuming points are connected to one another
Scales easily to multiple billions of records
As location records of the same asset are related to one another, they can be connected to form trajectory lines.
You can switch between gridded data handling and trajectories data handling using the selection input in the Layers panel.
Only use a limited amount of data for trajectories
Trajectories are retrieved and visualized client-side, in your browser. This means that the amount of data that can be handled this way is limited at the expense of very high interactivity when filtering and styling the data.
Sometimes a dialog will pop up to inform that the data would be too big. In that case, apply a spatial or attribute filter to restrict the data.
When selecting Realtime, each asset is shown at its last reported location.
Data will automatically update
When pushing/or uploading new data the map (and timeline and attribute) views are automatically updated.
This allows you to have an always up-to-date view, for example, when looking at real-time data.