FPDS Query Library
About Us
Contact Us

Generic Boolean03

Numeric custom boolean flag in the FPDS IDV Generic Tags section, stored as Generic Boolean03. It typically records a yes/no-style indicator using coded values such as 0 and 1 for extended or internal tagging purposes.

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__genericBoolean03
Title
Generic Boolean03
FPDS Path
IDV/genericTags/genericBooleans/genericBoolean03
Description
Numeric custom boolean flag in the FPDS IDV Generic Tags section, stored as Generic Boolean03. It typically records a yes/no-style indicator using coded values such as 0 and 1 for extended or internal tagging purposes.
Business Meaning
This field supports reusable filtering and classification in procurement analysis when standard FPDS attributes are not sufficient. Analysts may use it to isolate a portfolio segment, apply internal business rules, or track an overlay condition across IDVs consistently.
Example Value
0
Observed Non-Null Count
695,853

FPDS Compare

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

Use Cases

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

Common Usage

  • Filtering IDVs that meet an internal tagging rule
  • Grouping records for a custom analytic segment
  • Joining to downstream business logic that uses extended FPDS tags

Common Mistakes

  • Assuming the numeric value has a universal government-wide meaning
  • Using the field without validating whether 0 and 1 are the only observed codes

Query Guidance

Use equality filters or CASE logic on the stored numeric code, and document the assumed code meaning in the query. Example pattern: WHERE content__IDV__genericTags__genericBooleans__genericBoolean03 = 1; if the code set is unclear, first run frequency counts and inspect related generic tag fields.

SQL Examples

Preview values

SELECT
    content__IDV__genericTags__genericBooleans__genericBoolean03 AS generic_boolean03
FROM fpds.data
WHERE content__IDV__genericTags__genericBooleans__genericBoolean03 IS NOT NULL
LIMIT 25

Aggregate total

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

Distribution overview

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