Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Development Code topic
No spam. Unsubscribe anytime.
Palm Coast workshop advances broad rewrite of development code, flags data centers for council review
Summary
Council staff proposed extensive Land Development Code updates that would standardize neighborhood meetings, tighten review procedures, require bonds for master-plan developments, and treat data centers as a prohibited use unless approved by a four‑fifths supermajority.
City planning staff on Tuesday presented a sweeping package of Land Development Code (LDC) amendments that would change how Palm Coast reviews development, not least by putting data centers on a short list of uses that would require a supermajority council vote to allow.
The proposed amendments would standardize neighborhood‑meeting notice and timing, tighten the process for special exceptions and prohibited uses, shorten how long master‑plan developments (MPDs) may sit without activity, and make performance bonds the default condition for MPD infrastructure unless the council waives the requirement.
Why it matters: The package adjusts the city’s front‑line land‑use tools. Staff said the changes are intended to make review more consistent with the city’s recently adopted comprehensive plan and with changes to state law. Council members stressed several policy goals: protecting adjacent neighborhoods, improving public notice, limiting lengthy “paper entitlements,” and ensuring developers build agreed infrastructure.
What staff proposed: Planning manager Fong Wing and Community Development Director Michael Hansen said the LDC edits would: - Require clearer neighborhood meetings (minimum mailing times, meeting summaries, and a waiver procedure where appropriate). - Clarify the special‑exception path and add an explicit process for "prohibited uses" so applicants still have due process to seek council approval; staff recommended that any approved prohibited use be subject to a supermajority (four of five) council vote. - Shorten MPD extension windows; staff proposed limiting developer extensions (council favored reducing multi‑year extensions to a single additional 12‑month extension). - Make construction/performance bonds the starting assumption for MPD infrastructure, with staff required to disclose whether it recommended a bond in the staff report.
Data centers: The discussion drew particular attention. Staff proposed adding a data‑center definition and listing data centers among the uses the council may prohibit by code while allowing a supermajority to approve a specific project. Council members asked staff to sharpen the definition (for example, tiers for hyperscale facilities vs. smaller, low‑impact server facilities) and to add mandatory protection measures should council ever approve a center (closed‑loop water systems, energy‑islanding, sound attenuation and industrial‑use performance standards were suggested).
Council direction and next steps: Council members generally supported tightening timelines and adding default bond requirements. They asked staff to return with clearer definitions and criteria for data‑center types and to incorporate objective review criteria for zoning changes where feasible. Staff said they will bring code revisions back as part of the July LDC wrap‑up and noted the planning board adoption schedule that follows.
Context and follow‑up: The LDC update is part of a larger city effort to align local regulations with the comprehensive plan and recent state statutes. Planning staff said the changes are not intended to prevent investment but to provide a predictable, measurable process for applicants and neighbors. The city will present the redlined code for first reading in August and the planning‑board adoption is scheduled for mid‑July.
