https://github.com/glide-rs/openair-rs
OpenAir airspace parser for Rust
https://github.com/glide-rs/openair-rs
airspaces aviation free-flight openair parser rust
Last synced: about 2 months ago
JSON representation
OpenAir airspace parser for Rust
- Host: GitHub
- URL: https://github.com/glide-rs/openair-rs
- Owner: glide-rs
- License: apache-2.0
- Created: 2019-04-25T23:59:05.000Z (almost 7 years ago)
- Default Branch: main
- Last Pushed: 2025-11-22T21:04:26.000Z (2 months ago)
- Last Synced: 2025-11-22T23:14:54.239Z (2 months ago)
- Topics: airspaces, aviation, free-flight, openair, parser, rust
- Language: Rust
- Homepage:
- Size: 659 KB
- Stars: 7
- Watchers: 2
- Forks: 5
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- Changelog: CHANGELOG.md
- License: LICENSE-APACHE
Awesome Lists containing this project
README
# openair-rs
[](https://github.com/glide-rs/openair-rs/actions/workflows/ci.yml)
[![Docs][docs-badge]][docs]
A Rust library for reading and writing airspace files in OpenAir format (used by flight instruments
like Skytraxx and others).
http://www.winpilot.com/UsersGuide/UserAirspace.asp (see also `FORMAT.txt`)
Docs: https://docs.rs/openair/
## Status
Supported file format features:
- [x] Parse airspace metadata
- [x] Write airspace metadata
- [ ] Parse terrain metadata
- [x] Support polygon points
- [x] Support circles
- [x] Support arcs
- [x] Support AY/AF/AG extension records
Label placement hints (AT) and style records (SP, SB) are not supported.
## Implementation Notes
Unfortunately the `OpenAir` format is really underspecified. Every device
uses varying conventions. For example, there is nothing we can use as clear
delimiter for airspaces. Some files delimit airspaces with an empty line,
some with a comment. But on the other hand, some files even place comments
between the coordinates so that they cannot be used as delimiter either.
This parser tries to be very lenient when parsing, based on real life data.
The end of an airspace is reached when the next one starts (with an `AC`
record) or when the file ends.
**NOTE: Altitude levels without a unit specifier (e.g. "1000 GND") will be
treated as feet!)**
## Examples
### Parsing
You can try the parser using the example program:
$ cargo run --example parse_file example_data/Switzerland.txt
### Writing
```rust,no_run
use std::fs::File;
use openair::{Airspace, Altitude, Class, Coord, Geometry};
let airspace = Airspace {
name: "Example Zone".to_string(),
class: Class::D,
type_: None,
lower_bound: Altitude::Gnd,
upper_bound: Altitude::FlightLevel(100),
geom: Geometry::Circle {
centerpoint: Coord { lat: 47.0, lng: 8.0 },
radius: 5.0,
},
frequency: None,
call_sign: None,
transponder_code: None,
activation_times: None,
};
let file = File::create("output.txt").unwrap();
openair::write(file, [&airspace]).unwrap();
```
## Serde Serialization
To include serialization of all data types, enable the `serde` feature.
## License
Licensed under either of
* Apache License, Version 2.0 ([LICENSE-APACHE](LICENSE-APACHE) or
http://www.apache.org/licenses/LICENSE-2.0)
* MIT license ([LICENSE-MIT](LICENSE-MIT) or
http://opensource.org/licenses/MIT) at your option.
### Contribution
Unless you explicitly state otherwise, any contribution intentionally submitted
for inclusion in the work by you, as defined in the Apache-2.0 license, shall
be dual licensed as above, without any additional terms or conditions.
[docs]: https://docs.rs/openair/
[docs-badge]: https://img.shields.io/badge/docs-docs.rs-yellow.svg?maxAge=3600