Navaids & airways navaids-conus · 2611
federal · navaids · effective 2026-10-29 to 2026-11-26 · in the live catalog · history
Experimental / Amateur-Built use only. Not certified. This data is provided as-is with no warranty and any use of the data is at your own risk.
Checks
pass 9 warn 0 fail 0 not run 8
- not run PACK-004 Upstream sources are recorded: Retro record: this edition was published before pack-report/1 existed, and the upstream inputs it was built from were not recorded then and cannot be recovered from the pack.
- not run ROW-002 Row counts against the previous edition: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here.
- not run ROW-003 No table of the previous edition has disappeared: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here.
- not run SG-001 schema_guard layer 1: input CSV structure matches the committed snapshot: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time.
- not run SG-002 schema_guard layer 2: every column the builder reads is present: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time.
- not run SG-003 schema_guard layer 3: policed columns hold only known values: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time.
- not run GEO-002 Points outside the US coverage envelope, against the previous edition: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here. This edition has 2,139 such points; the next edition compares against that.
- not run UNQ-002 Identifiers the FAA reuses, against the previous edition: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here. This edition: navaids(id, type) 33; awy_segments(awy_id, seq) 332.
- record is retro, not build: only a build record can clear the gate
- ROW-003 is blocking and did not run: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here.
- SG-001 is blocking and did not run: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time.
- SG-002 is blocking and did not run: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time.
- SG-003 is blocking and did not run: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time.
Show:
| Check | What it checks | Measured | Expected | Cannot catch | ||
|---|---|---|---|---|---|---|
| not run | PACK-004 non-blocking | Upstream sources are recorded | — | at least one source, each with a non-empty edition and a 64-hex sha256 | A recorded source that is not the one the build actually used, and an edition or sha256 that is well formed but wrong. | Note: Retro record: this edition was published before pack-report/1 existed, and the upstream inputs it was built from were not recorded then and cannot be recovered from the pack. |
| not run | ROW-002 non-blocking | Row counts against the previous edition | — | Provisional threshold: no table moves more than 10%; a larger move needs a build note | A change that keeps counts steady (rows replaced by wrong rows), any defect already present in the previous edition, and a loss under the threshold (for obstacles at 10%, about 65,000 rows). | Note: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here. |
| not run | ROW-003 | No table of the previous edition has disappeared | — | every table in the previous edition is still present, unless schema_version changed | A table dropped together with a schema_version bump that should not have been; the bump is taken as the declaration that the drop is intended. | Note: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here. since AER-4102 |
| not run | SG-001 | schema_guard layer 1: input CSV structure matches the committed snapshot | — | no added, removed, retyped or widened column | A change in the values inside an unchanged column layout. | Note: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time. since NASR 26-01 |
| not run | SG-002 | schema_guard layer 2: every column the builder reads is present | — | all required headers present | A column that is present but filled with wrong or blank values. | Note: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time. since NASR 26-01 |
| not run | SG-003 | schema_guard layer 3: policed columns hold only known values | — | no unknown value in a policed column | A known value used with a new meaning, and every column the contract does not police. | Note: Needs the upstream CSVs (--inputs). The guard runs on the live download at build time. since NASR 26-01 |
| not run | GEO-002 non-blocking | Points outside the US coverage envelope, against the previous edition | — | Provisional threshold: no growth beyond 25 points or 10%, whichever is larger. FAA files carry real oceanic and foreign points, so the count is tracked, not forbidden | A point moved to the wrong place inside the envelope; the envelope is a handful of boxes, not a coastline. | Note: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here. This edition has 2,139 such points; the next edition compares against that. |
| not run | UNQ-002 non-blocking | Identifiers the FAA reuses, against the previous edition | — | no more reused navaid idents or airway sequence numbers than the previous edition | Whether any one reuse is legitimate; the check only counts them. | Note: Retro record: no earlier edition is listed, so there is nothing to compare against. Editions published before the ones the manifest lists were pruned and are not known here. This edition: navaids(id, type) 33; awy_segments(awy_id, seq) 332. |
| pass | PACK-001 | pack_meta is readable and names a known kind | id=navaids-conus kind=navaids cycle=2611 schema_version=1 | pack_meta present; kind is one the device knows | A pack_meta that is well formed but names the wrong id or cycle for the bytes inside. | |
| pass | PACK-002 | Attribution and license are recorded in pack_meta | attribution and license present | both non-empty | A license tag or attribution that is present but wrong for the data. | |
| pass | PACK-003 | Origin label is federal, community or user-supplied | federal (defaulted by kind navaids, not read from the pack) | one of federal / community / user-supplied | Whether the label matches where the data really came from. For a kind with a default label (ORIGIN_BY_KIND in packtools/report.py) the label comes from that table, not from the builder or the pack, so the check is tautological and always passes; measured says which. With --origin it shows only that the label given is one of the three. | since AER-699 |
| pass | ACC-001 | Device acceptance: pyEfis's own reader opens the pack and answers a fixed query set | opened; 3/3 queries returned data | the reader opens the pack and every query returns data | Wrong values the reader accepts. It shows the device can open and query these bytes, not that what it returns is right. The queries cover fixed points only: US kinds, 5 CONUS metros (Denver, Seattle, Atlanta, Los Angeles and Chicago); airports (Canada), Toronto and Vancouver; water, Puget Sound, Lake Michigan and Lake Ontario; navaids, idents DEN, SEA, LAX; procedures, airways V23, J80, V1; terrain, one native tile or the coarsest mosaic level. So it cannot catch a missing Alaska, Hawaii or Puerto Rico, or any state or province that holds none of those points. | |
| pass | SQL-001 | SQLite structure is sound (PRAGMA quick_check) | ok | ok | Wrong data in a structurally sound file, and an index whose contents do not match its table: quick_check does not verify index contents, which is SQLite's documented difference from integrity_check. IDX-001 covers the R-trees. | |
| pass | ROW-001 | No data table is empty | 0 | 0 empty tables, apart from those declared empty by design for the kind (water: waterway_lines) | A table that has rows but is missing most of them. | |
| pass | SG-004 | schema_guard layer 4: output tables clear their row floors | awy_segments 17,310 (floor 8,600); fixes 70,060 (floor 35,000); navaids 1,608 (floor 800) | every floored table at or above its floor (half an observed build) | A loss smaller than half an observed build, and a table with enough rows that are wrong. | since NASR 26-01 |
| pass | GEO-001 | Coordinates are present, valid and not at 0,0 | 0 | 0 bad coordinates. On point tables a NULL latitude or longitude is bad; on procedure and airway legs a leg with no fix position is left to PROC-FIX-001 | A plausible coordinate in the wrong place, such as a transposed digit that still lands on land. On airway_legs, a leg with a NULL fix position (no check counts those). | |
| pass | UNQ-001 | Identifiers that must be unique are unique | fixes(id) 0 | 0 duplicates | Two different things given the same correct-looking identifier in different tables, and a wrong identifier that happens to be unique. |
Black-box check (Auspex)
Not run for this edition.
Row counts
Rows per table, no previous edition was compared.
| Table | Rows | Previous | Change |
|---|---|---|---|
| awy_segments | 17,310 | — | — |
| fixes | 70,060 | — | — |
| navaids | 1,608 | — | — |
Identity
| Pack sha256 | 2cb9eca314387c9d93f0fe92cd33f509bfe989cac1e7331b88077ce41ad5725b |
|---|---|
| Size | 5,812,224 bytes |
| Content schema | 1 |
| Record | retro · raw JSON sha256 1a2a267ea201a1d0 — matches the report_sha256 in the signed catalog |
| Built | · · no CI run recorded |
| From | makerplane-data — |
| Compared against | none |
Sources
No upstream sources are recorded for this edition (see PACK-004).
Known issues
Issues found after this edition was built are not listed here yet. Until they are, see the makerplane-data issues.
What this report is and is not
These are the checks we ran on this pack, what each one measured, and what each one cannot catch. It is evidence, not a warranty and not a certification. No authority has reviewed or approved this data or these checks. Passing them does not mean the data is correct, complete or current. Results marked as coming from Auspex come from a proprietary AI test engine whose method is not published; each of its findings is stated so you can check it yourself. This data is for Experimental / Amateur-Built use. This data is provided as-is with no warranty and any use of the data is at your own risk. Verify against official publications.
Check it yourself
packtool report --check navaids-conus-2611.pack
Re-runs every open check on the pack you downloaded and compares the result with this record. How to do it.