Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Site Plan Parking topic
No spam. Unsubscribe anytime.
Planning commission approves Spring Street restaurant site plan with eight conditions to address parking, lighting and drainage
Summary
The commission approved a site plan and parking arrangement for Restaurant Properties LLC (Spring & Quarter) at 887 Spring Street, subject to eight conditions covering parking, lighting cutoff times, landscaping, drainage and alley improvements.
Get email alerts on the Site Plan Parking topic
No spam. Unsubscribe anytime.
The Petoskey Planning Commission approved a site plan and parking plan review for a proposed outdoor dining patio at 887 Spring Street (case number 250‑25) after a lengthy discussion about parking calculations and shared parking rules.
The applicant, identified in the packet as Restaurant Properties LLC (Spring & Quarter restaurant), sought approval for an outdoor patio area on the south side of the restaurant that reduces on‑site parking requirement calculations. Staff and the applicant disagreed over which parking baseline to use when applying the ordinance's shared‑parking maximum (25% of required parking). Lisa, the zoning administrator, reported that current code constrains shared parking to 25% of the required parking and that, by staff calculation, the proposal left a deficit without additional measures. Jason Fape, director of the Department of Public Works, recommended a drainage structure near the building and oversized perforated pipe backfill in a geotextile‑lined trench to allow infiltration and added detention storage; staff included that as a condition.
Key points of debate included the number of seats and the resulting required parking: staff used a seating basis that led to a 42‑space requirement (based on 103 seats at the 2 spaces per 5 seats standard), and later discussion recalculated requirements around 90 seats and 36 spaces depending on assumptions. The applicant argued the code does not explicitly set the laundromat's required parking and asked the commission to apply discretion in determining a defensible required number rather than using the existing on‑site count.
Commissioners and staff examined how many on‑site spaces the revised plan provided (26 on the plan, with a potential reconfigure to 27 or 28), how many shared spaces the adjacent laundromat could effectively make available, and whether on‑street spaces within the 300‑foot radius could be counted. Lisa explained that the shared‑parking allowance is calculated as a percentage of the required parking and not the actual existing count on the adjacent lot; that interpretation gives applicants less shared‑parking credit than if the actual existing count were used. Several commissioners expressed frustration that the current code offers limited discretion for seasonal outdoor seating.
The commission approved the project with eight conditions including: provide a curb‑cut width notation on the site plan; submit a landscaping plan (matching plant materials used on a nearby project to create corridor continuity); provide an outdoor lighting plan with specified cutoff time for patio lighting if used; identify snow‑storage location; screen the dumpster; implement DPW's drainage recommendations; improve the alley to accommodate pedestrian and vehicular access between lots; and reduce total indoor/outdoor seating to meet the ordinance parking requirement (the staff motion language recorded in the meeting specified a reduction to 100 total seats as the condition).
A motion to approve was seconded and passed on roll call: Moss — yes; Newman — yes; Robson — yes; Wilmot — yes; Debmar — yes; Reid — yes; Crombert/Cromberg — yes.
Why it matters: The approval allows the restaurant to add outdoor dining while addressing neighborhood impacts and public‑infrastructure concerns through specific conditions. The item highlighted constraints in the current zoning code for shared parking and seasonal outdoor seating; staff and commissioners noted the city's upcoming zoning rewrite may add greater flexibility.

