AeroCommonsNavigation Data · test reports · check it yourself

Airports (regional) airports-canada · 2026.06

community · airports · 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 7   warn 0   fail 1   not run 3

Show:

CheckWhat it checks MeasuredExpectedCannot catch
failPACK-002Attribution and license are recorded in pack_metamissing: licenseboth non-emptyA license tag or attribution that is present but wrong for the data.
not runPACK-004
non-blocking
Upstream sources are recorded—at least one source, each with a non-empty edition and a 64-hex sha256A 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 runROW-002
non-blocking
Row counts against the previous edition—Provisional threshold: no table moves more than 10%; a larger move needs a build noteA 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 runROW-003No table of the previous edition has disappeared—every table in the previous edition is still present, unless schema_version changedA 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
passPACK-001pack_meta is readable and names a known kindid=airports-canada kind=airports cycle=2026.06 schema_version=1pack_meta present; kind is one the device knowsA pack_meta that is well formed but names the wrong id or cycle for the bytes inside.
passPACK-003Origin label is federal, community or user-suppliedcommunity (defaulted by kind airports, not read from the pack)one of federal / community / user-suppliedWhether 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
passACC-001Device acceptance: pyEfis's own reader opens the pack and answers a fixed query setopened; 2/2 queries returned datathe reader opens the pack and every query returns dataWrong 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.
passSQL-001SQLite structure is sound (PRAGMA quick_check)okokWrong 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.
passROW-001No data table is empty00 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.
passGEO-001Coordinates are present, valid and not at 0,000 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-001A 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).
passUNQ-001Identifiers that must be unique are uniqueairports(icao) 00 duplicatesTwo 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.

TableRowsPreviousChange
airports1,490——
runway_ends1,456——
runways728——

Identity

Pack sha2569e08ec278d68a9c524556fef4f587e0dd21630c76e4d4c07d6bf14d140772b75
Size393,216 bytes
Content schema1
Recordretro · raw JSON sha256 402c208425176cf2 — matches the report_sha256 in the signed catalog
Built · · no CI run recorded
Frommakerplane-data —
Compared againstnone

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 airports-canada-2026.06.pack

Re-runs every open check on the pack you downloaded and compares the result with this record. How to do it.