Initially, all three parts of this standard are prefaced by the phrase "safe and adequate" in the <br />opening sentence. If the "safe and adequate" phrase is a part of the standard that is independent <br />of the standards in the subparts, then the standard as a whole is not clear and objective and may <br />not be applied. If, in contrast, the standard is correctly read as being implemented only through <br />the more particular standards listed in (a), (b) and (c), then the focus should be on the <br />substandards in those sections. Furthermore, if it is not clear whether a separate "safe and <br />adequate" determination, is needed, and the standard could be read either way, then the standard <br />as a whole is not clear enough to be applied. <br />The applicant believes that the standard as a whole is sufficiently ambiguous that it should not be <br />applied at all. <br />Looking to the individual subparts of this standard: <br />EC 9.8320(5)(a): EC 9.6800 through EC 9.6875 Standards for Streets, Alleys, and <br />Other Public Ways (not subject to modifications set forth in subsection (10) below). <br />1. The Staff Report, at pages 25 through 30, slogs through about 14 different standards for <br />streets, alleys and other public ways, based on the comments incorporated by Public Works, and <br />it finds compliance without the need for any further right of way dedication or special setback <br />standards. The HO should endorse the findings of compliance in the Staff Report. <br />The Staff relies heavily on the December 8 Memorandum from City Engineer Scott Gillespie, <br />PE, which is Attachment F to the Staff Report. That memo reviews the development proposal <br />for compliance with city road standards, in particular the adequacy of Capital Drive and Spring <br />Blvd., with respect to "capacity, operations and safety." It also reviewed the traffic engineering <br />study submitted by the applicant's engineer. The Gillespie memo concluded: <br />"The applicant's engineer provided a robust traffic study and concluded the <br />existing roadway system is safe and adequate to serve. I have also reviewed the <br />roadway system and conclude there is no evidence to suggest the existing <br />roadways are unsafe or incapable of serving the development site. Therefore, City <br />staff concurs with the applicant's engineer and recommends the existing <br />transportation system is adequate to serve the proposed development and no <br />offsite mitigation is required." <br />2. Opponents take issue with the Staff Report and City Engineer supporting analysis. The thrust <br />of the opposition evidence and argument, however, is that the road situation is neither "safe" nor <br />"adequate." The applicant believes that opponents misunderstand the nature of the standard. It <br />does not invite a new, subjective determination of safety or adequacy. Instead, the "safe and <br />adequate" test has been operationalized in the code to inquire into compliance with the myriad of <br />code standards that are referenced in EC 9.8320(5)(a). That is the analysis conducted by the <br />applicant and the City Engineer and summarized in the Staff Report. The development proposal <br />will have a "safe and adequate transportation system" with respect to streets because it will <br />APP C - Final Argument 4.6.2018 <br />