Electrical Components & Equipment · data.gov / US GSA

data.gov federal open data catalog

Datadory delivers data gov federal open data catalog data covering 552,271 US government dataset records from federal, state, county and city publishers - each with fourteen-field metadata: title, abstract, publisher, bureau and program codes, contact point, file-level distributions, subject tags, persistent identifiers and both freshness timestamps. Delivered by API, files, or your warehouse; get a sample of this dataset.

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

Where it covers
United States at every level - federal agencies, states, counties and city portals in one index; some records carry global or geospatial extents beyond that
How far back
Continuously growing catalog; each record self-reports a publisher modification date and a verification timestamp, so freshness reads off the row rather than resting on a blanket promise
How fine
One row per dataset record, linked to file-level resources whose media types ride in the row; underlying data granularity varies by publishing agency

What is the data.gov federal open data catalog dataset?

It is the United States government as one addressable table: 552,271 dataset records as of August 2026, drawn from federal agencies, states, counties and city portals, each described in the same DCAT-US metadata vocabulary. A query for electrical equipment returns the spread in one screen - the EPA's Supply Chain Greenhouse Gas Emission Factors v1.3 by NAICS-6, covering 1,016 six-digit commodities with electrical equipment manufacturing among them; NREL's SMART-DS synthetic electrical network models; wind turbine gearbox condition-monitoring benchmarking data; a translated patent titled Electrical Equipment Housing; Los Angeles building-and-safety inspections modified August 17, 2026. Hundreds of records answer that single query, and the catalog answers every other query besides.

That breadth is the point and the trade-off. This is the discovery layer beneath every single-agency collection: where the OpenEI energy data record curates the Department of Energy's shelf, this one reaches every other cabinet department plus state capitols and city halls. It scores 8/10 against a catalog-wide 7.81 average across all 1,744 datasets we hold, and ranks eighth of ten on the best electrical components & equipment datasets list precisely because it tells you what else exists.

Get a sample of this dataset - name the topic, agency or geography, and matching records come back shaped exactly like the dictionary below.

What do sample records look like?

Five records pulled from an electrical-equipment query during our August 2026 research pass, shown as they arrive:

title      : Supply Chain Greenhouse Gas Emission Factors v1.3 by NAICS-6
publisher  : U.S. EPA Office of Research and Development (ORD)
media_type : text/csv                        modified : 2024-07-05
note       : GHG emission factors for 1,016 NAICS-6 commodities,
             electrical equipment manufacturing included (2022 data)

title      : Building and Safety Inspections
publisher  : data.lacity.org
media_type : application/json, text/csv, KML modified : 2026-08-17

title      : SMART-DS Synthetic Electrical Network Data OpenDSS Models
             for SFO, GSO, and AU
publisher  : National Renewable Energy Laboratory (NREL)

title      : Wind Turbine Gearbox Condition Monitoring Vibration Analysis
             Benchmarking Data
publisher  : National Renewable Energy Laboratory

title      : Patent AT-E400988-T1: [Translated] ELECTRICAL EQUIPMENT HOUSING
publisher  : National Center for Biotechnology Information (NCBI)
media_type : text/html                        checked  : 2026-07-31T21:19:39

Read what the variety argues. The first row is supply-chain carbon accounting ready to join onto a vendor master - emission factors keyed by six-digit NAICS, electrical equipment manufacturing explicitly covered, built on 2022 data. The second is municipal enforcement tempo: building-and-safety inspections for a city of four million, in tabular and geospatial formats, its modification stamp only days old at our research pass. The third and fourth are national-laboratory engineering assets - synthetic grid models and rotating-machinery vibration benchmarks - that never surface through commercial channels. The fifth proves the index reaches even intellectual property: a foreign patent, translated, classified under electrical equipment housing.

Every row carries its publisher, its file formats and its two timestamps, so judging whether a record is alive takes reading the row, not asking anyone.

Which fields does the field dictionary define?

Fourteen verified columns, defined in the table below. Three do the structural work. identifier - usually a persistent DOI - is the join key to citation graphs, repositories and any other DOI-keyed set. The paired timestamps, modified and last_harvested_date, put freshness on the row itself: one date belongs to the publishing program, the other to the catalog's verification pass, and disagreement between them is itself a signal about how actively a program maintains its data. And distribution lists file-level resources with explicit media types, so a format-inventory question - CSV here, KML there, nothing but HTML for that one - resolves by reading, not by opening.

Then there is the administrative plumbing few commercial aggregators bother to carry: bureauCode and programCode tying records to budget programs, a structured contactPoint per dataset, and a popularity score that turns the whole corpus into a demand map. Those columns are why analysts treat this record as reference infrastructure rather than another listing.

Where does coverage run, and at what grain?

Three chips summarize the footprint:

  • Geography: the United States at every level - federal agencies, states, counties and cities in one index - with some records carrying global or geospatial extents. One query spans all of it; nobody maintains a wider net.
  • Time frame: continuously growing, and honestly labeled - each record publishes its own modification date and verification stamp, so staleness is visible per row rather than hidden behind a blanket promise. Historical depth varies by publishing program.
  • Granularity: one row per dataset record, linked to file-level resources whose media types ride in the row. Underlying granularity varies by agency - census tables, inspection events, engineering models - which is exactly why the metadata layer earns its keep as the map before the terrain.

How is the data delivered through Datadory?

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

Pick the channel your pipeline already speaks and set the cadence to match the decision being fed. Every delivery ships the field dictionary unchanged, sample rows for validation, and records flattened so publisher, formats and both timestamps sit in one row - a freshness audit becomes a sort, not a survey. Get a sample and the anatomy above comes back populated with the topics you name.

Who uses this data, and for what?

Ranked by how directly one well-formed index settles the day job:

  1. Discovery and make-or-buy decisions. Before commissioning custom collection, teams enumerate what government already publishes on a topic - the catalog answers does this exist in minutes, with named publishers attached.
  2. ESG and supply-chain carbon accounting. NAICS-keyed emission factors join onto vendor masters by industry code, turning scope-3 estimation into a lookup with a documented vintage (market researchers use cases).
  3. Policy, grant and market-entry research. Bureau and program codes plus publisher provenance map who funds what at which level of government - the substrate for positioning any regulated product (competitive intel product teams use cases).
  4. Data-product prototyping. Uniform metadata over half a million records makes this the cheapest place to test a retrieval or classification idea before committing to deeper feeds (developers builders use cases).
  5. Municipal and grid analytics. City inspection records and national-laboratory grid models sit one query apart - unusual adjacency, routinely useful for siting and permitting work (data scientists use cases).

Which personas get the most value?

What should I know before requesting a sample?

Three things, stated up front.

First, this is a catalog of descriptions before it is a pile of data. Each row describes a dataset held by its publishing program; the underlying files vary in depth and age by agency. We cut samples that resolve that distance - named records first, then the referenced content where you want it.

Second, relevance is a vocabulary conversation. Half a million records reward a precise brief: the topics, agencies and geographies you care about decide whether a cut returns fifty rows or five thousand.

Third, the electrical slice is discovered, not pre-assembled. Nothing here arrives pre-filtered, which is the same property that makes it the widest net in the industry pool - and the reason it pairs so well with a curated set.

Which pages pair with this dataset?

Notes worth reading next:

Field dictionary

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

Field dictionary - data.gov federal open data catalog, one row per dataset record (definitions verified against live records, August 2026)
fieldtypedefinitionexample
titlestringDataset title as published by the source agency - the primary human-readable key for triage.Supply Chain Greenhouse Gas Emission Factors v1.3 by NAICS-6
descriptiontextDataset abstract as written by the publishing program, usually stating method, vintage and intended use.
publisherstringPublishing organization name plus a government-level marker separating Federal, State, County and City provenance.U.S. EPA Office of Research and Development (ORD)
accessLevelenumDCAT-US access classification declared by the publishing agency.public
bureauCode / programCodestringFederal bureau and program classification codes tying a record to budget-line programs rather than topical keywords.["020:00"] / ["020:000"]
contactPointstringNamed contact and mailbox for dataset questions, carried as a structured card on each record.
distributionstringFile-level resource entries, each with a title and a media type, so format inventory reads without opening anything.text/csv; application/json; KML
licensestringUsage declaration stated by the publishing agency where one applies; normalized during delivery so usage rights resolve from your Datadory agreement.
keyword / themestringSubject tags driving faceting and topical recall across the catalog.GHG reporting; USEEIO; scope 3
identifierstringPersistent identifier for the record, frequently a Digital Object Identifier - the cleanest join key to citation graphs and repository holdings.DOI
modified / Dataset Last UpdateddateThe publisher's own last-modification date for the dataset contents.2024-07-05
last_harvested_date / Catalog Last CheckeddatetimeWhen the catalog last ingested or verified the record - the second of the two timestamps that make freshness readable per row.2026-07-31T21:19:39
has_downloadbooleanFlag marking records that carry at least one file-level resource.true
popularitynumberUsage-weighted score behind popularity ordering - a demand signal across the whole federal corpus.

Questions buyers ask

What does one record of data gov federal open data catalog data contain?

Fourteen documented metadata fields: dataset title, abstract, publishing organization with its government-level marker, access classification, bureau and program codes, a named contact point, file-level distribution entries with media types, the publisher's usage declaration where stated, subject tags, a persistent identifier usually a DOI, the publisher's modification date, the catalog's verification timestamp, a downloadable-resource flag and a popularity score.

How much ground does the catalog cover?

552,271 dataset records as of August 2026, contributed by federal agencies, states, counties and city portals. Topical queries for electrical equipment return hundreds of relevant records spanning emissions factors, patents, grid models and municipal inspections.

How is this different from a single-agency dataset collection?

Scope. A curated collection assembles one publisher's best shelf; this index reaches every cabinet department plus state, county and city publishers - two orders of magnitude more records, at the cost of arriving unfiltered. The two approaches complement each other, which is why both sit in the same industry pool.

Can the electrical-relevant slice be isolated?

Yes. Records carry subject tags, publishing-organization markers separating Federal from State, County and City provenance, geographic descriptors and multiple sort keys, so a brief like electrical equipment manufacturing narrows cleanly. Name the topics, agencies and geographies and the sample comes back pre-cut.

How fresh is each record?

Each row carries two dates: the publishing program's own modification date and the catalog's verification timestamp. Reading the pair together shows which records describe living datasets and which describe older one-off publications - no blanket promise required.

What can I combine this dataset with?

Natural pairs sit on the same industry shelf: OpenEI energy data for the curated Department of Energy layer, BEA GDP-by-industry iTable for macro context, SAM.gov contract awards for federal procurement, and the EU Open Data Portal as the European counterpart index. Persistent identifiers keep the joins mechanical.

How well documented is the schema?

Fourteen fields with written definitions, verified against live catalog records during our August 2026 research pass rather than reconstructed from documentation. Identity, provenance, distribution and timestamp columns are fully specified; variability sits in the underlying datasets, not in the metadata dictionary.

Datasets that pair with this one

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