\u201cThe old SALDO is no longer applicable unless the developers submitted their land development before we enacted the new SALDO \u2014 they have the benefit of using either the old or the new,\u201d Pfeiffer said.<\/p>\n
\u201cBut going forward, any new development has to follow this current ordinance.\u201d<\/p>\n
![\"Bethlehem](\"https:\/\/static.lehigh-v.lehigh-valley.production.k1.m1.brightspot.cloud\/dims4\/default\/f33d5f4\/2147483647\/strip\/true\/crop\/917x608+0+0\/resize\/880x583!\/quality\/90\/?url=http%3A%2F%2Flehigh-valley-brightspot.s3.us-east-2.amazonaws.com%2F6e%2Fb5%2F088612c642759a0ff117b2477ce4%2Fbethlehem-eac-saldo-slide.jpg\")
<\/p>\n
Screenshot<\/p>\n
\/<\/p>\n
City of Bethlehem<\/p>\n
Craig Pfeiffer, assistant director of planning and zoning, gave a presentation on changes to the city’s SALDO during the Bethlehem EAC’s monthly meeting.<\/p>\n
What\u2019s in the new SALDO?<\/p>\n
The new SALDO, in the works for four years, is a 102-page document that regulates how land is divided or improved within the city, aligning with the state Municipalities Planning Code.<\/p>\n
Pfeiffer offered one caveat \u2014 the document includes \u201cshould\u201d for some guidelines, and \u201cshall\u201d for others. While the former reads as a suggestion, the latter acts as a guideline.<\/p>\n
\u201cBut we do encourage our development community to not only review this document, but review our review letters, [which] include a lot of this information and where that becomes applicable, where it gives us a little bit more teeth, is when we go to the Planning Commission.\u201d<\/p>\n
Craig Pfeiffer, assistant director of planning and zoning<\/p>\n
\u201cIt’s difficult for us to require developers to do things,\u201d Pfeiffer said. \u201cIt’s obviously easier for us to do it when we’re working within the public right-of-way.<\/p>\n
\u201cBut we do encourage our development community to not only review this document, but review our review letters, [which] include a lot of this information and where that becomes applicable, where it gives us a little bit more teeth, is when we go to the Planning Commission.\u201d<\/p>\n
For his presentation, Pfeiffer focused on Article 134 of the document, which outlines design standards and required improvements, many of which deal with green infrastructure or alternative transportation.<\/p>\n
For example, all new and widened roads and resurfaced roads now should be considered for bicycle traffic.<\/p>\n
And if a building is more than 20,000 square feet, or has more than 20 dwellings, indoor bicycle parking is required.<\/p>\n
There\u2019s also a new section dedicated to green stormwater design.<\/p>\n
\u201cRain gardens, bioswales, some other considerations, these should be installed and planted to promote infiltration and filtering pollutants where appropriate,\u201d Pfeiffer said.<\/p>\n
\u201cStormwater basins should be designed in a more naturalist manner with plantings that do not require weekly mowing or interior of the interior.\u201d<\/p>\n
In addition, the SALDO has guidelines for landscaping. For example, all tree species must be approved by the city forester, and existing healthy, mature trees should be preserved wherever practical.<\/p>\n
While many of the guidelines in the new SALDO support the city\u2019s Climate Action Plan, Pfeiffer said there is room for improvement.<\/p>\n
Electric vehicle infrastructure, just like solar panels, are encouraged rather than required, which he noted is \u201cfrustrating.\u201d<\/p>\n
\u201cWhere we have been successful, we either get the developer to put in EV charging, or we get them to put in the infrastructure so that in the future, it could be hooked up,\u201d Pfeiffer said.<\/p>\n
\u201cAnd that has happened in my tenure. So that’s positive.\u201d<\/p>\n
Another CAP goal, to promote green roofs \u2014 a roof covered in vegetation \u2014 has been unsuccessful, he said, citing the expense.<\/p>\n
Heritage trees<\/p>\n
Also during the meeting, members unanimously voted to accept three nominations for the EAC\u2019s heritage tree program.<\/p>\n