FPDS Query Library
About Us
Contact Us

City

Human-readable city name associated with the vendor ZIP code in the vendor location record. It identifies the locality component of the mailing address, such as a municipal name or place name stored with the ZIP code.

Family: Other Transaction 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__OtherTransactionIDV__contractDetail__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city
Title
City
FPDS Path
OtherTransactionIDV/contractDetail/vendor/vendorSiteDetails/vendorLocation/ZIPCode/city
Description
Human-readable city name associated with the vendor ZIP code in the vendor location record. It identifies the locality component of the mailing address, such as a municipal name or place name stored with the ZIP code.
Business Meaning
This field helps analysts locate vendor geography, assess award distribution by place, and support address standardization, geocoding, and market concentration analysis. It can also be used to compare vendor locations against place-based policy, socioeconomic, or regional procurement patterns.
Example Value
CLEVELAND
Observed Non-Null Count
13,417

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__vendor__vendorSiteDetails__vendorLocation__ZIPCode__city
FPDS XML Path
OtherTransactionIDV/contractDetail/vendor/vendorSiteDetails/vendorLocation/ZIPCode/city
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/contractDetail/vendor/vendorSiteDetails/vendorLocation/ZIPCode/city' into the SQL-ready variable 'content__OtherTransactionIDV__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

  • vendor location analysis
  • geographic distribution of awards
  • address normalization and matching

Common Mistakes

  • using city as a unique key for vendors
  • assuming the value is always USPS-standard or consistently formatted

Query Guidance

Use it in SELECT, GROUP BY, and filtering when analyzing vendor geography, but pair it with ZIP code and state to reduce ambiguity. For reliable joins or deduplication, prefer standardized location keys or combined address fields rather than city alone.

SQL Examples

Preview values

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

Top values

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