FPDS Query Library
About Us
Contact Us

Street Address2

Second address line for the vendor location in the IDV vendor site record. It typically captures supplemental location detail such as suite, floor, building, or mail stop when the primary street address is not sufficient.

Family: 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__IDV__vendor__vendorSiteDetails__vendorLocation__streetAddress2
Title
Street Address2
FPDS Path
IDV/vendor/vendorSiteDetails/vendorLocation/streetAddress2
Description
Second address line for the vendor location in the IDV vendor site record. It typically captures supplemental location detail such as suite, floor, building, or mail stop when the primary street address is not sufficient.
Business Meaning
This field improves location specificity in vendor identification and address-based analysis, especially when multiple vendor records share the same primary address. It can support deduplication, vendor matching, geographic normalization, and audits of vendor site detail quality.
Example Value
SUITE 920
Observed Non-Null Count
173,050

FPDS Compare

FPDS Query Variable
content__IDV__vendor__vendorSiteDetails__vendorLocation__streetAddress2
FPDS XML Path
IDV/vendor/vendorSiteDetails/vendorLocation/streetAddress2
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'IDV/vendor/vendorSiteDetails/vendorLocation/streetAddress2' into the SQL-ready variable 'content__IDV__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 vendor matching
  • Vendor location quality checks
  • Supplemental filtering within a known site address

Common Mistakes

  • Using it as a standalone location key
  • Assuming consistent formatting or standardized abbreviations

Query Guidance

Filter with exact or pattern matching only when needed for address cleanup or deduplication, and combine with other location fields for joins and grouping. In SQL, use NULL/empty checks carefully because many records may not populate this line; avoid using it as a primary grouping dimension unless you are explicitly analyzing site-level address detail.

SQL Examples

Preview values

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

Top values

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