FPDS Query Library
About Us
Contact Us

Congressional District Code

Code for the congressional district associated with the vendor’s location in the IDV record. It is a geographic identifier, typically stored as a short code such as "08," rather than a full district name or description.

Family: IDV
Category: Vendor Site Details
Data Type: identifier_or_code
Semantic Type: identifier
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__IDV__vendor__vendorSiteDetails__vendorLocation__congressionalDistrictCode
Title
Congressional District Code
FPDS Path
IDV/vendor/vendorSiteDetails/vendorLocation/congressionalDistrictCode
Description
Code for the congressional district associated with the vendor’s location in the IDV record. It is a geographic identifier, typically stored as a short code such as "08," rather than a full district name or description.
Business Meaning
This field lets analysts connect vendors to U.S. congressional districts for geographic distribution, local economic impact, and legislative oversight analyses. It supports reporting on where federal suppliers are located and how contracting activity is distributed across districts.
Example Value
08
Observed Non-Null Count
5,145,507

FPDS Compare

FPDS Query Variable
content__IDV__vendor__vendorSiteDetails__vendorLocation__congressionalDistrictCode
FPDS XML Path
IDV/vendor/vendorSiteDetails/vendorLocation/congressionalDistrictCode
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/vendor/vendorSiteDetails/vendorLocation/congressionalDistrictCode' into the SQL-ready variable 'content__IDV__vendor__vendorSiteDetails__vendorLocation__congressionalDistrictCode'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building
  • Contractor profiling and competitor analysis

Common Usage

  • Map vendor locations to congressional districts
  • Summarize awards or IDVs by district
  • Join to geographic reference tables for reporting

Common Mistakes

  • Assuming the code is a human-readable district name
  • Grouping without normalizing formatting differences or handling missing values

Query Guidance

Filter and group on the raw code only after standardizing format and checking source conventions. Use a reference table or CASE logic if you need a display label, and join on the code when building district-level summaries.

SQL Examples

Preview values

SELECT
    content__IDV__vendor__vendorSiteDetails__vendorLocation__congressionalDistrictCode AS congressional_district_code
FROM fpds.data
WHERE content__IDV__vendor__vendorSiteDetails__vendorLocation__congressionalDistrictCode IS NOT NULL
LIMIT 25

Top values

SELECT
    content__IDV__vendor__vendorSiteDetails__vendorLocation__congressionalDistrictCode AS value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__vendor__vendorSiteDetails__vendorLocation__congressionalDistrictCode IS NOT NULL
GROUP BY value
ORDER BY record_count DESC
LIMIT 25

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.