data.gov Federated Catalog - Automotive Retail Datasets

Datadory delivers data gov federated catalog automotive retail datasets data: dealer licensing rosters, monthly vehicle sales counts, county-level EV registrations, fuel gallons sold and recall records, drawn from one U.S. catalog indexing 552,271 datasets across federal, state, county, city and tribal publishers. Delivered daily, weekly, or hourly.

What is the data.gov Federated Catalog - Automotive Retail Datasets?

The U.S. government keeps one master index of its data, and it is enormous: 552,271 dataset records harvested from federal agencies and from state, county, city, tribal and university portals, run as a GSA Technology Transformation Services property. Queried for automotive retail, that haystack compresses into something usable - roughly 1 to 20 records per query term - and the records are concrete. Maryland's motor vehicle administration publishes monthly new and used vehicle sales counts and sales dollars from 2002 through April 2026. The same state tracks electric and plug-in hybrid registrations by county and zip code. New York contributes vehicle, snowmobile and boat registrations plus DMV facility listings; Connecticut contributes licensed automobile dealers, repairers, leasing companies and manufacturers, and motor vehicle fuel gallons sold. Federal safety regulators round out the slice with defect-recall records and the transaction files from the Car Allowance Rebate System - the cash-for-clunkers program.

One caveat shapes everything else: the catalog indexes descriptions of datasets, not the datasets themselves. Each record points at a publisher. Get a sample of this dataset and Datadory hands you the resolved automotive-retail slice - records with their fields populated - instead of a list of places to look.

What does a sample of the automotive-retail slice look like?

Five records pulled from the slice at verification, shown exactly as the catalog describes them:

title     : MVA Vehicle Sales Counts by Month for Calendar Year 2002 through April 2026
publisher : opendata.maryland.gov
issued    : 2018-07-27
modified  : 2026-07-06
-
title     : Licensed Automobile Dealers, Repairers, Leasing Companies and Manufacturers
publisher : data.ct.gov
-
title     : NHTSA's Office of Defects Investigation (ODI) - Recalls
publisher : National Highway Traffic Safety Administration
-
title     : Car Allowance Rebate System (CARS) - Transactions
publisher : National Highway Traffic Safety Administration
-
title     : Motor Vehicle Fuels Gallons Sold
publisher : data.ct.gov

Read the first row closely - it is the whole proposition in miniature. A state motor vehicle administration has published a month-by-month count of vehicles sold, new and used, with sales dollars, continuously for over two decades, and the catalog noticed it was modified in July 2026. Most analytics teams hunting for dealer-level sales context never learn this series exists. The other four rows cover franchised-dealer licensing, recall history, scrappage-program transactions and taxable fuel volume - four different publishers, one query away from each other.

What fields does every catalog record carry?

Every harvested record arrives in the same six-attribute envelope regardless of which agency published the underlying dataset, so one parser handles the lot. The relevance score is the only computed field - everything else is publisher-supplied descriptive metadata.

How wide is the coverage across geography, time and granularity?

  • Geography - the United States, at unusual depth: federal agencies sit alongside state portals (Maryland, Connecticut and New York appear in this slice), plus county, city, tribal and university publishers. Dealer licensing is inherently local, which is why sub-state coverage matters here.
  • Temporal - governed entirely by the underlying datasets. Verified records ranged from a 2018 issuance date to a July 2026 modification, and the Maryland sales-count series itself spans January 2002 through April 2026 - a 24-year monthly panel.
  • Granularity - one record per dataset. The catalog describes tables and files; the granularity inside them varies from monthly state aggregates to transaction-level recall and rebate records.

How is the data delivered?

API, files, or your warehouse. Daily, weekly, or hourly.

Who uses this data, and for what?

  • Dealer network and territory mapping - licensing rosters from Connecticut and New York enumerate who may legally sell, repair and lease, giving franchise-development teams a ground-truth map of incumbent dealers by state.
  • EV adoption tracking - Maryland's electric and plug-in hybrid registration counts by county and zip code turn fleet-transition talk into measured penetration, zip by zip, useful for siting service capacity.
  • Recall exposure screening - the federal defect-recall records let aftermarket and insurance analysts quantify how many vehicles on the road carry open safety campaigns.
  • Fuel-demand baselining - Connecticut's monthly gallons-sold series provides a taxable-fuel baseline against which dealer-group fuel margins can be sanity-checked.
  • Sales-trend triangulation - the Maryland monthly counts (2002-2026) give a long-run, state-level read on new-versus-used mix that complements national retail surveys.

Which personas get the most value?

Data Scientists & ML Engineers get a stable six-field metadata envelope plus genuinely odd, useful targets - 24 years of monthly sales counts, zip-code EV registrations - that make strong exogenous features. Competitive Intelligence & Product Teams get licensing and facility rosters that reveal where rivals' dealers actually operate. Developers & Data-Product Builders get uniform records across hundreds of publishers, which is rare enough to build on. Market Researchers & Consultants get quotable public-sector numbers - recall volumes, scrappage transactions, fuel gallons - that survive client scrutiny.

What should I know before requesting a sample?

Three things, stated plainly. First, this is a discovery layer: the catalog holds descriptions and identifiers, and each underlying dataset lives with its publisher, so a sample from Datadory means resolved records rather than a pointer list. Second, result sets per query term are small - roughly 1 to 20 records - and the catalog did not expose a total-match count at verification, so the true size of the automotive-retail slice is unknowable from the outside; breadth comes from varying the terms, not paging deep. Third, Datadory rates this source 6 out of 10 on its own rubric - field documentation is excellent and freshness is proven, but the thin per-topic depth caps the score. Pair it with the Census monthly motor-vehicle-and-parts survey (rated 10) when a single authoritative series matters more than breadth.

What else sits in Datadory's automotive-retail catalog?

Of the 1,744 datasets Datadory catalogs across 159 viable industries, twelve cover automotive retail, and this catalog is the broadest-discovery entry among them. The specialist companions:

  • U.S. Census Monthly Retail Trade Survey - monthly sales, inventories and inventory-to-sales ratios for motor vehicle and parts dealers; the strongest single series in the industry at rating 10.
  • U.S. Census County Business Patterns - annual establishment and employment counts for automobile dealer businesses, down to the county.
  • NADA Dealership Financial Profiles - annual and mid-year financial benchmarks for U.S. franchised new-car dealers.
  • SMMT UK Vehicle Data Hub - monthly British new car, LCV, EV and bus registrations plus the annual motor-industry fact book.
  • UK Department for Transport VEH01-VEH03 - DVLA-backed statistics on licensed vehicle stock and first registrations.
  • ONS Retail Sales Index - Great Britain's monthly value and volume indices including automotive fuel.

Browse the automotive retail data hub for the full twelve, or see the data scientists use cases, competitive intel product teams use cases and developers builders use cases pages.

Field dictionary

Every field below is documented against real records. The full dictionary ships with the sample.

Field dictionary - the metadata envelope on every harvested record
fieldtypedefinitionexample
_scorenumberRelevance score the catalog assigns to each matched record.60.909252
dcat.titlestringDataset title exactly as supplied by the publishing agency or portal.MVA Vehicle Sales Counts by Month for Calendar Year 2002 through April 2026
dcat.descriptiontextAbstract of the dataset written by the publisher.The number of new and used vehicles and the sales dollars respectively sold by month.
dcat.publisher.namestringPublishing organization - a state portal, a federal agency or another public-body publisher.opendata.maryland.gov
dcat.identifierstringPublisher-side unique identifier for the described dataset, usually resolving to a view ID on the publishing portal.un65-7ipd
dcat.modified / dcat.issueddateLast-modified and first-published dates recorded in the harvested metadata.2026-07-06

Questions buyers ask

How many datasets does the catalog index?

552,271 dataset metadata records at verification, harvested from federal agencies plus state, county, city, tribal and university publishers. Automotive-retail query terms cut through to small, workable result sets - roughly 1 to 20 records per term rather than another 500k-row haystack.

Which motor-trade records sit inside the automotive-retail slice?

Maryland MVA's monthly new and used vehicle sales counts running 2002 through April 2026, electric and plug-in hybrid registrations by Maryland county and zip code, New York vehicle and snowmobile registrations plus DMV facility listings, Connecticut dealer licensing and motor vehicle fuel gallons sold, and federal recall and clunker-trade-in transaction files.

Does the catalog hold the underlying data itself?

No. It is a metadata index operated as a GSA Technology Transformation Services property - every record describes a dataset that lives with its publishing agency or state portal, and carries that publisher's identifier so the description and the actual tables never get confused.

How current are the records?

Each record carries its own issued and modified dates, and they vary by publisher. Examples verified during research ranged from a 2018 issuance date to a July 2026 modification - the Maryland sales-count series was touched within weeks of verification.

Is the record schema stable across publishers?

Yes. Whether a record was harvested from a federal agency or a city portal, it arrives in the same envelope: title, description, publisher, identifier, issued and modified dates. Pipelines written against one publisher's records parse every other publisher's records unchanged.

See the rows before you pay anything.

Name this dataset and we send real records from it — scoped to the fields you asked for.

See pricing