vehicles 0.9.0 → 0.9.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +57 -7
- data/README.md +353 -69
- data/data/PROVENANCE-vehicles.md +2 -2
- data/data/plates/PROVENANCE.md +2 -2
- data/data/plates/_decode/at-districts.yml +2 -2
- data/data/plates/_decode/cn-issuing-offices.yml +2 -2
- data/data/plates/_decode/cn-provinces.yml +2 -2
- data/data/plates/_decode/cz-kraj.yml +1 -1
- data/data/plates/_decode/dk-serial-blocks.yml +1 -1
- data/data/plates/_decode/es-provinces.yml +1 -1
- data/data/plates/_decode/fr-departements.yml +2 -2
- data/data/plates/_decode/gb-age-identifiers.yml +1 -1
- data/data/plates/_decode/gb-memory-tags.yml +1 -1
- data/data/plates/_decode/gr-prefectures.yml +1 -1
- data/data/plates/_decode/hr-cities.yml +3 -3
- data/data/plates/_decode/ie-counties.yml +3 -3
- data/data/plates/_decode/in-state-codes.yml +2 -2
- data/data/plates/_decode/it-provinces.yml +3 -3
- data/data/plates/_decode/jp-office-marks.yml +2 -2
- data/data/plates/_decode/jp-use-marks.yml +2 -2
- data/data/plates/_decode/kr-authority-marks.yml +1 -1
- data/data/plates/_decode/mx-entity-series.yml +1 -1
- data/data/plates/_decode/my-index-marks.yml +4 -4
- data/data/plates/_decode/pt-trailer-services.yml +1 -1
- data/data/plates/_decode/ro-counties.yml +1 -1
- data/data/plates/_decode/se-diplomatic.yml +1 -1
- data/data/plates/_decode/si-regions.yml +1 -1
- data/data/plates/_decode/ua-regions.yml +1 -1
- data/data/plates/_meta/classes.yml +1 -1
- data/data/plates/_meta/separators.yml +1 -1
- data/data/plates/ad.yml +555 -52
- data/data/plates/ar.yml +8 -8
- data/data/plates/at.yml +91 -10
- data/data/plates/au-act.yml +13 -13
- data/data/plates/au-nsw.yml +9 -9
- data/data/plates/au-nt.yml +13 -14
- data/data/plates/au-qld.yml +7 -7
- data/data/plates/au-sa.yml +7 -7
- data/data/plates/au-tas.yml +10 -10
- data/data/plates/au-vic.yml +6 -6
- data/data/plates/au-wa.yml +8 -8
- data/data/plates/be.yml +11 -11
- data/data/plates/br.yml +14 -14
- data/data/plates/ca-ab.yml +10 -10
- data/data/plates/ca-bc.yml +6 -6
- data/data/plates/ca-mb.yml +4 -4
- data/data/plates/ca-nb.yml +9 -9
- data/data/plates/ca-nl.yml +11 -11
- data/data/plates/ca-ns.yml +12 -12
- data/data/plates/ca-nt.yml +7 -7
- data/data/plates/ca-nu.yml +7 -7
- data/data/plates/ca-on.yml +21 -21
- data/data/plates/ca-pe.yml +13 -13
- data/data/plates/ca-qc.yml +11 -11
- data/data/plates/ca-sk.yml +6 -6
- data/data/plates/ca-yt.yml +6 -6
- data/data/plates/ch.yml +14 -14
- data/data/plates/cn.yml +9 -9
- data/data/plates/cy.yml +6 -6
- data/data/plates/cz.yml +9 -9
- data/data/plates/de.yml +8 -8
- data/data/plates/dk.yml +12 -12
- data/data/plates/ee.yml +13 -13
- data/data/plates/eg.yml +708 -0
- data/data/plates/es.yml +8 -8
- data/data/plates/fi.yml +14 -14
- data/data/plates/fr.yml +12 -12
- data/data/plates/gb.yml +16 -16
- data/data/plates/gr.yml +14 -14
- data/data/plates/hr.yml +15 -15
- data/data/plates/hu.yml +16 -16
- data/data/plates/ie.yml +7 -7
- data/data/plates/in.yml +7 -7
- data/data/plates/is.yml +3 -3
- data/data/plates/it.yml +21 -21
- data/data/plates/jp.yml +121 -121
- data/data/plates/kr.yml +6 -6
- data/data/plates/li.yml +6 -6
- data/data/plates/lt.yml +10 -10
- data/data/plates/lu.yml +4 -4
- data/data/plates/lv.yml +9 -9
- data/data/plates/mc.yml +4 -4
- data/data/plates/mt.yml +5 -5
- data/data/plates/mx.yml +7 -7
- data/data/plates/my.yml +18 -18
- data/data/plates/ng.yml +346 -0
- data/data/plates/nl.yml +5 -5
- data/data/plates/no.yml +7 -7
- data/data/plates/nz.yml +18 -18
- data/data/plates/pl.yml +4 -4
- data/data/plates/pt.yml +13 -5
- data/data/plates/ro.yml +14 -14
- data/data/plates/se.yml +13 -13
- data/data/plates/si.yml +8 -8
- data/data/plates/sk.yml +15 -15
- data/data/plates/sm.yml +7 -7
- data/data/plates/th.yml +10 -10
- data/data/plates/tr.yml +432 -0
- data/data/plates/ua.yml +9 -9
- data/data/plates/us-ak.yml +11 -11
- data/data/plates/us-al.yml +12 -12
- data/data/plates/us-ar.yml +15 -15
- data/data/plates/us-as.yml +10 -10
- data/data/plates/us-az.yml +10 -10
- data/data/plates/us-ca.yml +13 -13
- data/data/plates/us-co.yml +14 -14
- data/data/plates/us-ct.yml +24 -24
- data/data/plates/us-dc.yml +7 -7
- data/data/plates/us-de.yml +10 -10
- data/data/plates/us-fl.yml +17 -17
- data/data/plates/us-ga.yml +10 -10
- data/data/plates/us-gu.yml +11 -11
- data/data/plates/us-hi.yml +11 -11
- data/data/plates/us-ia.yml +9 -9
- data/data/plates/us-id.yml +13 -13
- data/data/plates/us-il.yml +11 -11
- data/data/plates/us-in.yml +9 -9
- data/data/plates/us-ks.yml +8 -8
- data/data/plates/us-ky.yml +11 -11
- data/data/plates/us-la.yml +11 -11
- data/data/plates/us-ma.yml +10 -10
- data/data/plates/us-md.yml +7 -7
- data/data/plates/us-me.yml +16 -16
- data/data/plates/us-mi.yml +8 -8
- data/data/plates/us-mn.yml +13 -13
- data/data/plates/us-mo.yml +13 -13
- data/data/plates/us-mp.yml +12 -12
- data/data/plates/us-ms.yml +8 -8
- data/data/plates/us-mt.yml +12 -12
- data/data/plates/us-nc.yml +12 -12
- data/data/plates/us-nd.yml +10 -10
- data/data/plates/us-ne.yml +10 -10
- data/data/plates/us-nh.yml +8 -8
- data/data/plates/us-nj.yml +8 -8
- data/data/plates/us-nm.yml +14 -14
- data/data/plates/us-nv.yml +18 -18
- data/data/plates/us-ny.yml +17 -17
- data/data/plates/us-oh.yml +13 -13
- data/data/plates/us-ok.yml +12 -12
- data/data/plates/us-or.yml +15 -15
- data/data/plates/us-pa.yml +14 -14
- data/data/plates/us-pr.yml +15 -15
- data/data/plates/us-ri.yml +10 -10
- data/data/plates/us-sc.yml +7 -7
- data/data/plates/us-sd.yml +12 -12
- data/data/plates/us-tn.yml +8 -8
- data/data/plates/us-tx.yml +17 -17
- data/data/plates/us-ut.yml +12 -12
- data/data/plates/us-va.yml +14 -14
- data/data/plates/us-vi.yml +16 -16
- data/data/plates/us-vt.yml +9 -9
- data/data/plates/us-wa.yml +18 -18
- data/data/plates/us-wi.yml +8 -8
- data/data/plates/us-wv.yml +9 -9
- data/data/plates/us-wy.yml +10 -10
- data/data/plates/va.yml +7 -7
- data/data/plates/za.yml +11 -11
- data/data/vehicles.json +121081 -62015
- data/lib/generators/vehicles/templates/initializer.rb +21 -12
- data/lib/generators/vehicles/templates/vehicles_refresh_job.rb +8 -4
- data/lib/vehicles/color.rb +8 -1
- data/lib/vehicles/colors.rb +14 -10
- data/lib/vehicles/configuration.rb +82 -3
- data/lib/vehicles/data_source.rb +220 -0
- data/lib/vehicles/dataset.rb +38 -6
- data/lib/vehicles/dataset_resolution.rb +39 -3
- data/lib/vehicles/dataset_slice.rb +90 -0
- data/lib/vehicles/hosted_result.rb +94 -0
- data/lib/vehicles/http.rb +75 -7
- data/lib/vehicles/id_lookup.rb +37 -0
- data/lib/vehicles/kind_rule.rb +63 -0
- data/lib/vehicles/labels.rb +131 -0
- data/lib/vehicles/make.rb +45 -19
- data/lib/vehicles/model.rb +66 -19
- data/lib/vehicles/model_match.rb +16 -2
- data/lib/vehicles/model_matcher.rb +6 -7
- data/lib/vehicles/plates/series.rb +87 -8
- data/lib/vehicles/plates/template_fill.rb +2 -2
- data/lib/vehicles/plates/templates.rb +9 -5
- data/lib/vehicles/plates.rb +54 -8
- data/lib/vehicles/providers/hosted_provider.rb +145 -32
- data/lib/vehicles/providers/local_provider.rb +2 -2
- data/lib/vehicles/refresh_result.rb +74 -0
- data/lib/vehicles/refresher.rb +190 -54
- data/lib/vehicles/release_checks.rb +72 -0
- data/lib/vehicles/text_matcher.rb +19 -10
- data/lib/vehicles/validators/vehicle_make_validator.rb +18 -1
- data/lib/vehicles/validators/vehicle_model_validator.rb +17 -1
- data/lib/vehicles/version.rb +1 -1
- data/lib/vehicles.rb +119 -67
- data/rakelib/data_refresh.rake +1 -1
- data/rakelib/plates_refresh.rake +1 -1
- data/sig/vehicles.rbs +67 -13
- metadata +13 -2
data/data/plates/us-co.yml
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# plates/us-co.yml — Colorado (
|
|
1
|
+
# plates/us-co.yml — Colorado (the plates spec gate L2, mountain group).
|
|
2
2
|
#
|
|
3
3
|
# WHY COLORADO IS UNUSUAL, stated up front: it is the only state in this group
|
|
4
4
|
# whose legislature legislates the SERIAL LENGTH and the COLOURS OF ITS OWN
|
|
@@ -14,7 +14,7 @@
|
|
|
14
14
|
# public records. See `artwork_risk` — this is a pinned primary, not an
|
|
15
15
|
# inference from a secondary summary.
|
|
16
16
|
#
|
|
17
|
-
# SOURCING RULE APPLIED HERE (
|
|
17
|
+
# SOURCING RULE APPLIED HERE (the plates spec §4): edicts of government are public
|
|
18
18
|
# domain at every level, so every claim that CAN come from Title 42 does. The
|
|
19
19
|
# Colorado Revised Statutes 2023 were read as the Colorado General Assembly's
|
|
20
20
|
# own PDF (Office of Legislative Legal Services). The Division of Motor
|
|
@@ -22,7 +22,7 @@
|
|
|
22
22
|
# designs are currently offered, the group-special catalogue, and the
|
|
23
23
|
# manufacture/Print-On-Demand arrangements.
|
|
24
24
|
#
|
|
25
|
-
# WHAT IS NOT HERE (
|
|
25
|
+
# WHAT IS NOT HERE (the plates spec §2.5): individual group-special DESIGNS. The
|
|
26
26
|
# index entry `us-co-group-special-index` stands for the whole programme.
|
|
27
27
|
jurisdiction: us-co
|
|
28
28
|
authority:
|
|
@@ -36,7 +36,7 @@ statute_edition: >-
|
|
|
36
36
|
it is nevertheless the legislature's own edition, which is what §4 asks for.
|
|
37
37
|
|
|
38
38
|
# ---------------------------------------------------------------------------
|
|
39
|
-
# artwork_risk — required per jurisdiction by
|
|
39
|
+
# artwork_risk — required per jurisdiction by the plates spec §4.
|
|
40
40
|
# ---------------------------------------------------------------------------
|
|
41
41
|
artwork_risk:
|
|
42
42
|
posture: adverse-copyright-authorised-by-statute
|
|
@@ -61,10 +61,10 @@ artwork_risk:
|
|
|
61
61
|
table. Nothing in the section touches the uncopyrightability of facts, and
|
|
62
62
|
nothing in it reaches the STATUTE itself: § 42-3-201, § 42-3-206.5 and
|
|
63
63
|
§ 42-3-211 are edicts of government and public domain at every level
|
|
64
|
-
(
|
|
64
|
+
(the plates spec §4). So the facts in this file are clean; the RENDERED MOUNTAIN
|
|
65
65
|
GRAPHIC is the exposure, and it routes through the strict path.
|
|
66
66
|
emblem_rule: >-
|
|
67
|
-
|
|
67
|
+
the plates spec §3 placeholder default applies with extra force here. The
|
|
68
68
|
Colorado mountain-range graphic is the single most recognisable element of
|
|
69
69
|
the plate and it has been continuously in use since 1960 — render
|
|
70
70
|
`graphic: {present: true, rendered: placeholder}` and do not trace, do not
|
|
@@ -80,7 +80,7 @@ artwork_risk:
|
|
|
80
80
|
adverse-posture state renderable at all.
|
|
81
81
|
sources:
|
|
82
82
|
- "https://leg.colorado.gov/sites/default/files/images/olls/crs2023-title-24.pdf # § 24-72-203(4): the state is 'specifically authorized to obtain and enforce' copyright over public records; the fair-use and mere-lists carve-outs; Source note L. 92 p. 1104 § 3"
|
|
83
|
-
- "https://en.wikipedia.org/wiki/Copyright_status_of_works_by_subnational_governments_of_the_United_States # LOCATOR ONLY (
|
|
83
|
+
- "https://en.wikipedia.org/wiki/Copyright_status_of_works_by_subnational_governments_of_the_United_States # LOCATOR ONLY (the plates spec §4) — this is where the § 24-72-203 pointer was found; the statute above was then read directly and is what is cited"
|
|
84
84
|
|
|
85
85
|
# ---------------------------------------------------------------------------
|
|
86
86
|
# The US standards chain. Recorded per file because each state file must stand
|
|
@@ -192,7 +192,7 @@ series:
|
|
|
192
192
|
letter, two numerals, six characters in all, which sits exactly at the
|
|
193
193
|
statutory cap. `regex_statutory` encodes what § 42-3-201(5)(a) actually
|
|
194
194
|
permits: up to six alphanumerics, written in PRINTED form per
|
|
195
|
-
|
|
195
|
+
the plates spec §2.6 rule 2 so that it accepts the hyphen the plate shows.
|
|
196
196
|
progression: >-
|
|
197
197
|
Not alphabetical in issuance. The DMV's own explanation, via the
|
|
198
198
|
collector record: plates are MANUFACTURED alphabetically but ISSUED from
|
|
@@ -232,7 +232,7 @@ series:
|
|
|
232
232
|
sources:
|
|
233
233
|
- "https://leg.colorado.gov/sites/default/files/images/olls/crs2023-title-42.pdf # § 42-3-201(5)(a): the SIX-CHARACTER cap, 'standardized coloring', and the personalized-plate exception; (2): displayed content and the 100-foot legibility rule"
|
|
234
234
|
- "https://dmv.colorado.gov/license-plates # Colorado DMV: all Colorado plates are printed by Colorado Correctional Industries; the Print-On-Demand programme for low-issuance plates; plate expiry on transfer under SB 21-069"
|
|
235
|
-
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Colorado # LOCATOR ONLY (
|
|
235
|
+
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Colorado # LOCATOR ONLY (the plates spec §4): the mid-2018 arrangement change, the AAA-A00 start, the mountain-base continuity since 1960 and the January 2000 screened redesign. None is asserted as sourced."
|
|
236
236
|
notes: >-
|
|
237
237
|
COLORADO STANDARD ISSUE, CURRENT ARRANGEMENT. The id carries 2018 because
|
|
238
238
|
the format boundary is what makes this a distinct series, but
|
|
@@ -243,7 +243,7 @@ series:
|
|
|
243
243
|
2000 and the mountain motif to 1960 — so a reader must not read this
|
|
244
244
|
series' start as a redesign date. If the department publishes an issuance
|
|
245
245
|
record, this id keeps its meaning and only the period sharpens; if the
|
|
246
|
-
boundary moves, the
|
|
246
|
+
boundary moves, the quality spec I-5/I-6 alias contract applies.
|
|
247
247
|
|
|
248
248
|
# =========================================================================
|
|
249
249
|
# ONE SERIES BACK. Same base design, previous arrangement.
|
|
@@ -365,7 +365,7 @@ series:
|
|
|
365
365
|
- "https://dmv.colorado.gov/license-plates # Colorado DMV: the application-then-approval-then-payment sequence, 6-8 week production, and the $60 one-time / $25 annual figures quoted on the FAQ (note the discrepancy against the statute's $35/$25 — recorded, not reconciled)"
|
|
366
366
|
notes: >-
|
|
367
367
|
PERSONALIZED PLATES. A DISCREPANCY IS RECORDED RATHER THAN AVERAGED
|
|
368
|
-
(
|
|
368
|
+
(the plates spec §5.3): § 42-3-211(6)(a) states $35 on issuance and $25 on
|
|
369
369
|
reissuance, while the DMV's own FAQ states "a one-time personalization fee
|
|
370
370
|
of $60 upon their initial registration and are an additional $25 upon
|
|
371
371
|
renewal each year after". Both are cited above with their sources; neither
|
|
@@ -375,7 +375,7 @@ series:
|
|
|
375
375
|
bound; Colorado has issued personalized plates for decades.
|
|
376
376
|
|
|
377
377
|
# =========================================================================
|
|
378
|
-
# SPECIALTY — THE PROGRAM INDEX, per
|
|
378
|
+
# SPECIALTY — THE PROGRAM INDEX, per the plates spec §2.5.
|
|
379
379
|
# =========================================================================
|
|
380
380
|
- id: us-co-group-special-index
|
|
381
381
|
class: specialty
|
|
@@ -397,7 +397,7 @@ series:
|
|
|
397
397
|
design:
|
|
398
398
|
plate: { w: 12, h: 6, unit: in }
|
|
399
399
|
background: { finish: retroreflective }
|
|
400
|
-
note: "one design per authorised programme; the designs themselves are L4 scope (
|
|
400
|
+
note: "one design per authorised programme; the designs themselves are L4 scope (the plates spec §2.5) and none is described here"
|
|
401
401
|
emblem: { present: true, rendered: placeholder }
|
|
402
402
|
program_index:
|
|
403
403
|
count_measured: 50
|
|
@@ -441,7 +441,7 @@ series:
|
|
|
441
441
|
- "https://dmv.colorado.gov/group-special-license-plates # the Colorado DMV's own group-special catalogue — the page the count of 50 was measured from, archived 2024-01-21"
|
|
442
442
|
notes: >-
|
|
443
443
|
THE GROUP-SPECIAL PROGRAM INDEX — one entry for the whole programme, which
|
|
444
|
-
is what
|
|
444
|
+
is what the plates spec §2.5 asks for at this gate. Two things worth carrying
|
|
445
445
|
forward. First, Colorado's programme is STATUTE-SHAPED in a way Florida's
|
|
446
446
|
is not: the rulemaking route closed on 1 January 2001, so the catalogue is
|
|
447
447
|
literally a list of sections of Title 42, and a future pass can enumerate
|
data/data/plates/us-ct.yml
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# plates/us-ct.yml — Connecticut (
|
|
1
|
+
# plates/us-ct.yml — Connecticut (the plates spec gate L2, northeast group).
|
|
2
2
|
#
|
|
3
3
|
# WHY CONNECTICUT IS UNUSUAL, and what the statute actually carries: Connecticut
|
|
4
4
|
# is one of the few states whose CURRENT BASE HAS A STATUTORY START DATE and
|
|
@@ -11,7 +11,7 @@
|
|
|
11
11
|
# are all primary — not brochure, not folklore. What the statute does NOT carry
|
|
12
12
|
# is the SERIAL GRAMMAR: Chapter 246 nowhere states a character count, an
|
|
13
13
|
# alphabet or a dimension. Every serial claim below is therefore secondary and
|
|
14
|
-
# is labelled as such (
|
|
14
|
+
# is labelled as such (the plates spec §4: Wikipedia is a LOCATOR; ctplates.info and
|
|
15
15
|
# licenseplates.cc are enthusiast corroboration, cited because they were used).
|
|
16
16
|
#
|
|
17
17
|
# THE SEPARATOR PROBLEM, recorded here because Connecticut is the first
|
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
# between serial groups (AB·12345), not a hyphen and not a space. U+00B7 is in
|
|
20
20
|
# `_meta/separators.yml`'s FORGIVING set — so a lenient consumer already strips
|
|
21
21
|
# it correctly — but it is NOT in the EMITTED set, so the dataset may not spell
|
|
22
|
-
# it (
|
|
22
|
+
# it (the plates spec §2.6). Every pattern and regex below therefore writes the gap
|
|
23
23
|
# as U+0020 and this note carries the fact. That is a data-honest workaround,
|
|
24
24
|
# not a silent one; whether the emitted set should grow a third member is a
|
|
25
25
|
# `_meta` PR question and is raised in the group dossier, not decided here.
|
|
@@ -37,7 +37,7 @@ statute_edition: >-
|
|
|
37
37
|
Assembly and revised to January 1, 2026 — the edition read for this pass.
|
|
38
38
|
|
|
39
39
|
# ---------------------------------------------------------------------------
|
|
40
|
-
# artwork_risk — required per jurisdiction by
|
|
40
|
+
# artwork_risk — required per jurisdiction by the plates spec §4.
|
|
41
41
|
# ---------------------------------------------------------------------------
|
|
42
42
|
artwork_risk:
|
|
43
43
|
posture: adverse-evidence-found
|
|
@@ -65,7 +65,7 @@ artwork_risk:
|
|
|
65
65
|
property, and nothing in the corpus suggests the standard base is treated
|
|
66
66
|
differently.
|
|
67
67
|
emblem_rule: >-
|
|
68
|
-
|
|
68
|
+
the plates spec §3 placeholder default applies without exception here. The
|
|
69
69
|
Connecticut base carries a screened STATE SHAPE at top left; state-shape and
|
|
70
70
|
state-seal protection independent of copyright is unresearched for
|
|
71
71
|
Connecticut (recorded gap, same gap the FL pilot recorded).
|
|
@@ -73,7 +73,7 @@ artwork_risk:
|
|
|
73
73
|
Commons photographs of Connecticut plates carry the PHOTOGRAPHER's licence,
|
|
74
74
|
not the design's — the uploader had no standing over the design. Because our
|
|
75
75
|
renders are generated from spec and never derived from a photograph, those
|
|
76
|
-
obligations never attach (
|
|
76
|
+
obligations never attach (the plates spec §4, §6).
|
|
77
77
|
sources:
|
|
78
78
|
- "https://www.cga.ct.gov/current/pub/chap_246.htm # C.G.S. § 14-21w(a) 'No use shall be made of such plates except as official registration marker plates'; § 14-21w(e) the reproduction-and-marketing authority over the plate IMAGE — the adverse evidence"
|
|
79
79
|
- "https://commons.wikimedia.org/w/api.php?action=query&titles=Template:PD-CTGov # queried this pass: Template:PD-CTGov is MISSING on Commons — no Connecticut public-domain tag exists, unlike PD-FLGov/PD-CAGov/PD-MAGov/PD-MEGov"
|
|
@@ -135,7 +135,7 @@ series:
|
|
|
135
135
|
character-count or character-set rule for standard plates, so this
|
|
136
136
|
exclusion is secondary (Wikipedia locator, sourced there to a Hartford
|
|
137
137
|
Courant report of the September 2015 changeover). It is recorded as a
|
|
138
|
-
note and deliberately NOT promoted to a `regex_strict`:
|
|
138
|
+
note and deliberately NOT promoted to a `regex_strict`: The plates spec
|
|
139
139
|
reserves the strict twin for the AUTHORITY's own alphabet, and laundering
|
|
140
140
|
a newspaper report into a strict twin is exactly the folklore failure
|
|
141
141
|
§4 forbids.
|
|
@@ -143,7 +143,7 @@ series:
|
|
|
143
143
|
THE PRINTED SEPARATOR IS A RAISED MIDDLE DOT (U+00B7): the plate reads
|
|
144
144
|
AB·12345. U+00B7 is in `_meta/separators.yml`'s FORGIVING set but not its
|
|
145
145
|
EMITTED set, so the dataset spells the gap as U+0020 here and records the
|
|
146
|
-
true glyph in this note (
|
|
146
|
+
true glyph in this note (the plates spec §2.6). A lenient consumer already
|
|
147
147
|
strips U+00B7 correctly; a consumer RENDERING from this data must read
|
|
148
148
|
this note, not the pattern, to place the dot.
|
|
149
149
|
progression: "AA 00001 upward; reported at BW 99865 as of 31 October 2025 (licenseplates.cc — enthusiast corroboration, cited because used)"
|
|
@@ -171,14 +171,14 @@ series:
|
|
|
171
171
|
region_encoding: none
|
|
172
172
|
sources:
|
|
173
173
|
- "https://www.cga.ct.gov/current/pub/chap_246.htm # § 14-21b(a): fully reflectorized plates for registrations issued on and after January 1, 2000; the 'Constitution State' and 'Connecticut' legends; two plates issued. § 14-18: display"
|
|
174
|
-
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Connecticut # LOCATOR ONLY (
|
|
174
|
+
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Connecticut # LOCATOR ONLY (the plates spec §4): the August 2015 introduction of the seven-character AB·12345 arrangement, the I/O/Q exclusion, and the AA·00001 start. Its own citation for the changeover is a Hartford Courant news report of 18 September 2015"
|
|
175
175
|
- "https://www.licenseplates.cc/CT # enthusiast corroboration, cited because used: the reported serial high-water mark BW·99865 as of 31 October 2025. No text or image copied"
|
|
176
176
|
notes: >-
|
|
177
177
|
CONNECTICUT CURRENT STANDARD. THE ID IS DATED 2015, NOT 2000, and that is a
|
|
178
178
|
deliberate schema decision: the DESIGN base is statutory from 1 January 2000
|
|
179
179
|
(§ 14-21b) but the SERIAL GRAMMAR changed twice on that base — to the interim
|
|
180
180
|
1ABCD2 and 1AB·CD2 shapes in 2013, and to the present AB·12345 shape in
|
|
181
|
-
August 2015.
|
|
181
|
+
August 2015. The plates spec §2.3 makes a format change its own series, so the
|
|
182
182
|
2000 base carries three passenger series, of which this is the current one.
|
|
183
183
|
PERIOD EVIDENCE: `secondary-dated` — the 2015 date is a news/locator claim,
|
|
184
184
|
not a statutory one; the STATUTORY date that is beyond doubt is 2000, and it
|
|
@@ -205,7 +205,7 @@ series:
|
|
|
205
205
|
Reported: the 'O' series was not used and the 'V' series was reserved
|
|
206
206
|
for Veteran plates. Secondary (locator) — not promoted to a strict twin,
|
|
207
207
|
for the reason given on us-ct-standard-2015.
|
|
208
|
-
separator_note: "printed as a raised middle dot (123·ABC); spelled U+0020 here per
|
|
208
|
+
separator_note: "printed as a raised middle dot (123·ABC); spelled U+0020 here per the plates spec §2.6 — see the file header"
|
|
209
209
|
progression: "100 NZN to 999 ZZX — i.e. it CONTINUED the sequence of the 1987-1999 base rather than restarting, which is why the 2000 base's first plate is not 100 AAA"
|
|
210
210
|
design:
|
|
211
211
|
plate: { w: 12, h: 6, unit: in }
|
|
@@ -242,7 +242,7 @@ series:
|
|
|
242
242
|
pattern: "00 LLLL"
|
|
243
243
|
regex: '\A00 ?[A-Z]{4}\z'
|
|
244
244
|
charset: { notes: "a literal '00' prefix followed by four letters — the two zeros are part of the serial, not a pad. Reported secondary; no statutory grammar exists" }
|
|
245
|
-
separator_note: "printed as a raised middle dot (00·ABCD); spelled U+0020 here per
|
|
245
|
+
separator_note: "printed as a raised middle dot (00·ABCD); spelled U+0020 here per the plates spec §2.6"
|
|
246
246
|
design:
|
|
247
247
|
plate: { w: 7, h: 4, unit: in, dimension_note: "MOTORCYCLE PLATE SIZE NOT OBTAINED — Connecticut's statute states no dimension for any plate and no departmental spec was found. This entry is a PLACEHOLDER carrying the conventional US motorcycle size and must not be treated as sourced (recorded gap)" }
|
|
248
248
|
background: { finish: retroreflective }
|
|
@@ -258,7 +258,7 @@ series:
|
|
|
258
258
|
MOTORCYCLE. The 00·ABCD block is reported to be SHARED with the Classic
|
|
259
259
|
Vehicle series — two different classes drawing from one serial space, which
|
|
260
260
|
means a serial alone does not determine the class and a parse API must
|
|
261
|
-
return both candidates. That is precisely the ambiguity model
|
|
261
|
+
return both candidates. That is precisely the ambiguity model the paid-API spec's
|
|
262
262
|
parse endpoint is specified to expose (ranked candidates, not one answer),
|
|
263
263
|
and Connecticut is the first US case of it in this dataset.
|
|
264
264
|
|
|
@@ -272,7 +272,7 @@ series:
|
|
|
272
272
|
pattern: "LL 99999"
|
|
273
273
|
regex: '\A[A-Z]{2} ?\d{5}\z'
|
|
274
274
|
charset: { notes: "commercial trailers now draw the same AB·12345 grammar as passenger plates; the older V·12345 and W·12345 prefixed forms are reported to remain on the road (secondary)" }
|
|
275
|
-
separator_note: "printed as a raised middle dot; spelled U+0020 here per
|
|
275
|
+
separator_note: "printed as a raised middle dot; spelled U+0020 here per the plates spec §2.6"
|
|
276
276
|
design:
|
|
277
277
|
plate: { w: 12, h: 6, unit: in }
|
|
278
278
|
background: { finish: retroreflective }
|
|
@@ -287,7 +287,7 @@ series:
|
|
|
287
287
|
TRAILER. Connecticut differentiates several non-passenger classes by SERIAL
|
|
288
288
|
COLOUR (red) on an otherwise identical base — Trailer, Commercial,
|
|
289
289
|
Apportioned, Construction, Factory, Farm and Fire Apparatus all reportedly
|
|
290
|
-
share the red-serial treatment. Under
|
|
290
|
+
share the red-serial treatment. Under the plates spec §2.3 a colour-only variant
|
|
291
291
|
of the same format+period is a sub-entry rather than a series; these are
|
|
292
292
|
given separate entries only where the FORMAT also differs. Trailer earns its
|
|
293
293
|
own entry because it also carries a distinct bottom legend, which is a
|
|
@@ -312,13 +312,13 @@ series:
|
|
|
312
312
|
this series is `recall-only`: the regex is a union across five reported
|
|
313
313
|
width combinations per prefix and is wider than any single issuing
|
|
314
314
|
grammar.
|
|
315
|
-
separator_note: "printed as a raised middle dot (XA·0); spelled U+0020 here per
|
|
315
|
+
separator_note: "printed as a raised middle dot (XA·0); spelled U+0020 here per the plates spec §2.6"
|
|
316
316
|
design:
|
|
317
317
|
plate: { w: 12, h: 6, unit: in }
|
|
318
318
|
background: { finish: retroreflective }
|
|
319
319
|
legend_bottom: "Dealer"
|
|
320
320
|
binding: business
|
|
321
|
-
region_encoding: "the NUMERIC SUFFIX identifies the DEALERSHIP, not a geography — a business decode, not a region decode. No decode table was obtained (recorded gap); it would be a per-dealer registry, which is out of
|
|
321
|
+
region_encoding: "the NUMERIC SUFFIX identifies the DEALERSHIP, not a geography — a business decode, not a region decode. No decode table was obtained (recorded gap); it would be a per-dealer registry, which is out of the plates spec scope in any event"
|
|
322
322
|
sources:
|
|
323
323
|
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Connecticut # LOCATOR ONLY: the X/D/MX/MD dealer prefixes, the five reported width combinations each, and the rule that the numeric suffix signifies the dealership"
|
|
324
324
|
- "https://www.cga.ct.gov/current/pub/chap_246.htm # § 14-21c: number plates for manufacturers of motor vehicles or automotive equipment — the statutory hook for the manufacturer end of this class; the dealer grammar itself is not in Chapter 246 (recorded gap)"
|
|
@@ -346,7 +346,7 @@ series:
|
|
|
346
346
|
Reported structure: one to three digits, then TWO OR THREE LETTERS THAT
|
|
347
347
|
NAME THE MUNICIPALITY. Six width combinations are reported (1·AB, 12·AB,
|
|
348
348
|
123·AB, 1·ABC, 12·ABC, 123·ABC), which is why this is `recall-only`.
|
|
349
|
-
separator_note: "printed as a raised middle dot; spelled U+0020 here per
|
|
349
|
+
separator_note: "printed as a raised middle dot; spelled U+0020 here per the plates spec §2.6"
|
|
350
350
|
design:
|
|
351
351
|
plate: { w: 12, h: 6, unit: in }
|
|
352
352
|
background: { finish: retroreflective }
|
|
@@ -368,11 +368,11 @@ series:
|
|
|
368
368
|
MUNICIPAL — Connecticut's government class, and the one Connecticut series
|
|
369
369
|
that encodes geography. Modelled `government` rather than `police` even
|
|
370
370
|
though police cars carry it, because the class is defined by OWNERSHIP (the
|
|
371
|
-
town) and not by function;
|
|
371
|
+
town) and not by function; the plates spec's `police` class is for fleets with a
|
|
372
372
|
series distinct from general government, which this is not.
|
|
373
373
|
|
|
374
374
|
# =========================================================================
|
|
375
|
-
# SPECIALTY — PROGRAM INDEX ONLY (
|
|
375
|
+
# SPECIALTY — PROGRAM INDEX ONLY (the plates spec §2.5). No individual designs.
|
|
376
376
|
# =========================================================================
|
|
377
377
|
- id: us-ct-specialty-index
|
|
378
378
|
class: specialty
|
|
@@ -387,7 +387,7 @@ series:
|
|
|
387
387
|
design:
|
|
388
388
|
plate: { w: 12, h: 6, unit: in }
|
|
389
389
|
background: { finish: retroreflective }
|
|
390
|
-
note: "one design per authorised program; individual designs are L4 scope (
|
|
390
|
+
note: "one design per authorised program; individual designs are L4 scope (the plates spec §2.5) and none is described here"
|
|
391
391
|
emblem: { present: true, rendered: placeholder }
|
|
392
392
|
program_index:
|
|
393
393
|
count_statutory: 13
|
|
@@ -406,11 +406,11 @@ series:
|
|
|
406
406
|
phrase-count is thirteen, because § 14-19b's heading spells the program
|
|
407
407
|
differently ("collegiate commemorative number plates") and § 14-21e's does
|
|
408
408
|
not use the word "commemorative" at all. The discrepancy is recorded, not
|
|
409
|
-
resolved by picking a number —
|
|
409
|
+
resolved by picking a number — the plates spec §5.3.
|
|
410
410
|
open_ended_route: "§ 14-19a additionally lets the commissioner issue SPECIAL number plates by REGULATION to members of qualifying organizations and to colleges, and to DISCONTINUE them — an open-ended route whose current membership is not countable from statute. So the true program count is 'thirteen-to-fourteen named in statute, plus an unknown number authorised by regulation'."
|
|
411
411
|
further_statutory_types: "Chapter 246 separately authorises non-commemorative special plates that are NOT part of the specialty program: § 14-20 (antique/rare/special interest, including year-of-manufacture plates), 14-20a (volunteer firefighters), 14-20b/c/d (veterans, war-period service, families of those killed in action), 14-21 (amateur radio), 14-21a (foreign consul), 14-21d (POW and Congressional Medal of Honor), 14-21h (animal population control), 14-27 (public service vehicles), 14-27a (vanpool)."
|
|
412
412
|
official_list_url: "https://portal.ct.gov/dmv"
|
|
413
|
-
official_list_caution: "CT DMV's own specialty-plate page was NOT successfully fetched in this pass (portal.ct.gov returns 404 on every guessed path and the Wayback CDX index for portal.ct.gov/dmv surfaces only image assets). The count above therefore rests on the STATUTE, which
|
|
413
|
+
official_list_caution: "CT DMV's own specialty-plate page was NOT successfully fetched in this pass (portal.ct.gov returns 404 on every guessed path and the Wayback CDX index for portal.ct.gov/dmv surfaces only image assets). The count above therefore rests on the STATUTE, which the plates spec §4 prefers anyway — but the DMV's live catalogue remains unpinned (recorded gap)."
|
|
414
414
|
ip_note: "§ 14-21w(e) — the reproduction-and-marketing authority over a plate image — sits inside this program and is the file's artwork_risk evidence. See artwork_risk above."
|
|
415
415
|
region_encoding: none
|
|
416
416
|
sources:
|
|
@@ -423,5 +423,5 @@ series:
|
|
|
423
423
|
versioned, PD as an edict of government, and it cannot silently drift.
|
|
424
424
|
Second, the count is NOT a clean integer and the file says so — the
|
|
425
425
|
phrase-count (13) and the section-enumeration (14) disagree because two
|
|
426
|
-
sections word their headings differently, and
|
|
426
|
+
sections word their headings differently, and the plates spec §5.3 forbids
|
|
427
427
|
averaging a disagreement away.
|
data/data/plates/us-dc.yml
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# plates/us-dc.yml — District of Columbia (
|
|
1
|
+
# plates/us-dc.yml — District of Columbia (the plates spec gate L2, mid-Atlantic group).
|
|
2
2
|
#
|
|
3
3
|
# THE DISTRICT IS THE ONLY JURISDICTION IN THE UNITED STATES WHOSE STANDARD
|
|
4
4
|
# PLATE LEGEND IS A POLITICAL DEMAND, AND THE DEMAND IS IN THE STATUTE.
|
|
@@ -22,7 +22,7 @@
|
|
|
22
22
|
# licence what you do not own. The Commons tag and the District's own statement
|
|
23
23
|
# cannot both be right, and the District's own statement is the better authority
|
|
24
24
|
# about the District. See `artwork_risk`; this is recorded as a folklore
|
|
25
|
-
# correction, exactly as
|
|
25
|
+
# correction, exactly as the plates spec §4 asks.
|
|
26
26
|
#
|
|
27
27
|
# period_evidence / format_evidence vocabularies as in us-ny.yml.
|
|
28
28
|
jurisdiction: us-dc
|
|
@@ -33,7 +33,7 @@ binding: vehicle
|
|
|
33
33
|
statute_edition: "Code of the District of Columbia, Title 50, Chapter 15, as served by code.dccouncil.gov and read 2026-08-02. DCMR Title 18 § 422 ('Display of Identification Tags', effective 11 August 2017) was identified in the DC Register index but its TEXT was not retrieved — the register serves rule metadata and puts the text behind a per-notice viewer. Recorded gap."
|
|
34
34
|
|
|
35
35
|
# ---------------------------------------------------------------------------
|
|
36
|
-
# artwork_risk — required per jurisdiction by
|
|
36
|
+
# artwork_risk — required per jurisdiction by the plates spec §4.
|
|
37
37
|
# ---------------------------------------------------------------------------
|
|
38
38
|
artwork_risk:
|
|
39
39
|
posture: asserted-but-openly-licensed
|
|
@@ -61,7 +61,7 @@ artwork_risk:
|
|
|
61
61
|
17 U.S.C. § 101 defines a 'work of the United States Government' as one
|
|
62
62
|
prepared by an officer or employee OF THE UNITED STATES GOVERNMENT, and the
|
|
63
63
|
District government is a municipal government created by Congress, not a
|
|
64
|
-
federal agency. RECORDED AS A FOLKLORE CORRECTION per
|
|
64
|
+
federal agency. RECORDED AS A FOLKLORE CORRECTION per the plates spec §4's
|
|
65
65
|
standing treatment of circular and unsupported claims. Anyone relying on
|
|
66
66
|
{{PD-DC}} for a DC plate design should stop.
|
|
67
67
|
practical_effect: >-
|
|
@@ -185,7 +185,7 @@ series:
|
|
|
185
185
|
sources:
|
|
186
186
|
- "https://code.dccouncil.gov/us/dc/council/code/sections/50-1501.02 # § 50-1501.02(f)(3) the Mayor designs the tags; (f-1) the mandated 'End Taxation Without Representation' phrase, its four carve-outs, and the individual opt-out to an alternate design"
|
|
187
187
|
- "https://dmv.dc.gov/service/dmv-vehicle-tags # DC DMV: two tags front and rear — the agency-page-in-force evidence for the display regime"
|
|
188
|
-
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Washington,_D.C. # LOCATOR ONLY (
|
|
188
|
+
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Washington,_D.C. # LOCATOR ONLY (the plates spec §4): August 2017 base, 'WASHINGTON, DC' at top with 'END TAXATION WITHOUT REPRESENTATION' at bottom, AB-1234 from FN-4000, blue on reflective white"
|
|
189
189
|
notes: >-
|
|
190
190
|
END TAXATION WITHOUT REPRESENTATION (2017-) — THE CURRENT DISTRICT
|
|
191
191
|
STANDARD ISSUE, and the only standard-issue plate in the United States
|
|
@@ -526,7 +526,7 @@ series:
|
|
|
526
526
|
agency service pages, and should be the first place a US pass looks.
|
|
527
527
|
|
|
528
528
|
# =========================================================================
|
|
529
|
-
# SPECIALTY — THE PROGRAM INDEX, per
|
|
529
|
+
# SPECIALTY — THE PROGRAM INDEX, per the plates spec §2.5.
|
|
530
530
|
# =========================================================================
|
|
531
531
|
- id: us-dc-specialty-index
|
|
532
532
|
class: specialty
|
|
@@ -541,7 +541,7 @@ series:
|
|
|
541
541
|
charset: { notes: "specialty tags carry ordinary serials on an alternative design. § 50-1501.02(f-1) excludes 'motor vehicles bearing organization plates' from the mandated phrase, so a District specialty tag is legally free of the political legend." }
|
|
542
542
|
design:
|
|
543
543
|
background: { finish: retroreflective }
|
|
544
|
-
note: "one design per approved programme; the designs themselves are L4 scope (
|
|
544
|
+
note: "one design per approved programme; the designs themselves are L4 scope (the plates spec §2.5) and none is described here"
|
|
545
545
|
emblem: { present: true, rendered: placeholder }
|
|
546
546
|
program_index:
|
|
547
547
|
count_official: 13
|
data/data/plates/us-de.yml
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
|
-
# plates/us-de.yml — Delaware (
|
|
1
|
+
# plates/us-de.yml — Delaware (the plates spec gate L2, mid-Atlantic group).
|
|
2
2
|
#
|
|
3
3
|
# DELAWARE IS THE SCHEMA STRESS TEST THE US/WORLD DOSSIER NAMED IN ADVANCE.
|
|
4
4
|
# The dossier flagged it as one of two rows that "break the fixed-width
|
|
5
5
|
# alphanumeric on a 6x12 rectangle assumption", because its serial is a BARE
|
|
6
6
|
# NUMBER of VARIABLE LENGTH with no leading zeros — 4 through 999999, one to six
|
|
7
7
|
# digits, nothing else. Every regex here quantifies rather than fixes width, and
|
|
8
|
-
# the no-leading-zeros rule lives in `regex_strict` exactly as
|
|
8
|
+
# the no-leading-zeros rule lives in `regex_strict` exactly as the plates spec §2.7
|
|
9
9
|
# says a charset restriction must.
|
|
10
10
|
#
|
|
11
11
|
# DELAWARE ALSO HAS THE OLDEST DESIGN STILL IN USE IN THE UNITED STATES. The
|
|
@@ -33,7 +33,7 @@ binding: vehicle
|
|
|
33
33
|
statute_edition: "Delaware Code Title 21 (Motor Vehicles), Chapter 21, Subchapter II (Plates), as served by delcode.delaware.gov and read 2026-08-02."
|
|
34
34
|
|
|
35
35
|
# ---------------------------------------------------------------------------
|
|
36
|
-
# artwork_risk — required per jurisdiction by
|
|
36
|
+
# artwork_risk — required per jurisdiction by the plates spec §4.
|
|
37
37
|
# ---------------------------------------------------------------------------
|
|
38
38
|
artwork_risk:
|
|
39
39
|
posture: unresearched
|
|
@@ -128,7 +128,7 @@ series:
|
|
|
128
128
|
VARIABLE from one digit to six, and the reported rule is that there are
|
|
129
129
|
NO LEADING ZEROS — a one-digit plate is '4', not '000004'. The no-
|
|
130
130
|
leading-zeros rule is what `regex_strict` carries; `regex` cannot,
|
|
131
|
-
because
|
|
131
|
+
because the plates spec §2.7 requires `regex` to round-trip against
|
|
132
132
|
`pattern` and a pattern of six 9s generates leading zeros freely.
|
|
133
133
|
Reported issued range: 4 to 999999, with 1, 2 and 3 reserved for the
|
|
134
134
|
Governor, the Lieutenant Governor and the Secretary of State
|
|
@@ -137,7 +137,7 @@ series:
|
|
|
137
137
|
`pattern` shows the SIX-DIGIT form because that is the modal printed
|
|
138
138
|
plate and a pattern must be a concrete printed shape; the regex is what
|
|
139
139
|
carries the variability. A consumer must read the regex, not the pattern,
|
|
140
|
-
for width. This is the shape
|
|
140
|
+
for width. This is the shape the plates spec §2.2 anticipated when it said
|
|
141
141
|
Delaware's variable-width serials mean 'regexes quantify rather than fix
|
|
142
142
|
width'.
|
|
143
143
|
progression: "strictly sequential ascending; the space has NEVER been reset, which is why Delaware serials are an unusually good age proxy — a low number is an old registration or an expensive one."
|
|
@@ -180,7 +180,7 @@ series:
|
|
|
180
180
|
sources:
|
|
181
181
|
- "https://delcode.delaware.gov/title21/c021/sc02/index.html # 21 Del. C. § 2121: one plate per vehicle, 'the registration number assigned to the vehicle, the name of this State', 'Number plates shall be of such design, size, material and color as the Department may determine', 'Gold letters on a blue background'; § 2125 ownership of plates; § 2126 rear display"
|
|
182
182
|
- "https://www.dmv.de.gov/VehicleServices/tags/index.shtml # DelDOT DMV's own plate index - the agency-page-in-force evidence that this scheme is current"
|
|
183
|
-
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Delaware # LOCATOR ONLY (
|
|
183
|
+
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Delaware # LOCATOR ONLY (the plates spec §4): the 2008 beveled-edge revision, the 4-999999 range, the 1/2/3 reservations for Governor / Lieutenant Governor / Secretary of State, the no-leading-zeros rule and the low-number market"
|
|
184
184
|
notes: >-
|
|
185
185
|
DELAWARE STANDARD ISSUE — VARIABLE-WIDTH NUMERIC, THE SCHEMA'S NAMED
|
|
186
186
|
STRESS TEST. `start: 2008` is locator-grade and marks a MANUFACTURING
|
|
@@ -222,7 +222,7 @@ series:
|
|
|
222
222
|
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Delaware # LOCATOR ONLY: 1969 base, flat, 'Screened gold serial on reflective dark blue plate with gold border', 'THE FIRST STATE' centred at top - identical description to the current base but for the bevel"
|
|
223
223
|
notes: >-
|
|
224
224
|
DELAWARE, FLAT (1969-2008). Recorded as its own series because
|
|
225
|
-
|
|
225
|
+
the plates spec §2.3 makes DESIGN difference a series test and the physical
|
|
226
226
|
construction differs — but recorded with the honest caveat that this is
|
|
227
227
|
the THINNEST series boundary in the mid-Atlantic group. Format, colours,
|
|
228
228
|
legends and serial space are all identical across it. A consumer that
|
|
@@ -265,7 +265,7 @@ series:
|
|
|
265
265
|
serial is all-numeric in a parallel space, the string '12345' is a
|
|
266
266
|
well-formed serial in BOTH the passenger and the motorcycle series and no
|
|
267
267
|
amount of regex resolves it. A parse API must return both candidates for
|
|
268
|
-
Delaware numerics, which is exactly the multi-parse behaviour
|
|
268
|
+
Delaware numerics, which is exactly the multi-parse behaviour the plates spec
|
|
269
269
|
§6's prior-art survey admired in @randock's formatter.
|
|
270
270
|
|
|
271
271
|
- id: us-de-trailer
|
|
@@ -471,7 +471,7 @@ series:
|
|
|
471
471
|
belongs in a later gate.
|
|
472
472
|
|
|
473
473
|
# =========================================================================
|
|
474
|
-
# SPECIALTY — THE PROGRAM INDEX, per
|
|
474
|
+
# SPECIALTY — THE PROGRAM INDEX, per the plates spec §2.5.
|
|
475
475
|
# =========================================================================
|
|
476
476
|
- id: us-de-specialty-index
|
|
477
477
|
class: specialty
|
|
@@ -487,7 +487,7 @@ series:
|
|
|
487
487
|
charset: { notes: "specialty plates carry the ORDINARY Delaware numeric serial on an alternative background - confirmed by reading DelDOT DMV's own specialty thumbnails, which show a six-digit numeric sample. The numeric space and the no-leading-zeros rule are unchanged." }
|
|
488
488
|
design:
|
|
489
489
|
background: { finish: retroreflective }
|
|
490
|
-
note: "one background or organisational design per approved programme; the designs themselves are L4 scope (
|
|
490
|
+
note: "one background or organisational design per approved programme; the designs themselves are L4 scope (the plates spec §2.5) and none is described here"
|
|
491
491
|
emblem: { present: true, rendered: placeholder }
|
|
492
492
|
eligibility_note: "DelDOT DMV: 'Special plates are restricted to passenger vehicles or trucks with a 3/4-ton or less manufacturers gross vehicle weight rating.' A WEIGHT CEILING ON SPECIALTY ELIGIBILITY - the only weight-keyed plate rule in this group, and the reason this series' categories are [car, truck] and not the full list."
|
|
493
493
|
program_index:
|
data/data/plates/us-fl.yml
CHANGED
|
@@ -1,4 +1,4 @@
|
|
|
1
|
-
# plates/us/fl.yml — Florida (
|
|
1
|
+
# plates/us/fl.yml — Florida (the plates spec gate L0 pilot; the federated case).
|
|
2
2
|
#
|
|
3
3
|
# WHY FLORIDA IS THE PILOT STATE, restated from the source law: the US has NO
|
|
4
4
|
# federal plate mandate and per-state IP posture VARIES. Florida is the
|
|
@@ -9,14 +9,14 @@
|
|
|
9
9
|
#
|
|
10
10
|
# SOURCING RULE APPLIED HERE: Florida's plate FACTS come from the STATUTE, not
|
|
11
11
|
# the brochure. Edicts of government are public domain at every level, and
|
|
12
|
-
#
|
|
12
|
+
# the plates spec §4 says always prefer the statute over the brochure. So every
|
|
13
13
|
# format, dimension, legend, display and replacement-cycle claim below cites
|
|
14
14
|
# Chapter 320 or Chapter 316 of the Florida Statutes. The FLHSMV brochure and
|
|
15
15
|
# the specialty portal are cited only for the two things the statute does not
|
|
16
16
|
# carry: which standard VARIANTS are currently offered, and how many specialty
|
|
17
17
|
# programs exist.
|
|
18
18
|
#
|
|
19
|
-
# REGEX FORM (
|
|
19
|
+
# REGEX FORM (the plates spec §2.6, issue #124): every regex in this file is written
|
|
20
20
|
# in PRINTED form — the separator is spelled where the plate shows it. That is
|
|
21
21
|
# why `regex_statutory` reads '\A[A-Z0-9](?: ?[A-Z0-9]){0,6}\z' and not
|
|
22
22
|
# '\A[A-Z0-9]{1,7}\z': the statutory claim is § 320.06(3)(a)'s SEVEN
|
|
@@ -24,7 +24,7 @@
|
|
|
24
24
|
# claimed the plate is printed without a gap, so it rejected "ABC 123" —
|
|
25
25
|
# every real Florida plate. The cap is the claim; the gap is not.
|
|
26
26
|
#
|
|
27
|
-
# WHAT IS DELIBERATELY NOT HERE (
|
|
27
|
+
# WHAT IS DELIBERATELY NOT HERE (the plates spec §2.5): the individual specialty
|
|
28
28
|
# DESIGNS. L2 indexes the programs with official links and counts; individual
|
|
29
29
|
# designs are L4. `us-fl-specialty-index` is that index entry and nothing more.
|
|
30
30
|
#
|
|
@@ -61,7 +61,7 @@ binding: vehicle
|
|
|
61
61
|
statute_edition: "The 2025 Florida Statutes (Title XXIII Motor Vehicles, Chapters 316 and 320) — the current edition read; leg.state.fl.us serves archive editions back to 1997, and the 1997 editions of §§ 320.06 and 320.086 were read for the 2026-08-02 re-dating pass, together with Laws of Florida ch. 99-248 (laws.flrules.org, accessed 2026-08-02)"
|
|
62
62
|
|
|
63
63
|
# ---------------------------------------------------------------------------
|
|
64
|
-
# artwork_risk — required per jurisdiction by
|
|
64
|
+
# artwork_risk — required per jurisdiction by the plates spec §4.
|
|
65
65
|
# ---------------------------------------------------------------------------
|
|
66
66
|
artwork_risk:
|
|
67
67
|
posture: public-domain-favourable
|
|
@@ -73,7 +73,7 @@ artwork_risk:
|
|
|
73
73
|
Wikimedia Commons carries and actively uses the {{PD-FLGov}} tag. Contrast
|
|
74
74
|
Arizona, which expressly asserts copyright, and NY/PA/WA, which are adverse.
|
|
75
75
|
emblem_rule: >-
|
|
76
|
-
|
|
76
|
+
the plates spec §3's placeholder default still applies to the ORANGE BLOSSOM and
|
|
77
77
|
STATE MAP graphic until the emblem is affirmatively cleared per-emblem. Even
|
|
78
78
|
under a favourable copyright posture, state seals and emblems carry
|
|
79
79
|
protection INDEPENDENT of copyright (state-seal misuse statutes), and that
|
|
@@ -233,7 +233,7 @@ series:
|
|
|
233
233
|
- "https://www.flhsmv.gov/pdf/specialtyplates/FLPB.pdf # official FLHSMV 'Florida License Plates' brochure, 27 pp — confirms the four standard variants: Sunshine State, County Name, In God We Trust (State Motto), America 250"
|
|
234
234
|
- "https://www.aamva.org/getmedia/646bcc8a-219b-47d8-b5cd-726240473163/License-Plate-Standard-Edition-3_September-2025-Update.pdf # AAMVA Ed.3 §1.1 replacement-cycle recommendation Florida's 10 years sits at the top of"
|
|
235
235
|
- "https://www.flhsmv.gov/2025/12/15/flhsmv-launches-america-250-license-plate/ # FLHSMV press release, 15 December 2025 (accessed 2026-08-02), verbatim: 'Unlike specialty plates, the America 250 plate serves as an alternative to the standard Florida license plate, with all regular fees applying.' — the agency's own words for the standard-variant relationship, and primary evidence the standard frame recorded here is current issue"
|
|
236
|
-
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Florida # LOCATOR ONLY (
|
|
236
|
+
- "https://en.wikipedia.org/wiki/Vehicle_registration_plates_of_Florida # LOCATOR ONLY (the plates spec §4), re-checked 2026-08-02: the December 2003 introduction of the current base, the February 2026 rollout of its successor, and the seven historical serial arrangements ALL carry no footnote in the article's tables — folklore-grade. The 2003 start below is recorded as this locator's claim, flagged, not asserted as sourced."
|
|
237
237
|
notes: >-
|
|
238
238
|
FLORIDA STANDARD ISSUE ON THE CURRENT BASE. RE-DATED 2026-08-02: the L0
|
|
239
239
|
pass shipped `start: 2025`, the statute-edition year — an instrument date,
|
|
@@ -242,7 +242,7 @@ series:
|
|
|
242
242
|
Sunshine State bottom legends) is reported to have entered issuance in
|
|
243
243
|
DECEMBER 2003 by the Wikipedia table, WHOSE ROW CARRIES NO FOOTNOTE —
|
|
244
244
|
so `period_evidence: secondary-locator-unverified` and 2003 is the
|
|
245
|
-
locator's claim, flagged, not asserted (
|
|
245
|
+
locator's claim, flagged, not asserted (the plates spec §9: primary-source-or-
|
|
246
246
|
marked). What WAS verified, and why nothing better exists to pin: (1)
|
|
247
247
|
FLHSMV has NO plate-history page — the department's full sitemap (3,988
|
|
248
248
|
URLs) was enumerated on 2026-08-02 and nothing on flhsmv.gov dates any
|
|
@@ -257,7 +257,7 @@ series:
|
|
|
257
257
|
new dated series when an agency primary lands. THE ID STAYS UNDATED under
|
|
258
258
|
the id contract: minting `us-fl-standard-2003` on a folklore boundary
|
|
259
259
|
would build a dated id on sand; when a primary lands, the dated id is
|
|
260
|
-
added and this id becomes its former-id alias (
|
|
260
|
+
added and this id becomes its former-id alias (the quality spec I-5/I-6).
|
|
261
261
|
THE IMMEDIATELY-PRIOR BASE (the green-serial county base the locator
|
|
262
262
|
dates to the late 1970s in several sub-forms) is deliberately NOT
|
|
263
263
|
authored: no primary and no CITED secondary dating it was found, and
|
|
@@ -269,7 +269,7 @@ series:
|
|
|
269
269
|
`regex_statutory` and are a recorded gap, per pattern_note.
|
|
270
270
|
|
|
271
271
|
# =========================================================================
|
|
272
|
-
# SPECIALTY — THE PROGRAM INDEX, per
|
|
272
|
+
# SPECIALTY — THE PROGRAM INDEX, per the plates spec §2.5. Count and official
|
|
273
273
|
# links only; no individual designs.
|
|
274
274
|
# =========================================================================
|
|
275
275
|
- id: us-fl-specialty-index
|
|
@@ -288,12 +288,12 @@ series:
|
|
|
288
288
|
design:
|
|
289
289
|
plate: { w: 12, h: 6, unit: in }
|
|
290
290
|
background: { finish: retroreflective }
|
|
291
|
-
note: "one design per authorised program; the designs themselves are L4 scope (
|
|
291
|
+
note: "one design per authorised program; the designs themselves are L4 scope (the plates spec §2.5) and none is described here"
|
|
292
292
|
emblem: { present: true, rendered: placeholder }
|
|
293
293
|
program_index:
|
|
294
294
|
count_official: "over 100"
|
|
295
295
|
count_official_quote: "FLHSMV, in its own words: 'Florida offers over 100 different specialty license plates for various organizations in support of the causes they represent.'"
|
|
296
|
-
count_secondary: "over 120 per Wikipedia — LOCATOR ONLY, not reconciled with FLHSMV's own figure; the discrepancy is recorded, not averaged (
|
|
296
|
+
count_secondary: "over 120 per Wikipedia — LOCATOR ONLY, not reconciled with FLHSMV's own figure; the discrepancy is recorded, not averaged (the plates spec §5.3)"
|
|
297
297
|
official_list_url: "https://www.flhsmv.gov/motor-vehicles-tags-titles/personalized-specialty-license-plates/specialty-license-plates/"
|
|
298
298
|
official_catalogue_url: "https://www.flhsmv.gov/pdf/specialtyplates/FLPB.pdf"
|
|
299
299
|
official_military_catalogue_url: "https://www.flhsmv.gov/pdf/specialtyplates/military_brochure.pdf"
|
|
@@ -326,7 +326,7 @@ series:
|
|
|
326
326
|
- "https://www.leg.state.fl.us/statutes/index.cfm?App_mode=Display_Statute&Search_String=&URL=0300-0399/0320/Sections/0320.08056.html # § 320.08056: specialty plate authorisation, annual use fees, the (8)(a) discontinuation duty with its 3,000/4,000-registration threshold, and the History line whose first entry — 's. 2, ch. 95-282' — dates the framework to 1995 (accessed 2026-08-02)"
|
|
327
327
|
notes: >-
|
|
328
328
|
THE SPECIALTY PROGRAM INDEX — one entry standing for the whole program, which
|
|
329
|
-
is what
|
|
329
|
+
is what the plates spec §2.5 asks for at this gate. RE-DATED 2026-08-02:
|
|
330
330
|
`start: 1995` is the creation year of the § 320.08056 framework — the
|
|
331
331
|
section's History line opens 's. 2, ch. 95-282' (Laws of Florida 1995),
|
|
332
332
|
and a History note is part of the official statute publication, so this
|
|
@@ -370,7 +370,7 @@ series:
|
|
|
370
370
|
THE STATUTORY HYPHEN IS RECORDED, NOT ENCODED. § 320.0805 permits one
|
|
371
371
|
hyphen INSIDE an owner-chosen configuration — which makes it part of
|
|
372
372
|
the plate's identity rather than a group gap, i.e. exactly the
|
|
373
|
-
glyph-inside-a-serial case
|
|
373
|
+
glyph-inside-a-serial case the plates spec §2.6 consequence 3 reserves for
|
|
374
374
|
a schema amendment (_meta/separators.yml never_separator), not a data
|
|
375
375
|
entry. No regex tier here accepts it yet; flagged for the separators
|
|
376
376
|
vocabulary owner. The closest existing precedent is the ES military
|
|
@@ -531,7 +531,7 @@ series:
|
|
|
531
531
|
pre-1997 History entries (78-363, 83-318, 87-197, 96-413 are the
|
|
532
532
|
candidates) because Laws of Florida before 1997 are not served online —
|
|
533
533
|
recorded gap, NOT guessed. The 'Collectible' plate is a genuinely DEAD
|
|
534
|
-
series that is still lawfully on the road — exactly the case
|
|
534
|
+
series that is still lawfully on the road — exactly the case the plates spec's
|
|
535
535
|
`ended: true` + `year_end_min:` semantics exist for; it is still not
|
|
536
536
|
given its own entry because no primary for its own FORMAT (as opposed to
|
|
537
537
|
its existence and closure) was obtained.
|
|
@@ -539,7 +539,7 @@ series:
|
|
|
539
539
|
# =========================================================================
|
|
540
540
|
# STATUTORY LEGEND SERIES. § 320.06(3)(a) mandates a specific bottom legend
|
|
541
541
|
# for five vehicle-tax classes. Each is a design difference on the standard
|
|
542
|
-
# serial, so each is its own series under
|
|
542
|
+
# serial, so each is its own series under the plates spec §2.3.
|
|
543
543
|
# =========================================================================
|
|
544
544
|
- id: us-fl-apportioned
|
|
545
545
|
class: standard
|
|
@@ -704,7 +704,7 @@ series:
|
|
|
704
704
|
statute draws the distinction itself, in adjacent sentences, and because
|
|
705
705
|
only the Dealer legend may be displaced by a specialty design. CLASS
|
|
706
706
|
CAVEAT: recorded as `dealer` — _meta/classes.yml has no `manufacturer`
|
|
707
|
-
value, and the
|
|
707
|
+
value, and the spec's definition of dealer ('trade/garage plates bound to
|
|
708
708
|
a business, not a vehicle') fits the binding but not the trade.
|
|
709
709
|
|
|
710
710
|
- id: us-fl-wrecker
|