FPDS Query Library
About Us
Contact Us

Generic Boolean02

Numeric indicator for Generic Boolean02 within the Other Transaction Award generic tags. It represents a boolean-style flag stored as a numeric value, typically using 0/1 semantics rather than free text.

Family: Other Transaction Award
Category: Generic Tags
Data Type: numeric
Semantic Type: attribute
Mapping: flattened_fpds_xml_field
AI Confidence: high

Variable Overview

FPDS Query Variable
content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02
Title
Generic Boolean02
FPDS Path
OtherTransactionAward/genericTags/genericBooleans/genericBoolean02
Description
Numeric indicator for Generic Boolean02 within the Other Transaction Award generic tags. It represents a boolean-style flag stored as a numeric value, typically using 0/1 semantics rather than free text.
Business Meaning
This field can support reusable filtering and segmentation across Other Transaction Award records when the boolean is used to mark a specific program condition, status, or classification. It matters because generic flags often drive cross-record analyses where standard FPDS line-item fields are not sufficient.
Example Value
0
Observed Non-Null Count
12,012

FPDS Compare

FPDS Query Variable
content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02
FPDS XML Path
OtherTransactionAward/genericTags/genericBooleans/genericBoolean02
Mapping Type
flattened_fpds_xml_field
Comparison Summary
FPDS Query flattens the original nested FPDS XML path 'OtherTransactionAward/genericTags/genericBooleans/genericBoolean02' into the SQL-ready variable 'content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02'.

Use Cases

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

Common Usage

  • Filtering awards by a specific yes/no attribute
  • Grouping records for comparative analysis
  • Joining to other generic tag indicators for composite logic

Common Mistakes

  • Interpreting the field as a quantitative amount
  • Assuming 0 and null have the same meaning

Query Guidance

Use equality filters such as `= 1` or `= 0` after confirming the encoding in the dataset. In SQL, handle nulls explicitly with `IS NULL` or `COALESCE` when separating unknown from false, and cast only if the source system stores the flag as text in some extracts.

SQL Examples

Preview values

SELECT
    content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02 AS generic_boolean02
FROM fpds.data
WHERE content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02 IS NOT NULL
LIMIT 25

Aggregate total

SELECT
    sum(content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02) AS total_value
FROM fpds.data
WHERE content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02 IS NOT NULL

Distribution overview

SELECT
    min(content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02) AS min_value,
    avg(content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02) AS avg_value,
    max(content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02) AS max_value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean02 IS NOT NULL

Each dictionary item includes SQL-ready examples generated alongside the variable metadata, allowing immediate use in FPDS Query for filtering, aggregation, and analysis.