Initial commit

.github/workflows/ci.yml

@@ -0,0 +1,39 @@
+name: CI
+
+on:
+  push:
+    branches: [ "main" ]
+    tags: [ "v*" ]
+  pull_request:
+    branches: [ "main" ]
+  workflow_dispatch:
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v3
+
+      - name: Create airports.json
+        run: |
+          yq airports.yaml > /dev/null
+          yq -o=json -I=0 airports.yaml > airports.json
+
+      - name: Create navaids.json
+        run: |
+          yq navaids.yaml > /dev/null
+          yq -o=json -I=0 navaids.yaml > navaids.json
+
+      - name: Create release
+        if: github.ref_type == 'tag' && contains(github.ref_name, 'v')
+        uses: softprops/action-gh-release@v1
+        env:
+          GITHUB_TOKEN: ${{ github.token }}
+        with:
+          name: NavData ${{ github.ref_name }}
+          prerelease: false
+          draft: true
+          files: |
+            airports.json
+            navaids.json

README.md

@@ -0,0 +1,24 @@
+# vATIS NavData
+
+This repository contains the navdata (airports and navaids) files used by [vATIS](https://github.com/vatis-project/vatis).
+
+## How do I submit a navdata change?
+Updates to the navdata files should be made directly by submitting a [pull request](https://github.com/vatis-project/navdata/pulls). 
+The navdata files hosted in this GitHub project are in `yaml` format to make it easier for contributions. Approved changes will be merged and automatically converted to `json` file format for use by vATIS.
+
+### Data Format
+The `airports.yaml` file contains data for airports. An airport is composed of four properties: `ID`, `Name`, `Lat` (Latitude) and `Lon` (Longitude).
+
+```yaml
+- ID: KLAX
+  Name: LOS ANGELES INTERNATIONAL AIRPORT
+  Lat: 33.942495
+  Lon: -118.40807
+```
+
+The `navaids.yaml` file contains navaid (VOR/VORTAC) data. A navaid is composed of two properties: `ID` and `Name`. 
+
+```yaml
+- ID: LAX
+  Name: LOS ANGELES
+```