PARK COST PROFILES — HISTORICAL ESTIMATES
Analysis added October 12, 2026. Source reporting context: KGW, November 2023.

These are historical project proposals, including repairs, improvements, expansion and mixed scopes. They are not current repair budgets, unfunded balances, annual operating expenses, or validated construction bids. No inflation adjustment or completed-work deduction is applied.

Original source: https://flo.uri.sh/visualisation/15494950/embed
Unchanged original export: https://parks.portlandciviclab.org/downloads/park-use/historical-kgw-estimates.csv

park-cost-profiles.csv:
One row for each of 318 Atlas properties. historical_estimate_usd is in dollars. Blank means no matched estimate, not zero need. annual_maintenance_usd is blank because this dataset does not provide annual costs. The sum covers whole properties, including co-located facilities, and may include overlapping project scopes. Property groups are Atlas classifications derived from names and building types; they do not allocate expenses to individual buildings.

project-cost-crosswalk.csv:
All 1,195 original source rows are retained. estimateCents is in cents (divide by 100 for dollars). id locates the row in the source export. propertyId is a unique normalized-name match to an Atlas property; blank means unresolved. No fuzzy matching or proximity assignment. duplicateOf identifies the one exact duplicate row excluded from totals. The original source total is $615,703,721.15. One repeated row contributes $147,006.00. Mapped distinct-row totals are $603,833,908.15; unmatched distinct-row totals are $11,722,807.00. Those three amounts reconcile to the source total. Duplicate exclusion does not resolve other potential overlaps, alternatives or superseded scopes.

Categories are Atlas interpretations of project titles, with expansion and new provision separated when the title explicitly identifies them. Categories are not PP&R budget accounts. Source descriptions provide the recorded reason and scope; they are not independently verified current diagnoses.

Maintenance-cost analysis is reproducible with scripts/build-maintenance-costs.py in the public repository. City condition ratings remain separate and are not used to infer a dollar cost. The City’s later public backlog workbook contains project status but no row-level costs, and is not added to these estimates.

For a current financial plan, verify project IDs, asset/site relationships, remaining scope, completion status, estimate date and basis, secured funding, shared work, alternatives, and incremental operations. Annual maintenance comparisons require property-level labor, materials, contracts, utilities and allocated overhead for the same fiscal year. Revenue and subsidy must be accounted for separately.

LICENSE
CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Credit:
Portland Parks Atlas, Portland Civic Lab (parks.portlandciviclab.org), CC BY 4.0.
Facts from City records stay public records; see ../LICENSE.txt for the scope.