The origin-destination page uses matrices to show you statistics on:
How many assets moved from location A to location B in a certain time period
What the average travel time was from location A to location B in a certain time period
You can do this analysis for a single time period, or compare two time periods side-by-side and see the difference between those time periods.
In the example above, the traffic flow is analyzed between Neuland, Altengamme, Marienthal and Poppenbuttel. The labels on the left are the originating areas, the labels at the top the destination areas. In an origin destination matrix, these labels are identical, and one analyzes for each pair of selected areas how many move from the first to the second.
4 assets travelled from Poppenbuttel to Altengamme in the selected time period
138 assets travelled from Neuland to Marienthal in that same time period
Cell (row i, column j) shows the traffic from the area at
row i to the area at
The matrix is asymmetrical
Most of the time, the amount of traffic going from A to B is not the same as the traffic going from B to A.
Therefore, most origin-destination matrices are asymmetrical.
You need a movement data set with records that define "trips" or "journeys": each record with the same id belongs to the same trip.
You cannot perform origin destination analysis when the id’s of your records change for every record.
In case the identifiers of your records do not correspond to trips, but to for example an individual vessel and if that vessel moves multiple times between the origin and the destination in the selected time period, that vessel will only be counted once.
Origin destination analysis is not supported for time series data sets.