St. Paul Park City Council — Transcript
Monday, October 12, 2026
Summergate Development Concept Plan Review
Votes (1)
Concept Plan Review for Summergate Development, Mississippi River Property
Dissent: Patrick DS (Chair) opposed the motion to continue hearing from the audience, advocating for declining comments due to perceived deficiencies.
Moved by Richard (Commissioner) [00:44:26] · Seconded by Mr. Hagerty (Commissioner) [00:44:40]
The city planner, Nate Sparks, presented the concept plan outlining 299 single-family homes and discussed its general alignment with the comprehensive plan's density and open space goals, while noting anticipated challenges with Murka regulations and PUD flexibility. Chair Patrick DS extensively critiqued the plan's deficiencies based on a DNR letter, highlighting inaccuracies in bluff lines, shoreland definitions, lot placements, and open space calculations, which he argued rendered the plan 'not ripe for municipal review.' He also cited several city ordinances (74-68, 74-69) that he believed the submitted concept plan failed to meet in terms of required statements and detailed tabulations. The developer, Brian Tucker, acknowledged the DNR comments as 'technical items' typical for a concept plan stage and expressed willingness to address them, emphasizing the need for general feedback on layout and unit mix. Whitney Clark from Friends of the Mississippi River supported the Chair's concerns, calling the plan 'disrespectful' due to its calculation deficiencies and stressed the site's ecological importance. Despite the procedural debate, the commission ultimately voted to hear comments from the audience.
Notable Quotes (7)
So in the comprehensive plan this is identified as being you know your regular single family residential is like 3 to five units per acre for low density. This is two to five. But then the comp plan specifies that it's single family only like you can't balance densities with apartments, town homes and and uh so it's just single family on this side and it can go down as low as two units per acre. Uh so it's two to five is the acceptable range.
The rule is by PUD as we call it plan unit development PUD you can get flexibility but you are required to meet the densities in the comprehensive plan. So, you can't exceed the comp plan density by PUB, but you can create custom zoning standards to create a community like this that balances densities um in order to um you know, better meet some standard that you're looking to do or achieve some goals you're trying to achieve.
So when I see number six which says that okay this all this giant swath of open space which I'm assuming is part of the math that they use to come up with this little table at the bottom right which kind of gives us our percentages and our acres. It would appear that if if none of this is available and if we have bluff issues, shoreline issues and other measurement and w and depth issues, it is technically and literally impossible for us to determine whether or not they've met any criteria or standards, whether they've met the 50% open, whether they've met any of the the lot size width or deaths because it would appear that almost all of these at some point might be touching either a bluff or a shoreline or an area that's going to cause us to have to relook at this.
If the DNR itself has identified multiple critical failures in the plan and they themselves say this thing is not ready for us to review. My question is why are we here?
I would like to clarify that those first five items are technical items. This is a concept plan. So, we do not invest, nor does any developer invest hundreds of thousands of dollars in finalized topography and engineering plans. It's a given that we have to address those issues. If through the process of formal plan submitt we identify that the bluff line was shown in the wrong place, we have to deal with that.
I I don't think they're just technical issues. I think I think this concept plan is disrespectful to the city to bring forward something that is so far off in the way that it calculates the densities. Uh it it puts it makes uh makes your your job impossible. how you could possibly determine what the densities are here or whether they're meeting the open space requirements under the critical area with this plan. It's impossible.
I appreciate that the diligence is being put forward to address all these things and that we don't just rubber stamp it without really understanding the importance not just as a a development um the benefits of what it brings to the city but um moving forward in the the parcels of property that we have left in the city to develop. I believe that it as a riverfront property that complete diligence is welld deserved.
Ordinances & Resolutions (12)
City's plan identifying the area as critical area residential (2-5 units/acre, single family only) and guiding park/trail development.
Existing zoning for the property, allowing 75-foot wide, 9,000 sq ft lots.
Special regulations for properties along the river, including the rural open space subdistrict requiring 50% open space.
Minnesota River Corridor Critical Area rules update, impacting open space requirements.
Proposed development type for flexibility from strict zoning standards, requiring a community benefit.
Submission requirements for PUD general concept stage, cited by Chair DS as potentially unmet.
Procedure for processing a PUD, cited by Chair DS as potentially unmet regarding concept plan details.
City plan identifying future park search areas and guiding parkland dedication.
City plan calling for connections between parks through trail systems.
Environmental review document required for 299 units, needing to be updated/renewed.
Letter from the Department of Natural Resources identifying critical deficiencies in the concept plan's accuracy and compliance.
Alternative environmental review document to AUR, less preferred in this case.