Skip to content

[Warning] Missing Census blocks from in LODES jobs data #280

Description

@bryce-sandag

Describe the warning

While reviewing pull request #279, I came across a unique geography case that led to a discussion about how the LODES data does not include complete coverage of census blocks for every year because blocks are not in final data set if there are no jobs reported for a given census block.

This was discovered while investigating 2020 census block 060730083763001, where the below query returns no results.

SELECT [YEAR], [C000] AS [all_jobs] 
FROM [socioec_data].[lehd].[lodes_8_wac]
WHERE 
        [SEG] = 'S000' -- 'S000' = 'Total number of jobs' 
        AND [TYPE] = 'JT00' -- 'JT00' = 'All Jobs' 
        AND [version] = 2 -- lodes v8.4
        AND [YEAR] >= 2020
        AND [w_geocode] = '060730083763001'

After doing some investigating a block is not reported in the lodes jobs datasets where there is no jobs. which is confirmed with query below:

SELECT [year], [C000] AS [all_jobs]
FROM [socioec_data].[lehd].[lodes_8_wac]
WHERE 
    [SEG] = 'S000' -- 'S000' = 'Total number of jobs' 
    AND [TYPE] = 'JT00' -- 'JT00' = 'All Jobs' 
    AND [version] = 2 -- lodes v8.4
    AND [C000] = 0 -- ALL jobs

This should not affect how jobs data is allocated but could lead to some discrepancies when comparing to EDD point level data, especially if there is any other unique geography cases such as 2020 census block 060730083763000 and 060730083763001 as discussed in review of pull request #279

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    No fields configured for Warning.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions