roadmap.qmd

---
title: "Roadmap"
---



The plan is to release subsequent improvements of the \acr{OPDI} data sets every two months. 

## Future Releases

### Q2 2024

This release aims to include the following improvements:

- Use 5-sec resolution trajectories
- Larger time frame for the available data sets (goal: 1 year).
- Improving the initial flight event extractions by fine tuning parameters and algorithms.
- Improvement in flight list \acr{ADEP} / \acr{ADES} approximations using [H3 geospatial indexing system](https://h3geo.org/).
- Inclusion of new event types and occurrences:
  * off-block
  * in-block
  * runway entry
  * runway exit


### Candidate topics for future releases

In the longer term the \acr{OPDI} aims to include the following improvements:

- Include more events
  * \acr{FIR} crossing
  * start and stop of holdings
- Use third party trajectory data (aside from the available via \acr{OSN}).
- Validate flight events and measurements using third party data.
- Provide easy access to \acr{OSN} state vector trajectories at 5-sec granularity
- Provide cleaned up state vector based trajectories, i.e. remove vertical glitches
  (via `filter()` in [`traffic`](https://traffic-viz.github.io/index.html) library), associate meteorological information (via
  [`fastmeteo`](https://github.com/junzis/fastmeteo) library), remove dirty trajectories (too small/short), ...

## Past Releases

An overview of past releases and the various versions were used in each OPDI version can be seen below.

| OPDI version | Release date   | Flight List | Flight Event | Measurements | Period |
|--------------|----------------|---------------------|----------------------|----------------------|----------|
| OPDI v0.0.1  | 1/12/2023| Flight List v0.0.1  | Flight Event v0.0.1  | Measurements v0.0.1  | 2 Months |


## Contact

If you notice any bugs, or if you have any feature requests, please [contact us](mailto:pru-support@eurocontrol.int).