FPDS Query Library
About Us
Contact Us

Generic Boolean01

A numeric boolean indicator in the IDV Generic Tags section that records the value of custom boolean flag 01. It is an extensible tagging field intended to store a true/false-style flag for internal, workflow, or analytical use rather than a standard FPDS procurement attribute.

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

Variable Overview

FPDS Query Variable
content__IDV__genericTags__genericBooleans__genericBoolean01
Title
Generic Boolean01
FPDS Path
IDV/genericTags/genericBooleans/genericBoolean01
Description
A numeric boolean indicator in the IDV Generic Tags section that records the value of custom boolean flag 01. It is an extensible tagging field intended to store a true/false-style flag for internal, workflow, or analytical use rather than a standard FPDS procurement attribute.
Business Meaning
This field matters when an organization uses custom tagging to segment IDVs for reporting, review, or downstream business rules. In procurement analysis, it can help isolate subsets of awards, support reusable filters, or mark records that meet a particular internal condition not represented by standard FPDS fields.
Example Value
0
Observed Non-Null Count
695,693

FPDS Compare

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

Use Cases

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

Common Usage

  • filtering IDVs for custom business rules
  • grouping awards into analyst-defined segments
  • supporting reusable query flags in dashboards

Common Mistakes

  • assuming the field has government-wide standardized meaning
  • treating it as a continuous numeric measure instead of a boolean flag

Query Guidance

Use it in WHERE clauses as a flag filter, for example `= 1` for true-like records and `= 0` for false-like records, after confirming the source convention. If the dataset contains nulls or non-binary values, normalize them explicitly with CASE logic before aggregation or joining to other indicators.

SQL Examples

Preview values

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

Aggregate total

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

Distribution overview

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