The data in our smarts are by default grouped by each column, except for the columns that are aggregated (for example pax column which shows the sum of passengers for the selected criteria). It means that the results providing the same information are presented in one single row.
For example, if there are three flights from the same origin to the same destination in one day, and the flight number nor hour is in your columns selection (nor the passengers' profile, nor any other info that might differ) you will get the information related to these three flights shown in one single row, and the corresponding total of passengers will be the sum. The implication of that is that removing columns from your customised view's selection can help to reduce its size significantly.
Let's imagine the following example:
In your smart, you can find five columns: flight departure date, flight origin country, flight origin city, the flight destination country and the total number of passengers.
| flight_leg_departure_date | flight_leg_origin_country | flight_leg_origin_city | flight_leg_destination_country | pax |
|
2023-01-05
|
ES | MAD | FR | 100 |
| 2023-01-05 | ES | BCN | FR | 200 |
| 2023-01-26 | ES | VLC | FR | 80 |
| 2023-01-26 | ES | BCN | FR | 150 |
If we remove the flight_leg_origin_city column from the above selection because we are only interested in travellers from Spain to France without considering their origin city, our custom view will become two times smaller as the results will be grouped as follows:
| flight_leg_departure_date | flight_leg_origin_country | flight_leg_destination_country | pax |
|
2023-01-05
|
ES | FR | 300 |
| 2023-01-06 | ES | FR | 230 |
From here, we could go further and, for example, modify the granularity of departure date to aggregate the data per month, or even remove the flight_leg_departure_date column completely if we are only interested in global figures. In this case, we would get the results for passengers travelling from Spain to France grouped in one single row:
| flight_leg_origin_country | flight_leg_destination_country | pax |
| ES | FR | 530 |
Keeping the above in mind, we strongly recommend that you remove from your customised view all the columns that are not essential for the analysis you work on.
You can learn more about the best practices in creating customised views from the below article: