Canonical names and compatibility layers
Homecastr's forecast APIs span several geographic levels. This page records the names the app expects so database tables, RPC wrappers, and public docs stay aligned when source tables vary by jurisdiction.
Source: geo_county20_us.county_fips
County forecasts expect a normalized geoid column.
Source: geo_tabblock20_us.geoid
Canonical tabblock table in production. Keep geo_tabblock20_tx and geo_tabblock20_tx_z13 as legacy fallbacks during the transition.
Source: state_forecast_by_year.geoid
State forecast-by-year rows join on the normalized geoid key.
Source: Derived from geo_tract20_us
Used for tract autocomplete and lookup.
RPC wrappers
Keep public RPC wrappers in the public schema when PostgREST exposure matters.
Use wrappers to bridge schema-cache issues and preserve stable names for clients.
Document required columns such as source_origin_year and as_of_date.
Documentation
Reference, guide, and status pages share this navigation so the public docs set stays consistent.