You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This will take a little bit of infrastructure/backend build out. Or maybe this should replace the Census DP1 database in PUDL?
Additionally, the new guidance specifies adjoining Census tracts that are separated by a river/waterway still count as "adjacent". Make sure this is handled when the new shapefiles are integrated.
The text was updated successfully, but these errors were encountered:
Currently, the Census tract and county boundaries that are being used are from the Census DP1 database integrated with PUDL.
The new energy communities guidance specifies that census tract boundaries should be defined by the 2020 Census with 2020 TIGER/Line Geodatabases.
This will take a little bit of infrastructure/backend build out. Or maybe this should replace the Census DP1 database in PUDL?
Additionally, the new guidance specifies adjoining Census tracts that are separated by a river/waterway still count as "adjacent". Make sure this is handled when the new shapefiles are integrated.
The text was updated successfully, but these errors were encountered: