Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use topic
No spam. Unsubscribe anytime.
Council approves ordinance to vacate lots in Shannon Heights to enable residential development
Summary
The Marion City Council unanimously approved Ordinance 4095 to vacate selected lots in the Shannon Heights subdivision, allowing a developer to consolidate parcels for a new residential project. Council discussed vacancy status and GIS imagery before the vote.
The Marion City Council voted unanimously to approve Ordinance 4095, vacating multiple lots in the Shannon Heights subdivision so the parcels can be combined to facilitate a forthcoming residential development by Bud Slick Development.
Mayor Absher introduced the ordinance as a step to simplify a parcel map that currently contains a large number of irregularly shaped lots. According to staff, the change would allow the developer to consolidate roughly 36 parcel identification numbers into fewer buildable parcels to support planned housing and duplex construction. "We think divide their property up just into 5 parcels where they'll build these properties instead of trying to manage 36 property identification numbers," the mayor said during the discussion.
A council member asked whether the lots were vacant; staff and other council members clarified that the lots do not contain structures and that some publicly available GIS imagery may be outdated. The council did not amend the ordinance and approved it by roll call with all members voting yes.
The ordinance was presented as part of item 6a on the agenda; staff said the change is intended to streamline land records and support the developer's checklist for starting construction this summer. The council did not specify permit or construction timelines during the meeting.
Background: The ordinance was described on the record as related to the Shannon Heights subdivision and the planned work by Bud Slick Development. Details about the final number of homes, financing or construction schedule were not specified in the meeting record.
