METHOD / STANDARD

Methodology

OpenODC measures how clearly public sources describe operational boundaries. It is not a safety certification and it does not rank automated-driving capability.

Baseline publishing rule

Unless a record is marked vendor_confirmed, OpenODC samples are community extractions from public sources. L2 records describe feature availability boundaries, not permission to stop supervising; L3/L4 records are the cases where an ADS may take responsibility for the dynamic driving task inside an ODD.

What OpenODC Does

Structures Public Evidence

Maps owner manuals, official pages, app operating rules, government notices, and third-party tests to the 144 ODC elements in GB/T 45312—2025.

Measures Gaps

Separates official evidence, owner-manual evidence, community extraction, inference, and elements that are not clearly stated in public sources.

Enables Comparison

Compares vehicles, functions, and automation levels through the same element vocabulary instead of comparing product names.

ODC and ODD

ODD usually describes the roads, environment, traffic, speed, geography, and other conditions in which an Automated Driving System is designed to operate. GB/T 45312—2025 provides an ODC element hierarchy that turns those boundaries into a checklist that can be authored, validated, and compared. OpenODC implements that checklist as JSON Schema and web tooling.

System TypeMeaning in OpenODCMain Risk
L2 driver assistanceFeature availability and exit / suppression conditions; the driver continuously supervises the dynamic driving taskMisreading “available” as “system responsible”
L3 conditional automationThe boundary under which the ADS performs the dynamic driving task, plus fallback-ready user responsibilitiesDeclaring road and weather while omitting fallback conditions
L4 robotaxi / ADSService operating boundary, usually including geofence, operating hours, weather, remote assistance, permit scope, and app rulesMisreading a pilot geofence as nationwide capability

Evidence Levels

TagMeaningCounts Toward Coverage
Official statementVendor website, official press release, official configuration table, or official robotaxi operating ruleYes, highest confidence
Owner manualOwner manual or product manual explicitly states the condition, threshold, or warningYes, highest confidence
Community extractionPublic sources support a directional interpretation but not a complete quantitative thresholdYes, but source traceability is required
InferredDerived from architecture, regulation, domain knowledge, or indirect public evidenceYes, but it is never treated as vendor disclosure
Not clearly statedNo public source explicitly states the elementNo; this is a gap
StructuralA parent node in the standard hierarchy; the actual judgment is made in child elementsNo substantive coverage

Coverage Metric

The Gallery coverage number is not a vendor disclosure rate. It is the number of GB/T elements for which OpenODC can build a public-source explanation: official statements + owner manuals + community extraction + inference. The UI also shows the number of elements not clearly stated in public sources so gaps are not mistaken for capability.

Reference Standards