FPDS Query Library
About Us
Contact Us

City

Human-readable city name associated with the vendor location ZIP code in the IDV vendor site details. It is a geographic label rather than a code, and it identifies the city portion of the location reference for the vendor address.

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__ZIPCode__city
Title
City
FPDS Path
IDV/vendor/vendorSiteDetails/vendorLocation/ZIPCode/city
Description
Human-readable city name associated with the vendor location ZIP code in the IDV vendor site details. It is a geographic label rather than a code, and it identifies the city portion of the location reference for the vendor address.
Business Meaning
This field supports geographic analysis of vendor presence, such as identifying where contractors are located, clustering awards by place, and validating location patterns against state or ZIP data. It is useful for market research, regional spend analysis, and detecting address anomalies or duplicates across vendor records.
Example Value
AMARILLO
Observed Non-Null Count
5,420,906

FPDS Compare

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

Use Cases

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

Common Usage

  • Geographic rollups of vendor locations
  • Filtering awards or vendors by city
  • Cross-checking city against ZIP/state combinations

Common Mistakes

  • Treating the city as a unique identifier instead of a descriptive location label
  • Assuming the value is standardized without verifying spelling or ZIP consistency

Query Guidance

Filter and group on the city text only after normalizing case and whitespace; for reliable location analysis, join or compare it with ZIP code and state. In SQL, use exact matching for known cities and consider UPPER(TRIM(city)) for normalization, but avoid relying on city alone as a geographic key.

SQL Examples

Preview values

SELECT
    content__IDV__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city AS city
FROM fpds.data
WHERE content__IDV__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city IS NOT NULL
LIMIT 25

Top values

SELECT
    content__IDV__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city AS value,
    count() AS record_count
FROM fpds.data
WHERE content__IDV__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city 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.