FPDS Query Library
About Us
Contact Us

Street Address2

Second line of the vendor location street address recorded for an Other Transaction Award. It stores supplemental address text such as a suite, floor, or building identifier and is part of the vendor site detail location record.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__vendor__vendorSiteDetails__vendorLocation__streetAddress2
Title
Street Address2
FPDS Path
OtherTransactionAward/contractDetail/vendor/vendorSiteDetails/vendorLocation/streetAddress2
Description
Second line of the vendor location street address recorded for an Other Transaction Award. It stores supplemental address text such as a suite, floor, or building identifier and is part of the vendor site detail location record.
Business Meaning
This field helps analysts standardize and distinguish vendor locations when multiple vendors share the same base address or when mail-stop details are needed for entity resolution, geocoding, and contract footprint analysis. It also improves address quality checks and supports more accurate grouping of awards by physical site.
Example Value
SUITE 750
Observed Non-Null Count
1,361

FPDS Compare

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

Use Cases

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

Common Usage

  • Address normalization and cleansing
  • Vendor site deduplication and entity matching
  • Geocoding and location-based analysis

Common Mistakes

  • Using it as a primary location field instead of a supplemental address line
  • Assuming consistent abbreviations or complete address coverage

Query Guidance

Select and concatenate this field only as an address extension; do not use it alone for filtering or joins. In SQL, combine it with streetAddress1 and other location fields, and apply NULL/blank handling when building standardized addresses or grouping vendor sites.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__contractDetail__vendor__vendorSiteDetails__vendorLocation__streetAddress2 AS street_address2
FROM fpds.data
WHERE content__OtherTransactionAward__contractDetail__vendor__vendorSiteDetails__vendorLocation__streetAddress2 IS NOT NULL
LIMIT 25

Top values

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