FPDS Query Library
About Us
Contact Us

Generic Boolean03

Numeric flag in the Other Transaction Award generic tags that records the value of the third generic boolean attribute. It is a simple 0/1-style indicator, with 0 shown in the example value, and should be interpreted only within the specific FPDS data model context.

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__genericBoolean03
Title
Generic Boolean03
FPDS Path
OtherTransactionAward/genericTags/genericBooleans/genericBoolean03
Description
Numeric flag in the Other Transaction Award generic tags that records the value of the third generic boolean attribute. It is a simple 0/1-style indicator, with 0 shown in the example value, and should be interpreted only within the specific FPDS data model context.
Business Meaning
This field can support reusable filtering and grouping logic across Other Transaction Award records when an agency has populated the generic boolean slot with a meaningful internal indicator. In procurement analysis, it may help segment awards by a custom yes/no attribute, but it has no standalone business meaning unless the associated program or reporting convention is known.
Example Value
0
Observed Non-Null Count
12,012

FPDS Compare

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

Use Cases

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

Common Usage

  • binary filtering
  • award segmentation
  • custom compliance or program flag analysis

Common Mistakes

  • assuming the field has a universal procurement meaning
  • interpreting 0 as a negative outcome without confirming the agency-specific code definition

Query Guidance

Use equality filters or CASE expressions for binary analysis, for example `WHERE content__OtherTransactionAward__genericTags__genericBooleans__genericBoolean03 = 1`. If the field is sparsely populated or inconsistently coded, pair it with null checks and inspect distinct values before aggregating.

SQL Examples

Preview values

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

Aggregate total

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

Distribution overview

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