FPDS Query Library
About Us
Contact Us

Street Address2

Second address line for the primary consortia location associated with an Other Transaction Award. It captures supplemental street-location detail such as suite, floor, or unit information when a single address line is not sufficient.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__contractDetail__consortiaInformation__primaryConsortiaLocation__streetAddress2
Title
Street Address2
FPDS Path
OtherTransactionAward/contractDetail/consortiaInformation/primaryConsortiaLocation/streetAddress2
Description
Second address line for the primary consortia location associated with an Other Transaction Award. It captures supplemental street-location detail such as suite, floor, or unit information when a single address line is not sufficient.
Business Meaning
This field helps analysts identify and standardize the physical location details of the consortia involved in an award, especially when matching award records to organizations, geocoding locations, or assessing geographic concentration and administrative footprint. It can improve location-level analysis when combined with the primary street address, city, state, and ZIP fields.
Example Value
STE 102
Observed Non-Null Count
21

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__contractDetail__consortiaInformation__primaryConsortiaLocation__streetAddress2
FPDS XML Path
OtherTransactionAward/contractDetail/consortiaInformation/primaryConsortiaLocation/streetAddress2
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/contractDetail/consortiaInformation/primaryConsortiaLocation/streetAddress2' into the SQL-ready variable 'content__OtherTransactionAward__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 entity matching
  • Geocoding and location enrichment
  • Filtering or grouping awards by consortia location detail

Common Mistakes

  • Using this field alone as a complete address
  • Assuming blank values mean no physical location exists

Query Guidance

Use it with the rest of the primary consortia location fields in WHERE, GROUP BY, or concatenation logic; for example, concatenate streetAddress1, streetAddress2, city, state, and postal code for standardized address output. Do not filter on this field unless looking for specific suite/unit patterns, and expect free-text variation that may require TRIM, UPPER, or pattern matching.

SQL Examples

Preview values

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

Top values

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