Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Land Use Development topic
No spam. Unsubscribe anytime.
Developer and council discuss 20-foot buffer, precast wall and timing for 5642 Pegasus Drive project
Summary
Developer Sreedhar Vasipalli and staff discussed replacing the required 20‑foot landscape buffer at 5642 Pegasus Drive with an 8‑foot precast concrete wall adjacent to single‑family homes, and council asked staff to add a clear timing condition — proposed at three years tied to building permit issuance — to the staff report.
Developer Sreedhar Vasipalli, who said he owns the property at 5642 Pegasus Drive, appeared at the workshop to discuss buffering and screening for a proposed light‑industrial/office/warehouse development adjacent to single‑family homes.
City staff and the developer said the project currently provides the UDC‑required 20‑foot landscape buffer along the northern and western boundaries but that nearby homeowners prefer a wall or denser screening. Vasipalli told council, "I'm the developer, and I own this property. And I'm trying to construct the, flex industry light industry office warehouse, and I'm looking for an approval from the zoning perspective." (Sreedhar Vasipalli, developer)
The developer and staff presented a site plan and said the applicant prefers to build an 18‑inch precast concrete wall (described in the discussion as an 8‑foot tall precast wall) in lieu of shrubs and trees along the property edge that faces existing residences. Shelby, the city case manager, said staff had contacted two adjacent property owners who "provided their feedback" and preferred a wall. Brian (city staff) summarized how the condition would be written, saying it currently reads that "applicants agree to install an 8 foot tall wall at this location, in lieu of trees and shrubs," and that staff would add timing tied to building permit issuance or construction of specified buildings.
Council members pressed for a clear deadline rather than an open‑ended condition. One councilmember suggested a three‑year timetable: "Let's just throw it out there at 2 let's say it's a 2 year time frame, if that's reasonable, or 3. But if you know, so that they have the assurance that the wall would get built within let's say it's 3 years." (unnamed councilmember)
The developer said his construction schedule is phased and dependent on permit timing and materials costs, and he said he would prefer to install trees and shrubs if the rear buildings are not built immediately but would commit to building the precast wall when those buildings are constructed. Vasipalli said, "But once I start building 1, 2, and 7, absolutely, yes. I mean, before even I start, I think I'll do the free cash concrete 1." (Sreedhar Vasipalli, developer)
City staff and several councilmembers recommended tying the requirement to the issuance of the first building permit for the initial phase or another clearly defined trigger and suggested a three‑year maximum before the wall must be installed. Council discussion indicated staff will revise the condition in the staff report to specify the wall (8 feet tall, precast concrete) in lieu of trees/shrubs and tie installation to either issuance of a building permit for the first phase or the start of construction on the specified buildings, with a proposed three‑year deadline; staff said they would include that clarification on the slide and in the report.
No formal motion or council vote was recorded in the workshop transcript; staff indicated they will prepare the revised condition for the regular meeting agenda.
Ending: Staff said they will update the staff report to reflect the clarified condition tying installation of the precast concrete wall to a building‑permit or construction trigger and the time frame discussed by council.
