Skip to main content

Census Tract Boundaries

census/tiger/cb_tract holds the outline of every US census tract, one partition per vintage year.

Source​

The Census Bureau's national cartographic boundary GeoPackage at the 1:500,000 scale, https://www2.census.gov/geo/tiger/GENZ<year>/gpkg/cb_<year>_us_all_500k.zip, layer cb_<year>_us_tract_500k. The Bureau publishes this national GeoPackage from the 2024 vintage on, so the asset has no partition before 2024.

Cartographic boundary polygons are clipped to the shoreline. TIGER/Line tract polygons include water, so a coastal tract's TIGER/Line outline is larger than its land. An isochrone that covers all of such a tract's land would cover too small a fraction of its TIGER/Line outline.

Columns​

ColumnTypeMeaning
geo_idString11-digit GEOID (state, county and tract), the key of census/acs/acs5_tract
geometryBinaryTract outline as WKB, longitude and latitude in EPSG:4326
land_area_m2Float64The tract's land area (ALAND) in square meters
yearInt64Vintage year
_partitionStringVintage year, the partition key

Coordinates​

The GeoPackage's coordinates are NAD83 (EPSG:4269). Each outline is transformed to EPSG:4326 with pyproj's default NAD83 to WGS84 transformation. That transformation leaves coordinates in the contiguous states, the District of Columbia and Puerto Rico unchanged. It moves coordinates in Alaska and Hawaii by less than 1 m, far below the precision of a 1:500,000 outline.

Checks​

A materialization fails when any of these holds:

  • The layer is missing.
  • The layer's SRS is not EPSG:4269.
  • A GEOID is null, is not 11 characters long, or is repeated.
  • A tract has no ALAND.
  • An outline is not a valid polygon or multipolygon.

Adding a vintage​

A deployment starts with no partitions. To add a vintage from 2024 on:

  1. Add the year, such as 2025, to the dynamic partitions census_tiger_cb_tract_years in Dagster+.
  2. The component's eager automation materializes the new partition. If no run starts, materialize the partition by hand.

To turn automation off, set automation: null in the asset's defs.yaml.

Resources​

The asset reads the layer in batches of 2,000 tracts and does not hold the whole table in memory. Peak memory for the 2024 vintage is about 590 MB. ecs_vcpu and ecs_memory_gb in the asset's defs.yaml set its ECS task size. A run's largest resource need is disk. The downloaded zip is deleted only after the GeoPackage is extracted from it, so a run briefly holds both: about 940 MB for the 2024 vintage.