FPDS Query Library
About Us
Contact Us

Street Address

Street address of the vendor location recorded in the Vendor Site Details portion of an Other Transaction IDV record. It captures the physical mailing or location address line, typically as free-text content rather than a coded value.

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__streetAddress
Title
Street Address
FPDS Path
OtherTransactionIDV/contractDetail/vendor/vendorSiteDetails/vendorLocation/streetAddress
Description
Street address of the vendor location recorded in the Vendor Site Details portion of an Other Transaction IDV record. It captures the physical mailing or location address line, typically as free-text content rather than a coded value.
Business Meaning
This field helps analysts identify where a vendor site is located, support geographic and address-level rollups, and distinguish among multiple locations tied to the same vendor. It is useful for market concentration analysis, locality-based reporting, and linking FPDS records to external geography, ownership, or entity-resolution datasets.
Example Value
120 COMMISSIONER DR
Observed Non-Null Count
13,417

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__vendor__vendorSiteDetails__vendorLocation__streetAddress
FPDS XML Path
OtherTransactionIDV/contractDetail/vendor/vendorSiteDetails/vendorLocation/streetAddress
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/contractDetail/vendor/vendorSiteDetails/vendorLocation/streetAddress' into the SQL-ready variable 'content__OtherTransactionIDV__contractDetail__vendor__vendorSiteDetails__vendorLocation__streetAddress'.

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 matching and entity resolution
  • geographic analysis at the address or site level
  • supporting vendor profile reviews and duplicate detection

Common Mistakes

  • assuming it is a standardized geocoded address
  • using it alone as a unique vendor identifier

Query Guidance

Filter or aggregate on this field only after normalizing text and pairing it with city, state, ZIP, and vendor identifiers. In SQL, trim whitespace, standardize case, and use it as a descriptive grouping attribute rather than a join key unless you have a controlled address-matching process.

SQL Examples

Preview values

SELECT
    content__OtherTransactionIDV__contractDetail__vendor__vendorSiteDetails__vendorLocation__streetAddress AS street_address
FROM fpds.data
WHERE content__OtherTransactionIDV__contractDetail__vendor__vendorSiteDetails__vendorLocation__streetAddress IS NOT NULL
LIMIT 25

Top values

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