FPDS Query Library
About Us
Contact Us

City

Human-readable city name associated with the vendor location ZIP code in the award record. It serves as the locality label for the vendor site and is not a geographic coordinate or census-standard place key.

Family: Other Transaction Award
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__OtherTransactionAward__contractDetail__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city
Title
City
FPDS Path
OtherTransactionAward/contractDetail/vendor/vendorSiteDetails/vendorLocation/ZIPCode/city
Description
Human-readable city name associated with the vendor location ZIP code in the award record. It serves as the locality label for the vendor site and is not a geographic coordinate or census-standard place key.
Business Meaning
Supports geographic profiling of vendors, such as identifying local versus out-of-area suppliers, mapping vendor concentration, and reviewing place-based award patterns. It is useful when analyzing vendor footprint, regional spend, and location consistency across awards.
Example Value
MIDDLETOWN
Observed Non-Null Count
38,894

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city
FPDS XML Path
OtherTransactionAward/contractDetail/vendor/vendorSiteDetails/vendorLocation/ZIPCode/city
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/vendor/vendorSiteDetails/vendorLocation/ZIPCode/city' into the SQL-ready variable 'content__OtherTransactionAward__contractDetail__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 aggregation of vendor locations by city
  • Filtering awards by vendor locality
  • Cross-checking city, state, and ZIP consistency

Common Mistakes

  • Using it as a unique location identifier
  • Assuming it is always the city where the vendor is headquartered

Query Guidance

Use equality, LIKE, and GROUP BY operations for location analysis, but pair with ZIP code and state fields to validate geographic matches. When deduplicating, apply UPPER(TRIM(city)) or a similar normalization step to handle formatting variation.

SQL Examples

Preview values

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

Top values

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