Marion County approves sweeping Land Development Code amendments; board sets 85-foot lot‑width rule with waiver for grading

Marion County commissioners approved amendments to multiple sections of the Marion County Land Development Code at the second and final public hearing on the proposed ordinance. The board voted to adopt staff’s package of changes covering stormwater compliance, driveway and conveyance criteria, floodplain mapping procedures and technical details, and set lot‑grading triggers at 85 feet of frontage with authority for the county engineer or the engineer’s designee to waive the requirement on a case‑by‑case basis.

The changes affect a range of development‑related standards that staff and the Land Development Regulation Commission (LDRC) had reviewed during prior workshops. The package included a switch that lets many single‑family and farm parcels comply through an administrative “stormwater compliance” process rather than pursuing a Development Review Committee (DRC) waiver or major site plan, new driveway‑application drainage and inspection requirements, clarified stormwater management facility access and safety standards, updated conveyance criteria, and clarified technical specifications for pipe bedding and trenching.

Why it matters: The amendments alter when stormwater controls and lot‑grading plans are required for small residential lots, change how some stormwater landscaping requirements are handled near roads and county facilities, and formalize how certain floodplain and mapping actions are submitted. Those changes affect builders, property owners of undeveloped lots and county infrastructure projects and could change permitting steps and costs for many infill residential parcels.

Most‑important details

- Lot‑grading threshold and waiver: The board approved a revision to the lot‑grading provision (agenda item 7) setting the width trigger at 85 feet. The adopted language includes a sentence authorizing the county engineer or the engineer’s designee to waive the lot‑grading plan requirement where the engineer determines it is not needed. Commissioner Stone moved the motion; Commissioner Curry seconded it, and the motion passed.

- Stormwater compliance in lieu of DRC waivers: Staff said the code will require “stormwater compliance in place of a waiver” for situations that previously required a DRC waiver under section 2.21.0.1; the new procedure is intended to allow many single‑family and farm parcels to work directly with county staff and pay a reduced fee instead of seeking a formal waiver hearing.

- Driveway and culvert inspections: The draft adds a drainage demonstration at the time of driveway connection application and requires an inspection when a culvert is needed.

- Stormwater management facility landscaping and DRA buffering: Staff proposed striking the current requirement for landscaping on public frontage of stormwater management areas (DRAs). The meeting included extended discussion and visual exhibits presenting three landscaping alternatives — full code‑compliant planting, reduced planting, and a minimal option keeping a minimum number of shade trees. Commissioners debated maintenance burdens and aesthetics; some members pressed for a minimum of shade trees while others favored leaving design decisions to project planning or targeted county projects. Staff noted pay‑in‑lieu funds and the county’s existing maintenance limits could affect long‑term upkeep.

- Floodplain mapping and Letters of Map Change: The amendments extend the existing no‑fill rule previously limited to FEMA flood zones to also cover county‑determined flood‑prone areas identified by watershed management plans. The code clarifies timing and submittal requirements for letters of map change to align with federal regulations.

- Conveyance, pipe and easement clarifications: The code updates the conveyance criteria (including lane‑spread clarifications), adjusts minimum pipe sizing references (15‑inch minimum replacing previous 18‑inch minimum), and replaces a blanket 20‑foot easement requirement with a table of minimum easement widths that vary by pipe size.

Quotes from the hearing

David Tillman, chair of the Land Development Regulation Commission, warned that changing the lot‑width trigger would affect more undeveloped parcels countywide: “you start looking at the majority of the lots now, in Marion County that are unbuilt that now this affects.” He also raised an estimate for added development cost if grading plans are required, saying survey and drainage plan work could “probably about I’m I’m I’m estimating and guessing… about $2,000” per lot in his view.

Jason Cambry, stormwater engineer, summarized the intended procedural change: “stormwater compliance is now required in place of a waiver,” meaning many small residential parcels would work directly with staff rather than pursue a DRC waiver.

Tracy Straubas, assistant county administrator, told commissioners the business‑impact statement reflected that the proposal reduces an existing landscaping requirement rather than adding a new one: “this request is to reduce the landscaping, so there is no, additional cost.”

Board direction, debate and next steps

Commissioners debated whether to adopt 75 feet (the LDRC preference), 85 feet (staff’s recommended middle ground), or 90 feet (a more conservative technical approach) as the lot‑width trigger. Staff presented parcel counts showing the effect of different thresholds in illustrative subdivisions: in Rainbow Park, a 75‑foot trigger would capture about 29% of parcels, while 85 feet would capture roughly 68% of vacant parcels; countywide staff reported about 13,000 parcels would be captured at 75 feet versus about 33,000 at 85 feet. Commissioners ultimately approved the package with the 85‑foot trigger and added a sentence authorizing the county engineer or designee to waive the lot‑grading plan requirement when appropriate. Staff said the office can screen permits and flag projects programmatically so the waiver/administrative check can be performed without returning every case to the board.

On landscaping for DRAs, commissioners did not adopt a single countywide prescriptive planting standard during the hearing. Instead, the discussion produced direction for staff to consider targeted plantings on county roadway projects, to use existing pay‑in‑lieu funds when appropriate, and to consult the county landscape architect on species selection. Commissioners emphasized maintenance concerns and said more rigorous planting should be applied where long‑term maintenance can be supported.

Vote and formal action

Commissioner Stone moved to approve items 1 through 9 as presented, with the revision to agenda item 7 to set the lot‑width trigger at 85 feet and to allow the county engineer or the engineer’s designee the authority to waive the lot‑grading requirement. Commissioner Curry seconded. The chair called for the vote and the motion carried. (The record shows the motion, second and a voice vote of “Aye;” the transcript does not include a roll‑call or an itemized tally of individual votes.)

What the ordinance text will change in practice

- Small residential and farm parcels that formerly needed DRC waivers to address stormwater and grading may now pursue an administrative stormwater compliance path with a reduced fee. - Driveway applications must address drainage earlier in the permit process and may require culvert inspection. - The no‑fill rule and LOMC timing will apply more broadly to county‑determined flood‑prone areas, potentially affecting some infill approvals. - The lot‑grading threshold was set to 85 feet of frontage; however, the county engineer or the engineer’s designee may waive the requirement when the engineer determines a plan is unnecessary.

Board members and staff said they expect staff to return with clarifying code language or further refinements as specific problem areas are identified and as staff implements the revised permitting workflow.

Ending

The board recessed to prepare for the subsequent public hearing. Any implementation details or ordinance codification text will be completed by staff and reflected in the formal ordinance and code update documents filed with the county clerk.