Yes, another dumb question from someone who thought he knew better.
I'm wrapping up edits on the development code, and one thing that seems to be causing me a great deal of gnashing of teeth are bufferyard requirements between various uses. I've seen two types:
1) Inflexible and almost too simple, using just minimum buffer widths or setbacks.
2) Unbelievably complicated, straight off the pages of the classic Performance Zoning by Lane Kendig, using tens of defined uses; points based on number of trees and their caliper; special provisions for berms, walls, and so on; along with various exceptions, bonuses, waiver provisions, and so on.
I'm trying to keep the code simple, so I don't want to have a 10+ page section on bufferyards like I've seen in some places. Then again, I don't want to just leave it as "just put up a wall"; there should be some flexibility. Right now, my awkward middle ground looks like this:
Consider that this is a hybrid traditional/form-based code for "kinder, gentler suburban context development"; the SmartCode will govern more urban-scale, mixed-use development.
Your thoughts or ideas?