Oklahoma City Open Data
Licensing
Parks Impact Fees - Benefit Areas
This dataset shows different park benefit areas in Oklahoma City where development fees apply
Source city: Oklahoma City · Catalog date: June 9, 2026 · License: custom
What this is
This dataset shows different park benefit areas in Oklahoma City where development fees apply.
Why it matters to you
If you’re building a new home, business, or development, these zones determine whether you’ll pay extra fees to fund nearby park improvements. The fees help maintain green spaces, trails, and recreation areas that serve your new development. Knowing your benefit area category could add thousands to your project costs or exempt you entirely.
How to read this data
- Benefit Area: The general neighborhood or region (like “NW 23rd Street Corridor”)
- Category: Fee classification (likely tiers like high/medium/low impact)
- Area: Size of the benefit zone in square feet - bigger areas may mean more shared costs
Where this leaves you
While you can’t look up specific addresses here, this data explains why similar projects in different parts of town might face different park fees. Check okc.gov’s development fee pages for exact rates tied to these zones.
The fields, explained
Pulled directly from the source catalog's published field definitions — not paraphrased.
| Field | What it means |
ObjectID | Numeric unique identifier with no special meaning |
Benefit Area | General location of are within the City of Oklahoma City |
Category | Classification of benefit area |
Shape | Geographic data in state plane coordinates (WKID 103512) |
Length | Approximate length of perimeter of feature in US feet |
Area | Approximate area of feature in US square feet |
From the source — real records
Unedited rows from Oklahoma City's published service, pulled when this site was built.
Look it up yourself
Everything on this page comes from the city's public open-data catalog. Anyone can download it — CSV, GeoJSON, KML, or the live service.
This explainer was written from the published catalog record. Always verify against the source dataset before relying on it for a decision.