FPDS Query Library
About Us
Contact Us

Street Address2

Second address line for the primary consortia location recorded on an Other Transaction IDV. It captures supplemental street-level address detail such as suite, building, or mail-stop information when present.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__consortiaInformation__primaryConsortiaLocation__streetAddress2
Title
Street Address2
FPDS Path
OtherTransactionIDV/contractDetail/consortiaInformation/primaryConsortiaLocation/streetAddress2
Description
Second address line for the primary consortia location recorded on an Other Transaction IDV. It captures supplemental street-level address detail such as suite, building, or mail-stop information when present.
Business Meaning
This field helps analysts resolve and standardize organization location information for consortium-related award records. It can improve entity matching, geographic analysis, deduplication, and interpretation of address completeness across procurement data.
Example Value
STE 200
Observed Non-Null Count
1

FPDS Compare

FPDS Query Variable
content__OtherTransactionIDV__contractDetail__consortiaInformation__primaryConsortiaLocation__streetAddress2
FPDS XML Path
OtherTransactionIDV/contractDetail/consortiaInformation/primaryConsortiaLocation/streetAddress2
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionIDV/contractDetail/consortiaInformation/primaryConsortiaLocation/streetAddress2' into the SQL-ready variable 'content__OtherTransactionIDV__contractDetail__consortiaInformation__primaryConsortiaLocation__streetAddress2'.

Use Cases

  • Dictionary lookup and field explanation
  • SQL filtering and grouping
  • Analytical reporting and reusable query building

Common Usage

  • Address normalization and record linkage
  • Location completeness checks
  • Manual review of consortium office addresses

Common Mistakes

  • Treating it as a coded field or using it for geographic aggregation by itself
  • Assuming blanks mean no location exists rather than missing second-line detail

Query Guidance

Use it as a text field for filtering or display, not as a join key. In SQL, pair it with the rest of the location hierarchy and use IS NOT NULL, LIKE, or CONCAT logic only when you need address matching or formatting.

SQL Examples

Preview values

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

Top values

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