Challenging the ACS-based assumptions used to justify a 0.7 spaces/unit parking standard and zero-parking exemptions for affordable and small-unit housing.
⚠ Critical Review of Proposed Zoning PolicyAdam Krom presented American Community Survey (ACS) data to support a proposed parking ordinance requiring only 0.7 parking spaces per unit, with zero-parking requirements for affordable housing and units under 750 sq ft. This analysis demonstrates that the data is statistically unreliable for policy use, misrepresents actual car ownership, and would create a significant parking deficit by the proposal's own math.
Krom cited the U.S. Census Bureau's American Community Survey (ACS) 5-Year Estimates (Table B25044) for Narberth Borough (ZIP/place code 42526), presented as a cross-tabulation of vehicle availability by tenure. The table below reproduces his figures exactly.
| Category | Owners | Renters | Total | % of Total |
|---|---|---|---|---|
| Total Households | 1,107 | 894 | 2,001 | 100% |
| With 0 Vehicles | 0 | 98 | 98 | 5% |
| With 1 Vehicle | 413 | 582 | 995 | 50% |
| With 2 Vehicles | 560 | 192 | 752 | 38% |
| With 3 Vehicles | 87 | 10 | 97 | 5% |
| With 4 Vehicles | 47 | 12 | 59 | 3% |
| With 5+ Vehicles | 0 | 0 | 0 | 0% |
ACS estimates for small geographies like Narberth Borough (~4,400 residents) carry substantial margins of error. Narberth is a small place — the ACS samples a fraction of its households. This is not a critique of the Census Bureau; it is a fundamental limitation the Bureau itself acknowledges. Using these estimates as the basis for binding zoning policy is statistically inappropriate.
| Category | Estimate | Margin of Error (±) | MOE as % of Estimate | Reliability |
|---|---|---|---|---|
| Total Households | 2,001 | ±159 | 7.95% | Acceptable |
| Owner Occupied | 1,107 | ±149 | 13.46% | Marginal |
| Owner – 1 Vehicle | 413 | ±109 | 26.39% | Unreliable |
| Owner – 2 Vehicles | 560 | ±137 | 24.46% | Unreliable |
| Renter Occupied | 894 | ±193 | 21.59% | Unreliable |
| Renter – No Vehicle | 98 | ±80 | 81.63% | Statistically Invalid |
| Renter – 1 Vehicle | 582 | ±149 | 25.60% | Unreliable |
| Renter – 2 Vehicles | 192 | ±132 | 68.75% | Statistically Invalid |
| Renter – 3 Vehicles | 10 | ±16 | 160.00% | Statistically Invalid |
| Renter – 4 Vehicles | 12 | ±18 | 150.00% | Statistically Invalid |
Red line = 30% threshold (Census Bureau reliability benchmark). Values above are flagged as unreliable for policy decisions.
Error bars show ±MOE. Notice how "No Vehicle" could range from 18 to 178 households — a 10× swing.
Krom's "76% have 1 or 0 cars" framing groups households that need parking (1 car) with those that don't (0 cars). Correctly disaggregated, the data tells a very different story.
"76% of renters have 1 or 0 cars" — conflates car owners with non-owners to minimize perceived demand.
88% of renters own at least one car and need at least one parking space. Only 11% own no car.
| Framing | Krom's Claim | Accurate Reading |
|---|---|---|
| Renters with 0 cars | Bundled into "76%" | 11% (98 of 894) |
| Renters with 1 car | Bundled into "76%" | 65% (582 of 894) — these people need parking |
| Renters with 2+ cars | ~24% | 24% (214 of 894) — these people need 2+ spaces |
| Renters who own a car (need parking) | Not stated | 88% (796 of 894) |
| Implied parking spaces needed per unit | 0.7 (proposed) | ≥0.88 (minimum, single-car owners only) |
Using a hypothetical 40-unit development at 198 Elmwood Avenue as a concrete test case, we can demonstrate that the proposed parking formula fails on its own terms — using Krom's own data.
| Scenario | Exempt Units | Spaces Required (0.7×) | Spaces Needed (88% ownership) | Deficit |
|---|---|---|---|---|
| Krom's Proposed Standard 4 affordable + 6 small-unit exempt |
10 | 21 spaces (0.7 × 30 non-exempt units) |
35.2 spaces (88% × 40 units) |
−14.2 spaces |
| Maximum Possible Under Proposal Only 4 affordable units exempt, all others >750 sq ft |
4 | 25.2 spaces (0.7 × 36 units) |
35.2 spaces | −10 spaces |
| Industry Standard (1.0/unit) | 0 | 40 spaces | 35.2 spaces | +4.8 buffer |
A likely response to parking concerns is that Narberth qualifies as a Transit-Oriented Development (TOD) zone, which often allows reduced parking. This argument fails on several grounds.
There is no single, legally binding federal or Pennsylvania definition of Transit-Oriented Development. Definitions vary widely across municipalities, MPOs, and state agencies. The most commonly cited standard:
Narberth train station is a SEPTA Regional Rail stop (Paoli/Thorndale line) — not a high-frequency urban rail system.
High car ownership persists in suburban rail communities. Narberth is a commuter suburb, not an urban transit hub.
| TOD Criteria | Krom's Implied Position | Reality |
|---|---|---|
| Transit type | Narberth SEPTA station = TOD qualifier | Commuter rail, 1-2 trains/hr peak — not high-frequency transit |
| Geographic scope | Station area = reduced parking zone | Under broadest PA interpretation, all of Narberth is "TOD" — making it useless as a standard |
| Car ownership behavior | Transit access reduces car ownership | ACS data shows 88% of Narberth renters still own cars despite being near transit |
| Comparable standards | 0.7 spaces/unit appropriate for TOD | 1.0 spaces/unit is the typical suburban minimum; industry standards for suburban multifamily range from 1.0–1.2 |
A neighborhood survey of Narberth Borough residents — conducted independently — collected 55 responses from households across the Borough. While not a statistically representative sample, the survey provides hyperlocal ground-truth data that directly contradicts the ACS estimates being used to justify the proposed parking standard.
55 deduplicated Narberth household responses.
% of renter/resident households with 0 cars vs. 1+ cars.
Respondents ranked four development scenarios from 1 (most preferred) to 4 (least preferred). The results are unambiguous: Single Family (2–4 homes) is overwhelmingly the most preferred, and Max Density (30–40 units) is overwhelmingly the least preferred.
Lower score = more preferred. Single Family averages 1.25 — near-unanimous first choice. Max Density averages 3.93 — near-unanimous last choice.
Out of 55 respondents. Single Family received 45 first-place votes. Max Density received just 2.
How respondents distributed their rankings for the highest-density option.
How respondents distributed their rankings for the lowest-density option.
| Density Option | Avg Rank Score | # Ranked 1st | # Ranked 2nd | # Ranked 3rd | # Ranked 4th (Least) | Community Verdict |
|---|
How does the proposed 0.7 standard compare to actual parking requirements in comparable suburban Philadelphia communities and national affordable housing standards?
| Community / Standard | Parking Requirement | Notes |
|---|---|---|
| Krom's proposal — Narberth | 0.7 spaces/unit (non-exempt) | With zero-parking for affordable & <750 sq ft units |
| Narberth Borough (current) | 1.0–1.5 spaces/unit | Existing zoning baseline |
| ITE Parking Generation Manual (suburban multifamily) | ~1.0–1.2 spaces/unit | Industry standard for suburban apartment |
| HUD minimum (affordable housing) | 1.0 spaces/unit | Typical FHA/HUD underwriting assumption |
| Typical TOD reduction (urban, high-frequency rail) | 0.5–0.8 spaces/unit | Applies to true urban TOD, not suburban commuter rail |
| Narberth survey average | 1.87 cars/household | Local ground truth, all respondents |
Krom's 0.7 proposal vs. comparable community and industry standards.
For a 40-unit building, how many spaces different standards would require.
Narberth Borough has invested significantly in its own long-range planning. Key documents from the Borough's own planning process contradict the premise that minimal parking is appropriate — and establish that the community itself prioritized parking and character preservation.
Adopted after an "extensive public engagement process," the 2040 Plan serves as the Borough's binding long-term guide for growth and development. The Plan explicitly aims to "maintain the Borough's character" and ensure "growth and change occur in ways that strengthen its walkable downtown."
The 2040 Plan was developed through direct resident input — the same constituency that the ACS estimates (with their massive error bars) fail to accurately represent. Any zoning amendment that contradicts the community priorities established in that Plan should require a new, equivalent level of public engagement before adoption.
Key tension: Reducing parking below demand doesn't strengthen a walkable downtown — it pushes parking conflicts onto surrounding residential streets, undermining the character the Plan sought to protect.
The Planning Commission has been working since mid-2025 on a "policy-neutral" recodification of the Zoning Code — explicitly described as intended to simplify structure, not change policy. Borough Council's directive to the Planning Commission in August 2025 directed them to address "future land uses and housing" — not to unilaterally reduce parking minimums using contested ACS data.
The Planning Commission recommended the recodification to Borough Council in April 2026 without the changes to civic institutional buildings — suggesting the Commission is exercising restraint on contested amendments. A parking standard change of this magnitude deserves the same level of scrutiny.
A Zoning Open House was held February 26, 2026, to gather community feedback on 5B and 4A zoning discussions. The results of that public process — not a single data presentation — should inform parking policy.
The Borough recently granted Preliminary/Final Land Development approval for a redevelopment at 230 Haverford Avenue. That application required full parking and land development review, including a dedicated Parking Lot Parcel (258 Haverford Avenue) as part of the approval package. The developer was required to include an Emergency Vehicle Maneuvering Diagram, Trip Generation Comparison, and full engineering review — demonstrating that the Borough's existing process already demands rigorous parking analysis case-by-case.
The question is: why would the Borough now adopt a blanket low parking standard for future projects that bypasses the rigorous review that 230 Haverford required?
This isn't a criticism of the Census Bureau. The ACS is a well-designed survey — but it is explicitly designed for large-geography analysis, not small-municipality policy decisions. Using it for Narberth (population ~4,400) is like using a bathroom scale to weigh a package to the nearest gram.
The 5-year ACS for Narberth surveys a fraction of households. With ~2,001 estimated households and typical ACS sampling rates for small places (~15–20%), the underlying sample is roughly 300–400 households — spread across 5 years.
The Census Bureau uses Coefficient of Variation (CV) to flag unreliable estimates. A CV above 40% means "use with extreme caution." Most Narberth renter sub-categories exceed this.
Consider what the ACS data actually represents for renter sub-categories:
TOD parking reductions are commonly cited using examples from Austin, TX and suburban Washington, DC. These are instructive examples — but they actively undermine, rather than support, the case for applying TOD standards to Narberth. Here's why.
| Location / Line | Transit Type | Peak Headway | Off-Peak Headway | Parking Standard Used | Appropriate for Narberth? |
|---|---|---|---|---|---|
| Washington DC Metro Red/Blue/Orange/Silver/Green/Yellow lines |
Heavy Rail (subway) | 4–6 min | 10–12 min | 0.0–0.5 spaces/unit (urban stations) | ❌ No — 5–10× more frequent |
| DC Metro Suburban Stations Vienna, Franconia, Shady Grove |
Heavy Rail | 6–8 min | 12–15 min | 0.5–1.0 spaces/unit (with shared parking) | ❌ No — still 4–8× more frequent + dedicated park-and-ride |
| Austin, TX — MetroRail Red Line commuter rail |
Commuter Rail | 30 min (peak only) | No off-peak service | 0.5–1.0 near stations (Austin's own reductions) | ⚠ Similar frequency — but Austin TOD zones are high-density mixed-use, not 0.5 sq mile borough |
| Austin, TX — MetroRapid Bus Rapid Transit lines |
BRT | 10–15 min | 15–20 min | 0.3–0.7 near major stops | ❌ No — BRT, not commuter rail; dramatically different ridership behavior |
| SEPTA Paoli/Thorndale Line Narberth Station |
Commuter Rail (diesel) | ~30 min (rush) | 60 min (off-peak) | Proposed: 0.7/unit | ✓ This is the actual baseline |
The most honest comparison isn't Austin or DC — it's small, walkable suburbs similar to Narberth that are also near commuter rail. Here's what comparable communities actually require:
| Community | Population | Transit Type | Parking Requirement (multifamily) | Notes |
|---|---|---|---|---|
| Haddonfield, NJ | ~11,500 | PATCO High-Speed Line (every 10–15 min) | 1.0–1.5 spaces/unit | Higher frequency than SEPTA Regional Rail; still requires 1.0 minimum |
| Media, PA | ~5,700 | SEPTA Media/Wawa trolley + R3 rail | 1.0 spaces/unit minimum | Downtown TOD overlay; 1.0 maintained despite walkable core |
| Jenkintown, PA | ~4,400 | SEPTA Regional Rail (similar to Narberth) | 1.0–1.25 spaces/unit | Comparable size and transit access to Narberth; no 0.7 standard |
| Collingswood, NJ | ~14,000 | PATCO High-Speed Line | 1.0 spaces/unit (1.5 recommended) | Active TOD planning; still requires 1.0 minimum |
| Ardmore, PA | ~13,000 | SEPTA Regional Rail + Route 100 trolley | 1.0 minimum; structured parking required for large projects | More transit access than Narberth; still holds 1.0 minimum |
| Narberth, PA (proposed) | ~4,400 | SEPTA Regional Rail only (30–60 min headways) | 0.7 (with zero-parking exemptions) | Below every comparable community; weakest transit access of the group |
Lower minutes = better service. Narberth has the worst transit frequency of any community whose parking standards are being cited as justification.
There is a clear relationship: as transit gets better (lower headway), parking requirements decrease. Narberth's proposed 0.7 standard is misaligned with its actual transit service level.
The Delaware Valley Regional Planning Commission (DVRPC) — the regional planning body that covers Greater Philadelphia — uses a multi-factor scoring system to evaluate actual TOD readiness. The criteria include transit service quality, job access by transit, travel time competitiveness, residential intensity, car ownership rates, non-car commuters, and Walk Score.
Under DVRPC's Transit Connectivity Index (TCI) framework, a location's TOD score reflects "the number of transit trips accessible by walking." For a SEPTA Regional Rail station with 30–60 minute headways, the TCI score would score in the lowest tier (1–2 out of 4) — far below what DVRPC considers supportive of TOD parking reductions.
DVRPC also scores stations on Job Access (jobs reachable in 30-minute transit ride) and Non-Car Commuter rate. Narberth's suburban bedroom-community character means most residents commute outward by car, not inward by rail — the opposite of the TOD profile that justifies parking reductions.
Prepared May 2026 · Narberth Borough, PA 19072 · This document is intended for public comment and civic deliberation purposes.