This page documents the full Decisions dataset, a superset of what the API returns. The API
DecisionsRead response exposes a subset of these fields, some under different names — notably when → decision_date, link → source_url, applicant → applicant_name, owner → owner_name, developer → developer_name, representative → representative_name, address_1/address_2/address_3 → street / city / state, and size_ac/size_sf → lot_size (the API also adds project_value). See the API Reference for the exact API schema.Core Metadata
Location Data
Geographic coordinates enable mapping and spatial analysis. The geographic identifiers (
address_id, city_id, county_id, jurisdiction_id) are flat fields you can use to join decision data with other Shovels datasets. Unlike permits, decisions do not nest these in a geo_ids object.Zoning Details
Example:
zoning_previous: “R-1” (Single-Family Residential)zoning_new: “MF-2” (Multifamily Medium Density)
Property Information
Regulatory Parameters
These fields capture the development rules associated with the decision:Involved Parties
Decisions often identify the people and organizations involved:Applicant
The person or entity requesting the zoning action.Property Owner
Development Team
Each role may include associated
_email, _linkedin, and _website fields when available.
Descriptive Content
Metadata Fields
Not all fields are populated for every decision. Field availability depends on what information was included in the source documents.