FPDS Query Library
About Us
Contact Us

Generic Boolean01

Numeric flag in the award-level Generic Tags area that represents the first generic boolean attribute. It is an encoded yes/no-style field rather than a descriptive text value, so it should be interpreted as a binary indicator with values such as 0 or 1.

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

Variable Overview

FPDS Query Variable
content__award__genericTags__genericBooleans__genericBoolean01
Title
Generic Boolean01
FPDS Path
award/genericTags/genericBooleans/genericBoolean01
Description
Numeric flag in the award-level Generic Tags area that represents the first generic boolean attribute. It is an encoded yes/no-style field rather than a descriptive text value, so it should be interpreted as a binary indicator with values such as 0 or 1.
Business Meaning
This field exists to support reusable classification and filtering across FPDS awards when standard award attributes need supplemental tagging. It can be useful for segmentation, cohort creation, or downstream business rules in procurement analysis, especially when the tag is used consistently within an organization or reporting workflow.
Example Value
0
Observed Non-Null Count
15,520,720

FPDS Compare

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

Use Cases

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

Common Usage

  • Filtering awards into a tagged analysis cohort
  • Grouping records for custom reporting workflows
  • Applying reusable business rules in FPDS extracts

Common Mistakes

  • Assuming the numeric value has a universal business meaning without source validation
  • Using the field as a descriptive label instead of an encoded indicator

Query Guidance

Use explicit predicates on the coded values, such as WHERE content__award__genericTags__genericBooleans__genericBoolean01 = 1 for tagged records. If the field is nullable or inconsistently populated, handle NULL separately and validate the observed code set before aggregating.

SQL Examples

Preview values

SELECT
    content__award__genericTags__genericBooleans__genericBoolean01 AS generic_boolean01
FROM fpds.data
WHERE content__award__genericTags__genericBooleans__genericBoolean01 IS NOT NULL
LIMIT 25

Aggregate total

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

Distribution overview

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