Do we really need to build this? And if so, how do we keep it simple?
The only use case for aggregated data (aggregated on time and altitude) is the bird migration flow visualization and TIMAMP. TIMAMP allows the user to aggregate the data in many ways, so it would require many data products (I think). The bird migration flow visualization only needs one type of aggregation, so a single aggregation would suffice. I would only tackle this work package once we adapt the flow visualization to work for all ENRAM data.
Do we really need to build this? And if so, how do we keep it simple?
The only use case for aggregated data (aggregated on time and altitude) is the bird migration flow visualization and TIMAMP. TIMAMP allows the user to aggregate the data in many ways, so it would require many data products (I think). The bird migration flow visualization only needs one type of aggregation, so a single aggregation would suffice. I would only tackle this work package once we adapt the flow visualization to work for all ENRAM data.
How does the data look like?