Output Formats¶
What LAIRA produces, in what format, for which downstream consumer. The compliance matrices reference these output types; this page is the canonical schema for each.
Layered output model¶
LAIRA's outputs are structured in a four-layer hierarchy. Each layer rolls up to the next.
Per-detection record (one row per detection)
│
▼
Per-sample-unit summary (aggregated by standard's sample-unit definition)
│
▼
Per-section report (rolled up to the pavement section)
│
▼
Per-network / per-installation dashboard (cross-section trend + comparison)
Every matrix row that mentions an "output" or "report" lands somewhere in this hierarchy.
Per-detection record¶
The atomic unit. Every detected distress, marking, or FOD object produces one record.
| Field | Type | Example |
|---|---|---|
detection_id |
UUID | 7f6e2a14-b3e1-4c2a-9f80-eb44d9bd0a51 |
distress_type |
enum (per source standard) | D6433.X1.5.alligator_cracking |
severity |
enum | L / M / H |
quantity |
numeric | 12.4 |
quantity_unit |
enum | sq_ft / linear_ft / count |
latitude |
float (WGS84) | 34.0521 |
longitude |
float (WGS84) | -117.2898 |
positional_accuracy_m |
float | 0.02 |
timestamp_utc |
ISO 8601 | 2026-05-11T14:32:18Z |
inspector_vehicle_id |
string | SBD-OPS-01 |
pass_id |
UUID | (groups detections from one inspection pass) |
image_url |
string | reference imagery for the detection |
evidence_digest |
sha256 | tamper-evidence hash on the detection record |
source_standard |
enum | ASTM_D6433_20 / ASTM_D5340_23 / UFC_3_260_16 / PROWAG_2023 |
measurement_payload |
object | {"width_mm": 8.4, "length_ft": 4.2, "depth_mm": 6.0} |
Native serialization: JSON. CSV export for downstream consumers that prefer flat tables.
Per-sample-unit summary¶
Sample-unit definitions vary by source standard:
| Standard | AC Sample Unit | PCC Sample Unit |
|---|---|---|
| ASTM D5340 (airfield) | 5,000 ± 2,000 sq ft | 20 ± 8 slabs |
| ASTM D6433 (roadway) | 2,500 ± 1,000 sq ft | 20 ± 8 slabs |
The summary aggregates all per-detection records inside the sample unit and produces:
- Total quantity per distress-type / severity combination
- Density per distress type (quantity ÷ sample-unit area × 100)
- Deduct value (DV) per distress per Appendix X3 curves
- Corrected Deduct Value (CDV) per the standard's iterative procedure
- Sample unit PCI (0–100)
CSV export matching PAVER and state-DOT data dictionaries.
Per-section report¶
Section-level rollup. PDF for human review plus JSON for downstream tooling.
Contents:
- Section identification (branch, section, GIS reference, LRS station range)
- Area-weighted PCI across all sample units in the section
- Section condition rating per the source standard's PCI → rating mapping (D6433 §12; D5340 §3-4)
- Distress distribution (top 5 distress types by impact, by density)
- Per-sample-unit detail table
- Photographic evidence pack (one image per per-detection record)
- Map view with detections overlaid on satellite or facility GIS
- Trend analysis vs. prior pass (pass-over-pass change detection)
- Citation chain: every claim traces to a standard section and a measurement primitive
Native exports¶
LAIRA produces native exports for each downstream system. The export format matches the consuming system's data dictionary; the underlying data is the same per-detection records described above, restructured.
| Consumer | Format | Status |
|---|---|---|
| PAVER (DoD + civil; UFC 3-270-08, UFC 3-260-16) | CSV / XML matching PAVER import schema | In active development |
| PaveM (Caltrans) | CSV aligned to the Caltrans Linear Reference System | In active development |
| PMIS (TxDOT) | TxDOT-specific format covering Distress Score, Ride Score components | In active development |
| FDOT Flexible Pavement Condition Survey | FDOT-format crack and rut ratings | Planned |
| HPMS (FHWA, 23 CFR 490 federal submission) | Section-level CSV with IRI, cracking %, rutting, faulting per HPMS Field Manual | Planned |
| PROWAG sidewalk condition report | PDF + JSON; per-segment cross slope, running slope, vertical discontinuity, surface openings | In active development |
| MUTCD marking condition report | PDF + JSON; per-marking color, width, retroreflectivity screening, condition score | In active development |
| FOD spatial report | JSON + heatmap PDF; per-zone density, material breakdown, temporal trend | Validated |
| Digital twin annotation | GeoJSON overlay on facility map | Validated |
Tamper evidence¶
Every detection record includes a SHA-256 evidence_digest over the structured payload plus the reference imagery. The digest is what downstream auditors (FAA inspectors, AFCEC evaluators, plaintiffs' counsel in a consent-decree forum) can use to confirm the record has not been modified after capture. The digest signing key and rotation policy are described in the security whitepaper.
Where matrices cite this page¶
| Matrix | Rows that anchor here |
|---|---|
| Civil Airfields | Data record requirements, By the Numbers comparison |
| Military Airfields | §8 Data Output & PAVER Integration |
| Federal & State Roads | §6 Output table |
| Military Roads | PAVER export for DoD road network |
| Parking Lots | D6433 PCI + accessible-parking compliance report |
| Sidewalks & Curb Ramps | Per-segment PROWAG geometric records |
| Roadway Markings (MUTCD) | Per-marking condition report |