FPDS Query Library
About Us
Contact Us

Generic Boolean02

Numeric flag in the Other Transaction IDV Generic Tags section representing the second reusable boolean indicator attached to the award record. It typically stores a binary value such as 0 or 1 to indicate whether the corresponding custom condition is present.

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

Variable Overview

FPDS Query Variable
content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean02
Title
Generic Boolean02
FPDS Path
OtherTransactionIDV/genericTags/genericBooleans/genericBoolean02
Description
Numeric flag in the Other Transaction IDV Generic Tags section representing the second reusable boolean indicator attached to the award record. It typically stores a binary value such as 0 or 1 to indicate whether the corresponding custom condition is present.
Business Meaning
This field supports flexible tagging of Other Transaction IDVs for segmentation, compliance review, and custom reporting when standard FPDS attributes are insufficient. Analysts use it to identify subpopulations of awards relevant to specific policy questions, extraction rules, or internal tracking workflows.
Example Value
0
Observed Non-Null Count
6,280

FPDS Compare

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

Use Cases

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

Common Usage

  • Filter awards matching a custom business rule
  • Create counts or rates for a tagged subgroup
  • Join or group records in reusable analysis workflows

Common Mistakes

  • Assuming 1 always means yes without validating the local code definition
  • Using the field as a descriptive label instead of a binary indicator

Query Guidance

Use explicit value tests such as = 1, = 0, or IS NULL depending on the analysis, and validate the coding scheme before applying logic. If the field is sparsely populated or implementation-specific, combine it with record type, award type, or related tag fields to avoid misclassification.

SQL Examples

Preview values

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

Aggregate total

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

Distribution overview

SELECT
    min(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean02) AS min_value,
    avg(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean02) AS avg_value,
    max(content__OtherTransactionIDV__genericTags__genericBooleans__genericBoolean02) AS max_value,
    count() AS record_count
FROM fpds.data
WHERE content__OtherTransactionIDV__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.