PRESIDENT’S COURT – THE MAIN ARTICLE — An Example of How Our Government Makes Flawed Development Decisions
June 16, 2013 § Leave a comment
C. DID THE PLANNING STAFF MAKE CORRECT DECISIONS?
Neither the TC, whose members were quite intelligent and reasonably qualified nor the ARB that was represented by one of the most experienced architects in the area, had little influence on the final outcome. The town planning staff that shepherded the project from May 1996 until its approval in March 1997 pulled all the strings and “won” everything that it wanted. Even though its own expertise is limited to planning, it and it alone seems to have decided what was good for the Town.
Early on, without gathering the necessary information, it decided that the developer could not afford to provide active recreation at the site. Using incorrect measures for comparing densities of neighborhoods, it decided that the developer could afford only 27 units. It conveyed these assumptions to the Planning Commission and others in the town and made them stick. Along the way, it decided that the ARB needed to conduct a review of the developer’s proposal. When the ARB’s concerns conflicted with its own decisions, it conveniently ignored them.
Later, it drew up the architectural guidelines for the ARB to use in the site plan stage. It seemed to be telling the respected architects on the ARB what the issues were and what they should decide. It also showed scant respect for the views of the nationally known hydrologist and physicist on the council. During the Town Council consideration of the application, it asserted that storm-water issues should be discussed only at the site planning stage, even though, in this case, they had the potential to limit the number of units that could be built and strongly influence the layout of the development.
The strange part in all of this is that it did not focus on many planning issues – its area of expertise. It did not (1) articulate the effects of accepting a private street, (2) discuss how the phrase “substantial conformity to the GDP” could be used by the developer to his advantage, (3) pay attention to the need for visitor parking, (4) consider how various parts of the code (such as those requiring building of decks) would affect the RGC districts, (5) pay attention to the privacy concerns of future residents, (6) articulate the differences between R-10 districts and the more urban RGC districts, (7) even mention, much less calculate, the monetary benefits the developer could realize by consolidating the three parcels, and (8) consider meeting the spirit of the RGC regulation. Once it had made some of its initial decisions in May-June of 1991, it did only those things that were necessary to shepherd the application through the bureaucracy. The following sections discuss the details.
1. Waiving the Requirement to Provide Dedicated, Active Recreation Area
The case record suggests that almost from day one, the staff, without gathering relevant and appropriate information, without determining the number of units that could be provided, and without developing some sense of the increase in value of the land through consolidation and subdivision, seems to have rushed to judgment and decided to support the application. It gave strong indications of support in memos prepared soon after the developer inquired about the appropriate development of the property.
- In its May 1, 1996 memo, it opined that, “There is a requirement for 700 sq. ft. of “developed, active recreation area” per dwelling unit, and this could constrain density…”
- Its July 10, 1996 memo stated, “…it is possible to argue that it would be difficult for this site to provide a meaningful recreation area. One compromise to consider would be to view (somewhat generously) the open space with the (exercise) trail (it probably amounts to half acre) and this could be argued to meet the letter (not the spirit) of the Zoning Ordinance…” (Italicized words added to reflect staff’s thinking)
There is nothing in the written record to support this judgment. In its rush to judgment, the staff had not thought through two issues related to the trail. First, a large part of the trail proposed by the developer was located in the open space behind 12 homes. The owners of such homes would lose their privacy and their sense of safety. The 12 affected owners certainly would not have supported for the trail. Second, there was no need for an exercise trail, because the Haley Smith Park across the street would have provided sufficient area for walking, running and exercising. What was needed was a common area containing a tennis court, a basketball court, a community garden, or a club house that would make it possible for the residents to enjoy their development and each other’s company. It should be noted that even though the developer reduced the number of units from 35 to 27, the need for active recreation, as contemplated by the RGC zoning, was never mentioned again. The spirit of the RGC zoning seemingly disappeared. The chief implication of this calculation is that rather than rushing to judgment the staff should have carefully conducted its analysis first.
2. Using Incorrect Measure of Density
To measure the “compatibility” of the proposed development with the adjacent neighborhoods, the staff decided to use the concept of theoretical maximum density under R-10 zoning. Its May 1, 1996 memo states, “A strict interpretation of the Comprehensive Plan would conclude that the RGC zoning could be appropriate with a maximum density of 4 dwellings per acre. This would enable the developer to achieve more lots than would be possible under R-10 zoning.” In other words, the staff, right from the start, began to use 4 units/acre as the “standard” for negotiations with the developer. However, there were two issues with its use.
First, this concept, theoretical maximum density, cannot be found in the town code. Instead, the following two terms are given:
- Density, gross: The number of dwelling units on a particular tract or parcel of land divided by the entire area of that tract or parcel.
- Density, net: The number of dwelling units on a particular tract or parcel of land divided by the area of that tract or parcel remaining after subtracting land that is dedicated.
By November 1996, the developer was proposing to build 31 units on 6.26 acres or at a gross density of 4.95 units/acre. The staff was comparing the theoretical maximum density of 4 with the gross density of 4.95 in deciding whether the number of units should be reduced further. Since the theoretical maximum density was equal or almost equal to net density, the staff was really comparing the net density of R-10 neighborhoods with the gross density of the proposed development.
Comparing net density with gross density is like comparing apples and oranges. The staff should have compared the gross density of the adjacent neighborhoods with the gross density of the proposed development. In fact, it should have calculated the actual gross density of the Chandon Woods (and/or the Downs) and compared it with the gross density of the proposed development. Only then its comparison would have been valid.
Our calculations show that 61 homes in Chandon Woods, along with the associated roads, occupy 17.7 acres of land. This means the gross density of Chandon Woods is (and was) 3.45 units/acre. Therefore, the staff should have used 3.45 unit/acre, rather than 4 units/acre, as its baseline for its negotiations with the developer. This difference in the baseline would have made a world of difference in the eventual outcome. The developer would have been permitted to build only 22 dwelling units, or 5 units less than the 27 units approved by the Town Council., 
Assuming that a unit occupies 5,000 sq. ft., the approval of 5 less units would have freed about 25,000 sq. ft of land for a variety of uses including: (1) a wider street, (2) more parking spaces and (3) a dedicated, active recreation area. Some of the extra square footage could even have been used to increase the distances between the homes and mitigate the “wall” effect that exists today.
3. Ignoring The Lot-Size Criteria
The staff totally ignored the lot size requirements under the Neighborhood Preservation mandate. The average lot size in the two adjoining R-10 districts was about 10,000 sq. ft. The average lot size in the proposed development, by comparison, was less than 5,000 sq. ft. If one uses “lot size” as the criterion for comparison, the density of the proposed development was at least twice that under the R-10 zoning. For this reason alone, the new development was not going to have the same character as the adjoining R-10 districts. Notwithstanding this fact, the staff report asserted that the proposed development was compatible with that of the adjoining neighborhoods.
4. Ignoring the Need For Visitor Parking
During its presentation to the Town Council, the staff stated, “… the applicant is providing ample on-site parking. The zoning requirement is for two parking spaces on each lot. The applicant has satisfied this requirement and is providing almost double the amount of required parking under the parking ordinance.” . The staff was referring to the requirement to provide 2 spaces/dwelling units and to the fact that the developer had provided 105 spaces (or about 3.89 spaces/unit). Consequently, it was not referring to the availability of visitor parking.
The staff should have known that this development, with homes clustered together along a narrow private street, would generate visitor-parking needs akin to that of a townhouse development. It could have gotten some idea of the magnitude of the demand for visitor parking by considering the following provisions of the code:
- “for every land use, there shall be provided sufficient area for … parking of all motor vehicles that may be expected to come to the establishment … whether driven by patrons, customers, purveyors, guests, employees or otherwise…”
- “ in townhouse type developments 0.75 cars/dwelling unit for visitors and 0.25 cars/dwelling units for recreation vehicles must be provided.”
Accordingly, it should have asked the developer to provide at least 20 (=0.75*27) visitor spaces, nine more than the 11 that have been provided. If it had done so, the residents’ continual fight for spaces for their guests perhaps would not be so intense.
The staff should also have been aware of the implications of three other aspects of the proposals that affected visitor parking. First, the developer by proposing a “private” street at the re-zoning stage, would have the ability to reduce the width of the street during the site plan stage and (thereby) to increase the size of homes in the development. Second even though the developer had proffered that every unit would have a minimum of 2,800 sq. ft. of finished space, there was no reason to believe that the units would not end up having more finished space. Larger homes would generate more visitor parking. Third, the staff should have known that the developer’s proffer to construct the final development “in substantial conformity to the GDP” was troublesome. He could make substantive changes without being too worried of the rejection by the staff.
Indeed, at the site plan stage (in 1999), the developer proposed a major change that affected the availability of street parking. It proposed to permanently remove the already approved 13 on-street parking spaces, reduce the street width to 24 feet, convert all 1-car garages into 2-car units, increase the length and width of driveways to accommodate two cars and increase the size of the dwelling units to at least 3,300 sq ft of floor space. This change was very significant, but on June 22, 1999, the Town gave conditional approval to the proposal by stating that, “…if at least 75% (11 spaces) of the on-street parking are retained, the proposed plan can be found to be in substantial conformity with the GDP”. To meet this requirement, the developer created at least 8 new street spaces, but located them at the two ends of the street. He couldn’t possibly have located them along the length of the street, because he had narrowed the street to a bare minimum in order to increase the size of the homes and meet other goals. For this reason, this development only has 11 on-street spaces for visitors. Note that even in the site plan stage, visitor parking was not given explicit consideration by the staff.
5. Review Of The Architectural Character
For some reason, even though the developer had indicated that he was building for the “executive class”, the planning staff was concerned about the quality of the dwelling units from the very start. The following comments made in July 1996 reflect some of their concerns:
- “where is the suggestion of quality? … It looks cheap. The units are practically the same…”
- “ re: fence along VB Street: see my alternative sketch. I prefer a wall of high quality landscaping instead of a fence…” (emphasis added)
- Batman needs to come up with a way to assure the Town that he is building for a specific market at a minimum sales price, or something. Otherwise, this development would become a disaster.”
Nothing in the code permits and nothing in their background qualifies the planning staff to substitute their judgment for the judgment of a builder (who was willing take business and financial risks to build 27 homes costing $8 to $10 million). Regardless, the staff pushed forward with public airing of such concerns. Its Dec. 16, 1996 staff report to the Planning Commission depicts a laundry list of items that the developer should be asked to address. The staff even threatened to withhold the approval of the zoning application by asserting that “ support for the rezoning application may depend on (a) the provision of details about the exterior of buildings and yards, (b) the quality of the details proposed, and (c) review by the ARB or review equivalent to the ARB…” Further, it asks the details of “…bays and alcoves…”, siding material, wood accents, landscaping between buildings, treatment of individual yards, site lighting, and decorative fencing. And, it makes many other demands about sidewalk and exercise stations. Needless to say, the staff seems to be designing the development for the builder.
By December 26, 1996, it had forced the developer to proffer that this Residential Garden Court district, is an Architectural Control District for the purposes of this development and later asked the TC to condition its approval upon the acceptance of a list of Architectural Guidelines. This meant that the Architectural Review Board of the Town would have the authority to review the architectural design after the approval of the zoning. Still, the proffer was not sufficient for the staff. It asked for an informal ARB review of the application before the council’s review in February.
The ARB review, though, turned out to be not to the liking of the staff. The review report included the following comments: (1) the proposed development is significantly more dense than R-10 zoning, (2) the development appears to “turn its back” on the neighborhood, (3) while the developer is proposing a “decorative” fence, it will still be the rear of the houses facing Van Buren Street, (4) attach the homes garage-to-garage to limit land area between each home, create more green area and create interesting backyards with private courts, and (5) create more recreational space. The staff made no mention of it in its presentations to the TC.
This review of the ARB came too late to change anything. The staff had already made its decisions several months earlier and the ARB’s comments conflicted with those decisions. However, the chairman of the ARB appeared in person to present its report to the council. The record shows that the councilmembers did not give much, if any, consideration to the major issues raised by the ARB, issues that still plague this development.
6. What Was Missing In The Process
We must go back to the start of the review of the process to find out what went wrong. The review of the application started in May 1, 1996. Somebody on the staff, perhaps the Director of Community Development, or a staff member, or even the Mayor decided that this application was noteworthy and could benefit the Town. But then, a single staff member of the Community Development was left to set the tone of the application. There was no guidance from the council or the mayor. There is no record to suggest that they even knew about the project until it hit their desks in February 1997. It would make matters worse, if they knew about it. This would mean that they did nothing to ensure that the project would be a success.