My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
11/15/2023 PLANNING BOARD Minutes
>
11/15/2023 PLANNING BOARD Minutes
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
1/29/2025 2:40:12 PM
Creation date
2/14/2024 11:56:37 AM
Metadata
Fields
Template:
Mashpee_Meeting Documents
Board
PLANNING BOARD
Meeting Document Type
Minutes
Meeting Date
11/15/2023
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
9
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
16 Great Neck RoadNorth <br />wlashyee, _Massachusetts o2649 <br />Ms. Faulkner also stated the actions are not in any priority, these are things we need to <br />consider doing. <br />Mr. Balzarini would like to prioritize items so that does not become a point of contention. <br />Ms. Waygan stated under time frame there are items, we should list all short time frames first <br />and medium time frames second, and then it would self -sort. <br />Mr. Oakley stated some environmental actions would benefit from being a priority. <br />Mr. Lehrer made a clarifying comment about form based code. This is the Planning Board's <br />plan as well as the Town. Form based code is simply one tool to effectuate goals and <br />objectives defined in this plan. We are not pigeonholing into one mechanism, it would be his <br />recommendation to pursue as another tool. He doesn't think form based code is contrary to <br />development patterns that have been prioritized through discussion. There have always been <br />a misunderstanding about this approach back when Mashpee Commons tried to introduce it. <br />Form based code can work at any density. <br />Ms. Faulkner always felt form based code was hard to understand as it regulates physical form <br />and character of new development. What would form based code over by the former Zachary's <br />look like as opposed to cleaning it up and making it look nice? <br />Mr. Lehrer stated right now you have zoning districts with certain uses, single, no mixture, <br />defined by use and dimensional criteria. Many critiques about what we have now is it creates <br />inconsistent development patterns. There is a different point A and B with not much cohesion <br />between public and private realm. For example at Andy's market, it is not a walkable pattern, <br />you would drive between all the uses. Mashpee doesn't use floor area ratio. It is an interesting <br />way to describe a set of differences that can occur. We use lot coverage. Form based code <br />would divide the town into variable districts. Instead of uses, it prescribes building types. Use is <br />not something that is considered as prominently as is conventional zoning. You would not want <br />to seek heavy industrial next to residential hence why prohibitions are in place. The community <br />defines what is acceptable per district with a predictable pattern between the town and <br />developers. We would prioritize redevelopment over new development and focus on <br />commercial areas for redevelopment. <br />Ms. Waygan noted form based code regulates exterior, what it looks like, not uses inside. <br />There is a big need in town for preexisting non -conforming. There is also a big need for design <br />standards in that area. It might be a good place to start. The Cape Cod Commission is doing <br />their Regional Housing Strategy and they are working on these design standards. They are so <br />general and we can at least adopt them as step one. <br />:l <br />
The URL can be used to link to this page
Your browser does not support the video tag.