FPDS Query Library
About Us
Contact Us

City

City name for the vendor's location recorded in the Vendor Site Details section of the FPDS Other Transaction IDV record. It identifies the municipality associated with the vendor site rather than the contracting office or place of performance.

Family: Other Transaction IDV
Category: Vendor Site Details
Data Type: string
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__vendor__vendorSiteDetails__vendorLocation__city
Title
City
FPDS Path
OtherTransactionIDV/contractDetail/vendor/vendorSiteDetails/vendorLocation/city
Description
City name for the vendor's location recorded in the Vendor Site Details section of the FPDS Other Transaction IDV record. It identifies the municipality associated with the vendor site rather than the contracting office or place of performance.
Business Meaning
This field supports geographic analysis of vendor distribution, market concentration, and regional sourcing patterns. Analysts use it to group awards by vendor location, assess local versus nonlocal participation, and standardize location-based reporting across procurement datasets.
Example Value
HUNTSVILLE
Observed Non-Null Count
13,417

FPDS Compare

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

  • Grouping vendor locations by city
  • Mapping vendor geographic concentration
  • Joining to city/state normalization or geocoding tables

Common Mistakes

  • Confusing vendor city with place of performance or agency office location
  • Assuming all city values are standardized or complete

Query Guidance

Select and group on this field only after trimming and normalizing case; for analysis, combine it with state or country to avoid ambiguous city names. Example: GROUP BY city, state, country, and use COALESCE or reference data to handle blanks and variant spellings.

SQL Examples

Preview values

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

Top values

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