Loading...
HomeMy WebLinkAbout02/27/2018 - Regular - Packet City of Port Orchard Council Meeting Agenda February 27, 2018 6:30 p.m. 1. CALL TO ORDER A. Pledge of Allegiance B. Council Photo 2. APPROVAL OF AGENDA 3. CITIZENS COMMENTS (Please limit your comments to 3 minutes for items listed on the Agenda and that are not for a Public Hearing. When recognized by the Mayor, please state your name for the official record ) 4. CONSENT AGENDA (Approval of Consent Agenda passes all routine items listed below, which have been distributed to each Councilmember for reading and study. Consent Ag enda items are not considered separately unless a Councilmember so requests. In the event of such a request, the item is returned to Business Items.) A. Approval of Checks and Payroll B. Adoption of an Ordinance Amending POMC Section 15.30.070 Discharge Prohibitions (Dorsey) Page 3 C. Approval of a Contract with Kitsap County – Participation in the 2020 Census Local Update of Census Address Operations – LUCA (Bond) Page 15 5. PRESENTATION 6. PUBLIC HEARING 7. BUSINESS ITEMS A. Adoption of an Ordinance Adopting a New POMC Chapter 20.127 Design Standards, Repealing Ordinance No. 1479, and Amending Chapters 20.12 Definitions, 20.38 Overlay Districts, and 20.100 Development Standards-Design Guidelines (Bond) Page 21 B. Adoption of an Ordinance Amending POMC Chapter 2.78 Design Review Board (Bond) Page 213 C. Adoption of a Resolution Approving the Conversion from GAAP to CASH (Crocker) Page 223 D. Approval of the February 13, 2018, Council Meeting Minutes Page 227 E. A Motion Directing the Mayor to Pursue the Opportunity Zone Program (Bond) Page 233 F. Discussion: Vision 2040 Scoping Notice and Comment Period (Bond) Page 237 G. Discussion: Brokers Price Opinion for 640 Bay Street Property Value (Mayor) H. Discussion: Council Retreat Topics and Format (Mayor) Mayor: Rob Putaansuu Administrative Official Councilmembers: Bek Ashby Chair: ED/Tourism/LT Committee Staff: Development Director Finance Committee KRCC / PSRC TransPol / KRCC TransPol KRCC PlanPol-alt / PRTPO Shawn Cucciardi Finance Committee Land Use Committee PSRC EDD-alt Fred Chang Utilities Committee Sewer Advisory Committee (SAC) Jay Rosapepe ED/Tourism/LT Committee Utilities Committee Sewer Advisory Committee (SAC) KRCC-alt / KRCC TransPol-alt John Clauson Chair: Finance Committee Staff: Finance Director Kitsap Public Health District-alt KEDA/KADA-alt Cindy Lucarelli Chair: Utilities Committee Staff: Public Works Director Sewer Advisory Committee (SAC) Staff: Public Works Director Chair: Chimes and Lights Committee Staff: City Clerk KEDA/KADA Scott Diener (Mayor Pro-Tempore) Chair: Land Use Committee Staff: Development Director ED/Tourism/LT Committee PSRC Growth Mgmt-alt Department Directors: Nicholas Bond, AICP Development Director Mark Dorsey, P.E. Director of Public Works/City Engineer Debbie Hunt Court Administrator Noah Crocker, M.B.A. Finance Director Geoffrey Marti Police Chief Brandy Rinearson, MMC, CPRO City Clerk Contact us: 216 Prospect Street Port Orchard, WA 98366 (360) 876-4407 Please turn off cell phones during meeting and hold your questions for staff until the meeting has been adjourned. The Council may consider other ordinances and matters not listed on the Agenda, unless specific notification period is required. Meeting materials are available on the City’s website at: www.cityofportorchard.us or by contacting the City Clerk’s office at (360) 876-4407. The City of Port Orchard does not discriminate on the basis of disability. Contact the City Cler k’s office should you need special accommodations. February 27, 2018, Meeting Agenda Page 2 of 2 8. REPORTS OF COUNCIL COMMITTEES 9. REPORT OF MAYOR 10. REPORT OF DEPARTMENT HEADS 11. CITIZEN COMMENTS (Please limit your comments to 3 minutes for any items not up for Public Hearing. When recognized by the Mayor, please state your name for the official record) 12. EXECUTIVE SESSION: Pursuant to RCW 42.30.110, the City Council may hold an executive session. The topic(s) and the session duration will be announced prior to the executive session. 13. ADJOURNMENT COMMITTEE MEETINGS Date & Time Location Finance TBD; 7:30am City Hall Economic Development and Tourism March 12, 2018; 9:30am City Hall Utilities March 19, 2018; 9:30am City Hall Sewer Advisory April 18, 2018; 6:30pm SKWRF* Land Use March 5, 2018; 9:30am DCD** Lodging Tax Advisory TBD City Hall Festival of Chimes & Lights March 19, 2018 3:30pm City Hall Council Retreat May 18, 2018; TIME TBD TBD Outside Agency Committees Varies Varies *South Kitsap Water Reclamation Facility, 1165 Beach Drive East, Port Orchard **DCD, Department of Community Development, 720 Prospect Street, Port Orchard CITY COUNCIL GOOD OF THE ORDER City of Port Orchard 216 Prospect Street, Port Orchard, WA 98366 (360) 876-4407 • FAX (360) 895-9029 Agenda Staff Report Agenda Item No.: Consent Agenda 4B Meeting Date: February 27, 2018 Subject: Adoption of an Ordinance Amending POMC Prepared by: Mark R. Dorsey, P.E. Section 15.30.070 Discharge Prohibitions Public Works Director Atty Routing No.: NA Atty Review Date: NA Summary: On August 11, 2009 the City of Port Orchard City Council ordained that title 15 be amended to include chapter 15.30 (ordinance no. 019-09). Chapter 15.30 specifically addresses Illicit Discharge Detection and Elimination (IDDE), which prohibits certain discharges into the City’s Municipal Separate Storm Sewer System (MS4) and encourages provisions to protect all surface and groundwater within the City from pollution. This ordinance was based upon language from the City’s 2007 -2012 National Pollutant Discharge Elimination System (NPDES) permit, issued by the Washington State Department of Ecology. In the City’s current NPDES permit (2013-2018 permit) text was added to the IDDE section of the permit, clarifying some language from the previous permit relating to prohibited discharges. The attached ordinance incorporates the descriptive text specified by the perm it into the existing text of section 15.30.070, specifically clarifying the term “total residual chlorine” in allowable levels and including text relating to thermally controlling spa or swimming pool discharges. These additions to section 15.30.070 will satisfy the permit requirement for the City. Recommendation: Staff recommends that the City Council vote to adopt an ordinance that includes the revised language into Section 15.30.070 of Title 15, keeping the City in compliance with its municipal stormwater permit. Relationship to Comprehensive Plan: N/A Motion for consideration: “I move to adopt an ordinance that includes the text revisions to Ordinance 019 - 09, keeping the City in compliance with its municipal stormwater permit as presented .” Fiscal Impact: This proposal is not expected to impact the City’s budget. Alternatives: Do not adopt this ordinance, leaving the existing language in Ordinance 019-09 as-is. This will result in the City failing to be in compliance with its municipal stormwater permit. Attachments: Draft ordinance and redline version Page 3 of 260 This Page Intentionally Left Blank Page 4 of 260   ORDINANCE NO. _______________              AN ORDINANCE OF THE CITY OF PORT ORCHARD, WASHINGTON,  AMENDING PORT ORHCARD MUNICIPAL CODE SECTION 15.30.070 ‐  DISCHARGE PROHIBITIONS AND PROVIDING FOR SEVERABILITY AND  PUBLICATION; AND SETTING AN EFFECTIVE DATE.    WHEREAS, the City of Port Orchard desires to reduce the public health and economic  impacts of illicit discharges to the City’s stormwater system and receiving waters, which  includes creeks, streams, and Sinclair Inlet; and    WHEREAS, the City of Port Orchard desires to reduce the impact of pollutants on the  wildlife and aquatic life associated with the receiving waters; and    WHEREAS, the City of Port Orchard is subject to the requirements of the Western  Washington Phase II Municipal National Pollutant Discharge Elimination System (NPDES)  Stormwater Permit issued by the Washington State Department of Ecology which requires  the City to adopt regulations to prohibit certain discharges into the City's stormwater  system and encourages additional provisions to protect all surface and groundwater within  the City; and    WHEREAS, The Port Orchard Municipal Code Title 15 Chapter 15.30 Section 15.30.070  need to be updated to include specific language from the City’s 2013‐2018 NPDES Permit  that is currently not present in the City’s municipal code; now, therefore,     THE CITY COUNCIL OF THE CITY OF PORT ORCHARD, WASHINGTON, DO ORDAIN AS  FOLLOWS:    SECTION 1.  The Port Orchard Municipal Code, Section 15.30.070, is hereby amended to  read as follows:    15.30.070 ‐ Discharge Prohibitions.    A. Prohibition of Illicit Discharges. It is unlawful for any person to throw, drain, or  otherwise discharge, or cause or allow others under its control to throw, drain or  otherwise discharge any materials other than stormwater into the municipal storm  drain system and/or surface and ground waters of the City. Prohibited materials  include, but are not limited to, pollutants or waters containing any pollutants, that  cause or contribute to a violation of applicable water quality standards. The  commencement, conduct, or continuance of any illicit discharge to the storm drain  system is prohibited.    Examples of pollutants include, but are not limited to, the following: trash or debris;  solid waste; construction materials; petroleum products including, but not limited to  Page 5 of 260 Ordinance No. _________  Page 2 of 5  oil, gasoline, grease, fuel oil, heating oil; antifreeze and other automotive products;  fixed and mobile vehicle washes; metals in either particulate or dissolved form in  excess of naturally occurring amounts; flammable or explosive materials; radioactive  materials; batteries; acids, alkalis, or bases; paints, stains, resins, lacquers, or  varnishes; degreasers or solvents; drain cleaners; commercial and household cleaning  materials; carpet cleaning wastes; pesticides, herbicides, or fertilizers; steam cleaning  wastes; laundry waste; soaps, detergents, or ammonia; swimming pool or spa filter  backwash (diatomaceous earth); swimming pool cleaning wastewater; chlorine,  bromine, and other disinfectants; heated water; chlorinated swimming pool or hot tub  water; human and animal wastes; domestic or sanitary sewage; recreational vehicle  waste; animal carcasses; food and food wastes; yard waste; bark and other fibrous  materials (does not include large woody debris in approved restoration projects);  collected lawn clippings, leaves, or branches; wastes associated with building  construction; concrete and concrete by‐products; silt, sediment, including dirt, sand,  and gravel; dyes and ink (except as stated in Port Orchard Municipal Code  15.30.070(B)(5)); chemicals not normally found in uncontaminated water; any other  process‐associated discharge except as otherwise allowed in this section; and any  hazardous material or waste not listed above.    B. Conditional Discharges. The following types of discharges shall not be considered  illicit discharges for the purposes of this Chapter if they meet the stated conditions or  unless the Director determines that the type of discharge, whether singly or in  combination with others, is causing or is likely to cause pollution of surface water or  groundwater:     1. Discharges from potable water sources, including water line flushing, hyper‐ chlorinated (>10mg/liter chlorine) water line flushing, fire hydrant system flushing,  and pipeline hydrostatic test water. Planned discharges shall be de‐chlorinated to a  total residual chlorine concentration of 0.1 ppm or less, pH‐adjusted if necessary, and  volumetrically and velocity controlled to prevent re‐suspension of sediments in the  stormwater system;     2. Discharges from lawn watering and other irrigation runoff; however, these shall be  minimized through water conservation efforts;     3. De‐chlorinated spa or swimming pool discharges. The discharges shall be de‐ chlorinated to a total residual chlorine concentration of 0.1 ppm or less, pH‐adjusted  and re‐oxygenized if necessary, and volumetrically and velocity controlled to prevent  re‐suspension of sediments in the stormwater system. Discharges shall be thermally  controlled to prevent an increase in temperature of the receiving water. Swimming  pool cleaning wastewater and filter backwash shall not be discharged to the storm  drainage system;   Page 6 of 260 Ordinance No. _________  Page 3 of 5    4. Street and sidewalk wash water, water used to control dust, and routine external  building wash down that does not use detergents. The amount of street wash, dust  control, and building wash water shall be minimized. At active construction sites,  street sweeping must be performed prior to washing the street;     5. Dye testing with verbal notification to the City a minimum of 24 hours prior to the  time of the test.     6. Non‐stormwater discharges covered by another NPDES permit, waiver, or waste  discharge order issued to the discharger and administered under the authority of the  Environmental Protection Agency or Washington State Department of Ecology,  provided that the discharger is in full compliance with all requirements of the permit,  waiver, or order and other applicable laws and regulations; and provided, that  written approval has been granted for any discharge to the storm drain system;     7. Discharges resulting from maintenance, repair, or operation of firefighting  equipment and facilities that are not directly associated with public firefighting,  including discharges from public firefighting training exercises, unless City‐approved  best management practices are implemented.     8. Other non‐stormwater discharges shall be in compliance with the requirements of  a stormwater pollution prevention plan reviewed and approved by the City, which  addresses control of such discharges by applying AKART to prevent contaminants  from entering surface or ground water.    C. Allowable Discharges. The following types of discharges shall not be considered illicit  discharges for the purposes of this Chapter if they do not contain pollutants or unless  the Director determines that the type of discharge, whether singly or in combination  with others, is causing or is likely to cause pollution of surface water or groundwater.     1. Diverted stream flows, rising ground waters, uncontaminated ground water  infiltration (as defined in Title 40 of the Code of Federal Regulations: 40 CFR  35.2005(20)), uncontaminated pumped ground water, foundation drains, air  conditioning condensation, irrigation water from agricultural sources that is  commingled with urban stormwater, springs, water from crawl space pumps, footing  drains, flows from riparian habitats and wetlands, and discharges from emergency  firefighting activities in accordance with “S2. Authorized Discharges,” of the City's  NPDES permit.     2. Discharges specified in writing by the City as being necessary to protect public  health and safety.   Page 7 of 260 Ordinance No. _________  Page 4 of 5    3. If a person can demonstrate that there are no additional pollutants being  discharged from the premises above the background conditions of the water entering  the site, that person shall not be in violation of subsection A of this section.     D. Prohibition of Illicit Connections.     1. The construction, use, maintenance or continued existence of illicit connections to  the storm drain system is prohibited. This prohibition expressly includes, without  limitation, illicit connections made in the past, regardless of whether the connection  was permissible under law or practices applicable or prevailing at the time of  connection.     2. Any connection identified by the Director that could convey anything not  composed entirely of surface and stormwater directly into municipal drainage  facilities is considered an illicit connection and is prohibited with the following  exceptions: connections conveying allowable discharges or connections conveying  discharges pursuant to an NPDES permit or a State Waste Discharge Permit.     3. Illicit connections must be disconnected and redirected, if warranted, to an  approved onsite wastewater management system or the sanitary sewer system upon  approval of the City.     4. Any drain or conveyance that has not been documented in plans, maps or  equivalent, and which is connected to the storm sewer system, shall be located by  the owner or occupant of that property upon receipt of written notice of violation  from the City requiring that such locating be completed. Such notice will specify a  reasonable time period within which the location of the drain or conveyance is to be  determined, that the drain or conveyance be identified as storm sewer, sanitary  sewer, or other, and that the outfall location or point of connection to the storm  sewer system, sanitary sewer system or other discharge point be identified. Results  of these investigations are to be documented and provided to the City.     E. Prohibition of Stormwater Discharge to Sanitary Sewer. Stormwater shall not be  discharged into the sanitary sewer without written permission to do so from the City  of Port Orchard.     F. Prohibition of Waste Disposal. No person shall throw, deposit, leave, maintain, or  keep in or upon any public or private property, the stormwater drainage system, or  waters of the state, any refuse, rubbish, garbage, litter, or other discarded or  abandoned objects, articles, or accumulations that may cause or contribute to  Page 8 of 260 Ordinance No. _________  Page 5 of 5  pollution. Wastes deposited in proper non‐leaking waste receptacles for the purposes  of collection are exempt from this prohibition.     SECTION 2.  Severability.  If any section, sentence, clause or phrase of this Ordinance  should be held to be unconstitutional or unlawful by a court of competent jurisdiction, such  invalidity or unconstitutionality shall not affect the validity or constitutionality of any other  section, sentence, clause or phrase of this Ordinance.      SECTION 3.  Publication.  This Ordinance shall be published by an approved summary  consisting of the title.     SECTION 4.  Effective Date.  This Ordinance shall take effect and be in full force and  effect five days after publication, as provided by law.        PASSED by the City Council of the City of Port Orchard, APPROVED by the Mayor and  attested by the Clerk in authentication of such passage this 27TH day of February 2018.                     Robert Putaansuu, Mayor    ATTEST:      SPONSOR:                     Brandy Rinearson, MMC, City Clerk Councilmember Ashby, Councilmember        APPROVED AS TO FORM:                  Sharon Cates, City Attorney    PUBLISHED:  EFFECTIVE DATE:    Page 9 of 260   ORDINANCE NO. _______________              AN ORDINANCE OF THE CITY OF PORT ORCHARD, WASHINGTON,  AMENDING PORT ORHCARD MUNICIPAL CODE SECTION 15.30.070 ‐  DISCHARGE PROHIBITIONS AND PROVIDING FOR SEVERABILITY AND  PUBLICATION; AND SETTING AN EFFECTIVE DATE.    WHEREAS, the City of Port Orchard desires to reduce the public health and economic  impacts of illicit discharges to the City’s stormwater system and receiving waters, which  includes creeks, streams, and Sinclair Inlet; and    WHEREAS, the City of Port Orchard desires to reduce the impact of pollutants on the  wildlife and aquatic life associated with the receiving waters; and    WHEREAS, the City of Port Orchard is subject to the requirements of the Western  Washington Phase II Municipal National Pollutant Discharge Elimination System (NPDES)  Stormwater Permit issued by the Washington State Department of Ecology which requires  the City to adopt regulations to prohibit certain discharges into the City's stormwater  system and encourages additional provisions to protect all surface and groundwater within  the City; and    WHEREAS, The Port Orchard Municipal Code Title 15 Chapter 15.30 Section 15.30.070  need to be updated to include specific language from the City’s 2013‐2018 NPDES Permit  that is currently not present in the City’s municipal code; now, therefore,     THE CITY COUNCIL OF THE CITY OF PORT ORCHARD, WASHINGTON, DO ORDAIN AS  FOLLOWS:    SECTION 1.  The Port Orchard Municipal Code, Section 15.30.070, is hereby amended to  read as follows:    15.30.070 ‐ Discharge Prohibitions.    A. Prohibition of Illicit Discharges. It is unlawful for any person to throw, drain, or  otherwise discharge, or cause or allow others under its control to throw, drain or  otherwise discharge any materials other than stormwater into the municipal storm  drain system and/or surface and ground waters of the City. Prohibited materials  include, but are not limited to, pollutants or waters containing any pollutants, that  cause or contribute to a violation of applicable water quality standards. The  commencement, conduct, or continuance of any illicit discharge to the storm drain  system is prohibited.    Examples of pollutants include, but are not limited to, the following: trash or debris;  solid waste; construction materials; petroleum products including, but not limited to  Page 10 of 260 Ordinance No. _________  Page 2 of 5  oil, gasoline, grease, fuel oil, heating oil; antifreeze and other automotive products;  fixed and mobile vehicle washes; metals in either particulate or dissolved form in  excess of naturally occurring amounts; flammable or explosive materials; radioactive  materials; batteries; acids, alkalis, or bases; paints, stains, resins, lacquers, or  varnishes; degreasers or solvents; drain cleaners; commercial and household cleaning  materials; carpet cleaning wastes; pesticides, herbicides, or fertilizers; steam cleaning  wastes; laundry waste; soaps, detergents, or ammonia; swimming pool or spa filter  backwash (diatomaceous earth); swimming pool cleaning wastewater; chlorine,  bromine, and other disinfectants; heated water; chlorinated swimming pool or hot tub  water; human and animal wastes; domestic or sanitary sewage; recreational vehicle  waste; animal carcasses; food and food wastes; yard waste; bark and other fibrous  materials (does not include large woody debris in approved restoration projects);  collected lawn clippings, leaves, or branches; wastes associated with building  construction; concrete and concrete by‐products; silt, sediment, including dirt, sand,  and gravel; dyes and ink (except as stated in Port Orchard Municipal Code  15.30.070(B)(5)); chemicals not normally found in uncontaminated water; any other  process‐associated discharge except as otherwise allowed in this section; and any  hazardous material or waste not listed above.    B. Conditional Discharges. The following types of discharges shall not be considered  illicit discharges for the purposes of this Chapter if they meet the stated conditions or  unless the Director determines that the type of discharge, whether singly or in  combination with others, is causing or is likely to cause pollution of surface water or  groundwater:     1. Discharges from potable water sources, including water line flushing, hyper‐ chlorinated (>10mg/liter chlorine) water line flushing, fire hydrant system flushing,  and pipeline hydrostatic test water. Planned discharges shall be de‐chlorinated to a  total residual chlorine concentration of 0.1 ppm or less, pH‐adjusted if necessary, and  volumetrically and velocity controlled to prevent re‐suspension of sediments in the  stormwater system;     2. Discharges from lawn watering and other irrigation runoff; however, these shall be  minimized through water conservation efforts;     3. De‐chlorinated spa or swimming pool discharges. The discharges shall be de‐ chlorinated to a total residual chlorine concentration of 0.1 ppm or less, pH‐adjusted  and re‐oxygenized if necessary, and volumetrically and velocity controlled to prevent  re‐suspension of sediments in the stormwater system. Discharges shall be thermally  controlled to prevent an increase in temperature of the receiving water. Swimming  pool cleaning wastewater and filter backwash shall not be discharged to the storm  drainage system;   Page 11 of 260 Ordinance No. _________  Page 3 of 5    4. Street and sidewalk wash water, water used to control dust, and routine external  building wash down that does not use detergents. The amount of street wash, dust  control, and building wash water shall be minimized. At active construction sites,  street sweeping must be performed prior to washing the street;     5. Dye testing with verbal notification to the City a minimum of 24 hours prior to the  time of the test.     6. Non‐stormwater discharges covered by another NPDES permit, waiver, or waste  discharge order issued to the discharger and administered under the authority of the  Environmental Protection Agency or Washington State Department of Ecology,  provided that the discharger is in full compliance with all requirements of the permit,  waiver, or order and other applicable laws and regulations; and provided, that  written approval has been granted for any discharge to the storm drain system;     7. Discharges resulting from maintenance, repair, or operation of firefighting  equipment and facilities that are not directly associated with public fire fighting,  including discharges from public fire fighting training exercises, unless City‐approved  best management practices are implemented.     8. Other non‐stormwater discharges shall be in compliance with the requirements of  a stormwater pollution prevention plan reviewed and approved by the City, which  addresses control of such discharges by applying AKART to prevent contaminants  from entering surface or ground water.    C. Allowable Discharges. The following types of discharges shall not be considered illicit  discharges for the purposes of this Chapter if they do not contain pollutants or unless  the Director determines that the type of discharge, whether singly or in combination  with others, is causing or is likely to cause pollution of surface water or groundwater.     1. Diverted stream flows, rising ground waters, uncontaminated ground water  infiltration (as defined in Title 40 of the Code of Federal Regulations: 40 CFR  35.2005(20)), uncontaminated pumped ground water, foundation drains, air  conditioning condensation, irrigation water from agricultural sources that is  commingled with urban stormwater, springs, water from crawl space pumps, footing  drains, flows from riparian habitats and wetlands, and discharges from emergency  fire fighting activities in accordance with “S2. Authorized Discharges,” of the City's  NPDES permit.     2. Discharges specified in writing by the City as being necessary to protect public  health and safety.   Page 12 of 260 Ordinance No. _________  Page 4 of 5    3. If a person can demonstrate that there are no additional pollutants being  discharged from the premises above the background conditions of the water entering  the site, that person shall not be in violation of subsection A of this section.     D. Prohibition of Illicit Connections.     1. The construction, use, maintenance or continued existence of illicit connections to  the storm drain system is prohibited. This prohibition expressly includes, without  limitation, illicit connections made in the past, regardless of whether the connection  was permissible under law or practices applicable or prevailing at the time of  connection.     2. Any connection identified by the Director that could convey anything not  composed entirely of surface and stormwater directly into municipal drainage  facilities is considered an illicit connection and is prohibited with the following  exceptions: connections conveying allowable discharges or connections conveying  discharges pursuant to an NPDES permit or a State Waste Discharge Permit.     3. Illicit connections must be disconnected and redirected, if warranted, to an  approved onsite wastewater management system or the sanitary sewer system upon  approval of the City.     4. Any drain or conveyance that has not been documented in plans, maps or  equivalent, and which is connected to the storm sewer system, shall be located by  the owner or occupant of that property upon receipt of written notice of violation  from the City requiring that such locating be completed. Such notice will specify a  reasonable time period within which the location of the drain or conveyance is to be  determined, that the drain or conveyance be identified as storm sewer, sanitary  sewer, or other, and that the outfall location or point of connection to the storm  sewer system, sanitary sewer system or other discharge point be identified. Results  of these investigations are to be documented and provided to the City.     E. Prohibition of Stormwater Discharge to Sanitary Sewer. Stormwater shall not be  discharged into the sanitary sewer without written permission to do so from the City  of Port Orchard.     F. Prohibition of Waste Disposal. No person shall throw, deposit, leave, maintain, or  keep in or upon any public or private property, the stormwater drainage system, or  waters of the state, any refuse, rubbish, garbage, litter, or other discarded or  abandoned objects, articles, or accumulations that may cause or contribute to  Page 13 of 260 Ordinance No. _________  Page 5 of 5  pollution. Wastes deposited in proper non‐leaking waste receptacles for the purposes  of collection are exempt from this prohibition.     SECTION 2.  Severability.  If any section, sentence, clause or phrase of this Ordinance  should be held to be unconstitutional or unlawful by a court of competent jurisdiction, such  invalidity or unconstitutionality shall not affect the validity or constitutionality of any other  section, sentence, clause or phrase of this Ordinance.      SECTION 3.  Publication.  This Ordinance shall be published by an approved summary  consisting of the title.     SECTION 4.  Effective Date.  This Ordinance shall take effect and be in full force and  effect five days after publication, as provided by law.        PASSED by the City Council of the City of Port Orchard, APPROVED by the Mayor and  attested by the Clerk in authentication of such passage this 27TH day of February 2018.                     Robert Putaansuu, Mayor    ATTEST:      SPONSOR:                     Brandy Rinearson, MMC, City Clerk Councilmember Ashby, Councilmember        APPROVED AS TO FORM:                  Sharon Cates, City Attorney    PUBLISHED:  EFFECTIVE DATE:    Page 14 of 260 City of Port Orchard 216 Prospect Street, Port Orchard, WA 98366 (360) 876-4407 • FAX (360) 895-9029 Agenda Staff Report Agenda Item No.: Consent Agenda 4C Meeting Date: February 27, 2018 Subject: Approval of a Contract with Kitsap County - Prepared by: Nicholas Bond Participation in the 2020 Census Local DCD Director Update of Census Address Operations Atty Routing No.: 113-17 (LUCA) Atty Review Date: 2/21/2018 Summary: In preparation for the 2020 Census, local governments have been invited by the US Census Bureau to participate in the Local Update of Census Address Operations (LUCA). The LUCA will review and provide corrections to the Census Bureau’s residential address list, which is used in conducting the national census. The review will be conducted in spring 2018. The City has registered to participate in the LUCA. According to the Census Bureau, the benefits of participating in the LUCA are: • Governments that participate in the LUCA help to ensure an accurate decennial census count for their communities. • An accurate count helps the federal government annually allocate more than $400 billion across 26 federal agencies for tribal, state, and local government programs and services. • Participating communities gain valuable information to help plan for their future needs. Given the staff time and training needed, and the very stringent security requirements for the handling of the Census Bureau’s data, it is more efficient for Kitsap County to perform the addressing review on the City’s behalf, rather than have the City undertake the task. The County will already have the necessary equipment and protocols in place and staff trained, as they will be performing their own addressing review, as well as the reviews of other local governments that may choose to contract with them. The County estimates a time commitment of 70-110 hours to perform the City’s LUCA review, at a rate of $93.25 per hour, for a maximum contract amount of $10,257.50. Relationship to Comprehensive Plan: N/A Recommendation: Staff recommends that the City Council approve the contract with Kitsap County to perform the LUCA review for the 2020 Census on the City’s behalf. Motion for consideration: “I move to approve the contract with Kitsap County to perform the LUCA review for the 2020 Census on the City’s behalf.” Fiscal Impact: Up to $10,257.50. Page 15 of 260 Consent Agenda 6B Page 2 of 2 Alternatives: Do not approve the contract and forgo participation in LUCA ; or, direct City staff to take appropriate measures to perform the LUCA review in -house. Attachments: Information Services Agreement for LUCA Operations and Memo from Code Enforcement Page 16 of 260 1 No. INFORMATION SERVICES AGREEMENT FOR LOCAL UPDATE OF CENSUS ADDRESS OPERATIONS (LUCA) This Information Services Agreement for Local Update of Census Address Operations (“Agreement”) is Agreement is made between Kitsap County (“County”) and the City of Port Orchard (“City”). In consideration of the mutual covenants contained herein, the parties agree as follows: Scope of Services by County. The County will provide to the City the services as follows:   Submit updates to LUCA on behalf of the City of Port Orchard conducting the review and response of the Census Bureau’s address list in accordance with the Census Bureau’s response requirements, training, protocols and security protocols. The services performed will not exceed the services listed above without the prior written agreement of the parties. Term. This Agreement shall commence upon execution by both parties and terminate on 12/31/2018. This Agreement may be extended for additional consecutive terms at the mutual agreement of the parties. Termination. Either party to this Agreement may terminate the Agreement on thirty (30) days’ written notice to the other party. Upon termination of this Agreement, any documents, reports and/or electronic data specifically prepared or produced for the City under this Agreement will be provided to the City within thirty (30) days of a written request from the City. Compensation. The maximum amount of compensation paid under this Agreement is $10,257.50, which will be paid at the hourly rate of $93.25. The County will advise the City as soon as possible if it appears that the number of hours required to complete the services under this Agreement will exceed 110 hours, and this Agreement will be amended accordingly. Billing and Payment. The County will submit a quarterly invoice to the City for the services completed to date. The City will pay all invoices within 30 days from the invoice date. Notices. All notices required to be in writing shall be delivered to a party by United States mail, postage prepaid, and addressed to the appropriate party as follows: County: Kitsap County, Department of Information Services 614 Division Street, MS-21 Port Orchard, WA 98366 Attn: Kitsap County IS Director Page 17 of 260 2 City: City of Port Orchard Department of Community Development 216 Prospect St. Port Orchard, WA 98366 Attn: Doug Price, Code Enforcement Officer Compliance with Legal Requirements. Each party shall comply with all applicable federal, state and local laws and regulations. Ownership of Work Product. Documents, reports and/or electronic data specifically prepared or produced for the City under this Agreement whether finished or not will become the property of the City. Independent Contractor. Each party under the Agreement shall be for all purposes an independent contractor. Nothing contained herein will be deemed to create an association, a partnership, a joint venture, or a relationship of principal and agent, or employer and employee between the parties. Indemnification and Limitation of Liability. Each party shall defend, indemnify, and hold harmless the other party, and the other party’s officers, employees, and agents, from and against any claims, including reasonable attorney fees resulting from such claims, by third parties for any or all injuries to persons, damage to property, disclosure of confidential information, or infringement of a protected intellectual property right of such third parties, which claim arises from intentional, reckless or negligent acts or omissions of the party its officers, employees, or agents. A party’s obligation to defend, indemnify, and hold harmless shall not be eliminated or reduced by any alleged concurrent negligence by the other party. The parties shall not be liable to each other, regardless of the form of action, for consequential, incidental, indirect, or special damages except a claim related to bodily injury or death, or a claim or demand based on disclosure of confidential information, data breach, or infringement of protectable intellectual property right interest. Neither party shall be liable to the other or be deemed to be in breach of this Agreement by reason of any delay in performing, or any failure to perform any of their respective obligations in relation to the Agreement, if the delay or failure was due to any cause beyond said party’s reasonable control including, but not limited to, any act of God, war, explosions, fire, flood, earthquake, epidemics, government or state action, unusually severe weather or other action of third parties out of the reasonable control of a party. Assignments. Except with the prior written consent of the other party, each party shall not assign or transfer, including by merger (whether that party is the surviving or disappearing entity), consolidation, dissolution, or operation of law any right, duty, obligation, or remedy under the Agreement. Any purported assignment or transfer in violation of this section shall be void. Page 18 of 260 3 Waiver. Either party’s failure to insist upon the strict performance of any provision of the Agreement, or to exercise any right based upon a breach thereof or the acceptance of any performance during such breach, will not constitute a waiver of any right or remedy under the Agreement unless expressly so agreed in writing by an authorized representative. Severability. If a court of competent jurisdiction holds any provision of the Agreement to be illegal, invalid, or unenforceable, in whole or in part, the validity of the remaining provisions will not be affected, and the parties’ rights and obligations will be construed and enforced as if the Agreement did not contain the particular provision held to be invalid. Survival. Those provisions of this Contract that by their sense and purpose should survive expiration or termination of the Contract shall so survive. Those provisions include, without limitation: Sections 5 (Compensation) and (Indemnification and Limitation of Liability). Entire Agreement. The parties acknowledge the Contract is the product of negotiation between the parties and represents the entire agreement of the parties with respect to its subject matter. All previous agreements, oral or written, are hereby revoked and superseded by the Contract. Authorization. Each party signing below warrants to the other party, that they have the full power and authority to execute this Agreement on behalf of the party for whom they sign. DATED this __ day of __________, 2018: KITSAP COUNTY, WASHINGTON Deborah A. Boe PROSECUTING ATTORNEY Tina R. Robinson DATED this __ day of ___________, 2018: CITY OF PORT ORCHARD, WASHINGTON Robert Putaansuu, Mayor ATTEST/AUTHENTICATED: Brandy Rinearson, MMC, City Clerk APPROVED AS TO FORM: Sharon Cates, City Attorney Page 19 of 260 Memo To: Nick Bond From: Doug Price Date: September 18, 2017 Re: 2020 Census - LUCA In preparation for the 2020 Census, there is a process called LUCA (Local Update of Census Address Operations) that local governments are invited (voluntary) to participate in. It’s an opportunity for local governments to review and provide corrections to the Census Bureau’s residential address list, which is used in conducting the census. According to the Census Bureau, the benefits of participating in LUCA are:  Governments that participate in the LUCA operation help ensure an accurate decennial census count for their communities.  An accurate count helps the federal government annually allocate more than $400 billion across 26 federal agencies for tribal, state, and local government programs and services.  To help your community plan for future needs. We don’t yet know exactly how the process works, as that information will be provided in training workshops that begin in October, but it will involve the use of GIS-related functions to review and update the list. Local governments may choose to do this function, themselves, or contract with a higher level of government to do so on their behalf. The deadline to register for LUCA is December 15, 2017. I have not been able to determine if Port Orchard participated in this process for the 2010 census, nor, if so, how it was done. Kitsap County does not have a record of having done it for us. County GIS estimates the time for them to do LUCA for local governments at 70-110 hours each, with smaller cities at the lower end, and would charge an hourly rate of $93.25 per hour. It is possible that we could do the LUCA review in-house (most likely me and Darren Podraza), but the time involved would likely be higher and there are very stringent security requirements for the handling of the Census Bureau’s data, including use of a network-isolated server or stand-alone computer in a locked room, with no network or offsite backup, encryption of files and passwords, restriction of data access to those who have signed a confidentiality agreement, retention of any paper copies or physical media in a locked room, and more. Please advise if I should register or decline participation in LUCA, if we will contract with Kitsap County for this service, or if you need additional information. City of Port Orchard Department of Community Development Page 20 of 260 City of Port Orchard 216 Prospect Street, Port Orchard, WA 98366 (360) 876-4407 • FAX (360) 895-9029 Agenda Staff Report Agenda Item No.: Business Item 7A Meeting Date: February 27, 2018 Subject: Adoption of an Ordinance Adopting a New Prepared by: Nicholas Bond, AICP POMC Chapter 20.127 Design Standards, DCD Director Repealing Ordinance No. 1479, and Amending Atty Routing No.: 115-17 Chapters 20.12 Definitions, 20.38 Overlay Atty Review Date: 2/13/18 Districts, and 20.100 Development Standards – Design Guidelines Summary: In 2016, the Mayor and City Council expressed concerns about the quality of some recent developments within the City and requested the Department of Community Development to begin working toward design standards for new and remodeled single-family and duplex residential development. In June 2017, the resulting design standards were adopted as Chapter 20.139 of Title 20 (Uni fied Land Use and Development Code) POMC, which became effective on September 1, 2017. For multi-family and commercial development, the City budgeted funds and selected a consultant, MAKERS Architecture and Urban Design, to assist in the creation of design standards for these types of development. A citizen review committee was also appointed to work with staff and MAKERS on the initial draft. The draft Design Standards were presented by MAKERS at a public open house in November 2017. A public hearing was held by the Planning Commission at its January and February 2018 meetings, and testimony was received from one person. The draft Design Standards were also provided in January 2018 to the citizen review committee for additional comments (none received). The draft Design Standards were then provided to City Council in February 2018 for an initial review. On February 6, 2018, the Planning Commission recommended that the City Council adopt the Design Standards as presented, subject to several corrections and revisions, including: • Map #3: Include Taylor Street as a “Landscape” street. • Map #5: Extend “Mixed” street designation to east side of movie theater on Mile Hill Rd. • Clarify review and permitting authority in several places in the document. • Revise parking location recommendations for “Marine” designation along the north side of Bay Street, so that parking is not encouraged to be at the rear of these buildings (i.e., along the waterfront). These changes were incorporated into the draft presented to the City Council at its February 20 work-study meeting. The design standards as prepared by Maker’s architecture also required changes to other code sections and ordinances to ensure internal consistency including: Page 21 of 260 Business Item 7A Page 2 of 2 • Repealing Ordinance 1479 concerning access from Port Orchard Blvd, an ordinance that included provisions that are included in the new design standards. • Amending Chapter 20.12 to add new definitions related to the new design standards. • Amending POMC Sections 20.38.200-230 concerning the Downtown Overlay District. • Repealing POMC Sections 20.38.600-633 concerning the Tremont Overlay District. • Amending POMC Sections 20.100 concerning the City’s existing Development Standards and Design Guidelines. Relationship to Comprehensive Plan: The proposed design standards are supported by numerous goals and policies which are listed in the “whereas” section of the adopting ordinance. Recommendation: Staff recommends that the City Council vote to approve an ordinance adopting the Design Standards, repealing ordinance 1479, and amending chapters of title 20 . Motion for consideration: “I move to adopt an ordinance adopting the Design Standards, repealing ordinance 1479, and amending multiple chapters within title 20 as presented.” Fiscal Impact: This proposal is not expected to impact the City’s budget. Alternatives: Direct staff and consultants to further revise the Design Standards; or, do not adopt the Design Standards. Attachments: Design Standards; Ordinance; User Introduction; Redline Changes to Existing Code Sections Page 22 of 260 ORDINANCE NO. __  ‐18              AN ORDINANCE OF THE CITY OF PORT ORCHARD, WASHINGTON, ADOPTING  CHAPTER 20.127 (DESIGN STANDARDS) OF THE PORT ORCHARD MUNICIPAL  CODE, REPEALING ORDINANCE 1479, AMENDING CHAPTER 20.12 (DEFINITIONS),  AMENDING SECTION 20.38 (OVERLAY DISTRICTS), AMENDING CHAPTER 20.100  (DEVELOPMENT STANDARDS – DESIGN GUIDELINES), AMENDING CHAPTER  20.124 (DEVELOPMENT STANDARDS – PARKING AND CIRCULATION),  AMENDING CHAPTER 20.128 (DEVELOPMENT STANDARDS ‐ LANDSCAPING);  PROVIDING FOR SEVERABILITY AND CORRECTIONS; AND ESTABLISHING AN  EFFECTIVE DATE.    WHEREAS, on June 13, 2017, the Port Orchard City Council adopted Ordinance 019‐ 17 establishing a new unified development code (Title 20 POMC); and    WHEREAS, on June 27, 2017, the Port Orchard City Council adopted Ordinance 022‐ 17 which created new Chapter 20.139 (Single‐Family Residential, Duplex and Residential  Fence Design Standards); and    WHEREAS, the City Council wishes to establish additional design standard  requirements that will apply to commercial, multifamily residential and mixed‐use  development; and    WHEREAS, City staff, in conjunction with consultants and a design standards  committee, have developed design standards for commercial, multifamily residential and  mixed‐use development, to be codified as Chapter 20.127 (Design Standards); and    WHEREAS, the adoption of Chapter 20.127 requires the repeal of a number of existing  code sections in Title 20 that address guidelines and standards for building and site design,  parking and landscaping; and    WHEREAS, on January 2, 2018, the City submitted to the Department of Commerce a  60‐day request for review of the proposed Chapter 20.127, pursuant to RCW 36.70A.106(1);  and    WHEREAS, on January 10, 2018, the Planning Commission held a duly‐noticed public  hearing on the proposed adoption of minor revisions and corrections to Title 20, and public  testimony was received, and the Planning Commission recommended approval of the  proposed adoption; and    WHEREAS, on January 12, 2018, the City’s SEPA official issued a determination of  non‐significance for the proposed Chapter 20.127, and there have been no appeals; and  Page 23 of 260 Ordinance No. __‐18    Page 2 of 16    WHEREAS, the design standards in Chapter 20.127 implement numerous  comprehensive plan goals and policies, including:    Policy LU‐3:  Update and establish building and site design standards that support an  attractive and functional built environment in all areas of the City.    Policy LU‐25: Incorporate the following principles in planning for commercial areas:   • Create lively and attractive places at a human scale.  • Support a mix of retail, office, and residential uses in multistory structures.  • Create transitions between commercial areas and surrounding residential  neighborhoods.  • Protect residential areas from excessive noise, exterior lighting, glare, visual  nuisances, and other conditions that detract from the quality of the living environment.  • Encourage multi‐modal transportation options, especially during peak traffic  periods.  • Promote an intensity and density of land uses sufficient to support effective  transit and pedestrian activity.  • Promote a street pattern that provides through connections, pedestrian and  vehicular access.  • Establish urban and architectural design standards that support an attractive and  functional pedestrian environment, such as block size limits and requiring street‐facing  windows and doors.  • Encourage pedestrian travel to and within commercial areas by providing:  • Safe and attractive walkways.  • Close groupings of land uses.  • Parking lot design that provides safe walking routes and pedestrian connections  between adjacent properties.  • Off‐street surface parking to the backs or sides of buildings to maximize  pedestrian access from the sidewalk(s).    Policy LU‐28: In conjunction with the proposed Centers strategy, enhance  downtown Port Orchard’s role as the center of the South Kitsap region, reflecting the  following principles in development standards and land use plans:   • Encourage land uses that support transit centers and promote pedestrian  activity.  • Promote a mix of uses, including retail, office, and housing.  • Encourage uses that will provide both daytime and evening activities.  • Support civic, cultural, and entertainment activities.  • Provide sufficient public open space and recreational opportunities.  Page 24 of 260 Ordinance No. __‐18    Page 3 of 16  • Enhance, and provide access to, the waterfront.  • Develop enhanced design guidelines and design review requirements that  promote attractive, pedestrian‐scale development and redevelopment within the City’s  historic downtown area.    Policy CN‐20: Adopt design standards for Gateways.    Policy CN‐24:  Create an aesthetically pleasing entryway to the City with the use of  high‐quality signs, artwork, and landscaping.    Policy HS‐19: Consider commercial building design standards that establish and  protect neighborhood character.    Policy TR‐81: Develop design guidelines and standards for street wise landscaping,  sidewalks, and maintenance within new developments.    Policy TR‐104:  Restore/create unique neighborhood aesthetics via formation of  distinctive streetscapes and traffic controlling devices.    Land Use Goal 7:  Encourage the development of active, vibrant, and attractive  destinations throughout the community.    Housing Goal 6:  Formulate and implement innovative development regulations and  design standards that maintain and strengthen neighborhood character.    Transportation Goal 18:  Provide aesthetically pleasing streets; now, therefore     THE CITY COUNCIL OF THE CITY OF PORT ORCHARD, WASHINGTON, DO ORDAIN AS  FOLLOWS:    SECTION 1.  The City Council adopts all of the “Whereas” sections of this ordinance as  findings in support of this ordinance.    SECTION 2.  New Chapter 20.127 Adopted.  The commercial, multifamily residential and  mixed‐use development regulations, to be codified as Chapter 20.127 POMC, attached as Exhibit  1 hereto and incorporated fully herein by this reference, is hereby adopted in its entirety.    SECTION 3.  Ordinance 1478 Repealed.  Ordinance 1478 (Designating Port Orchard  Boulevard as a Limited Access Road) is hereby repealed in its entirety.    Page 25 of 260 Ordinance No. __‐18    Page 4 of 16  SECTION 4.  POMC Chapter 20.12 Revised.  Chapter 20.12 (Definitions) of the Port  Orchard Municipal Code is hereby revised to include the following additional definitions:    “Articulation” shall mean the giving of emphasis to architectural elements (like windows,  balconies, entries, etc.) that create a complementary pattern or rhythm, dividing large buildings  into smaller identifiable pieces. See POMC 20.127.430 for articulation standards.    “Articulation interval” shall mean the measure of articulation, the distance before  architectural elements repeat. See POMC 20.127.430 for articulation standards.    “Blank wall” shall mean a wall (including building façades and retaining walls) over 10 feet  in height and with a horizontal length greater than 15 feet and which does not include a  transparent window or door.    “Block frontage” refers to the portion of a property that fronts onto a street or other  public right‐of‐way.  This includes the front yard and the building façade facing the street.    “Cornice” shall mean a horizontal molding projecting along the top of a wall or building.    “Departure” shall mean a provision allowing applicants to propose alternative means of  compliance with a specific standard on a voluntary basis provided they meet the “purpose” of  the standards. See POMC 20.127.060 for departure standards.    “Fenestration” shall mean the design, proportioning, and disposition of windows and  other exterior openings of a building.    “Front‐loaded” shall mean a dwelling unit with an attached private garage that faces a  public street or highway.      “Habitable floor” shall mean any floor used or able to be converted to use for living  purposes, which includes working, sleeping, eating, cooking, or recreation, or a combination  thereof. A floor useable only for storage or parking is not a habitable floor. An unfinished  basement or attic which could be finished and converted to habitable space must be counted as  a habitable floor.    “High visibility street corners” shall mean special sites identified in the community design  framework maps (see POMC 20.127.130 for the location of street corners that warrant the  special design standards set forth in POMC 20.127.250).     Page 26 of 260 Ordinance No. __‐18    Page 5 of 16  “Level I, II, or III Improvements” refer to different thresholds for site improvements,  building remodels, and additions that are used to determine the levels of compliance needed for  the design standards in Chapter 20.127 POMC. See POMC 20.127.020(2) for details.    “Modulation” shall mean stepping forward or backwards a portion of the façade as a  means to articulate or add visual interest to the façade.      “Pedestrian‐oriented space” shall mean a courtyard or plaza space of varying sizes  serving commercial or a mixture of uses that meets the criteria of POMC 20.127.350(4).    “Roofline” shall mean the highest edge of the roof or the top of a parapet, whichever  establishes the top line of the structure when viewed in a horizontal plane.    “Streetscape” shall mean the space between the buildings on either side of a street that  defines its character. The elements of a streetscape include block frontage, building façades,  landscaping (trees, yards, bushes, plantings, etc.), sidewalks, street paving, street furniture  (benches, kiosks, trash receptacles, fountains, etc.), signs, awnings, and street lighting.    “Storefront” shall mean the ground floor façade of a commercial use adjacent to a  sidewalk or internal walkway.    “Transom window” shall mean a window or series of windows placed above a beam  separating a door and/or storefront windows. Transom windows are often placed above a canopy  or marquee to admit extra daylight into a commercial space.    “Transparency” shall mean the degree to which rays of light may transmit through a  substance.  For storefronts and other ground level non‐residential uses, transparency also refers  to the ability to see through the window and into the building as clarified in POMC 20.127.140.     “Trellis” shall mean a frame supporting open latticework used as a screen or a support for  growing vines or plants.    “Vertical building modulation” shall mean a stepping back or projecting forward of the  vertical walls of a building face, within specified intervals of building width and depth, as a means  of breaking up the apparent bulk of a structure’s continuous exterior walls.    “Weather protection” shall mean a horizontal structure above pedestrian areas such as  sidewalks and building entries that blocks rain, snow, and sun.    Page 27 of 260 Ordinance No. __‐18    Page 6 of 16  SECTION 5.  POMC Sections 20.38.200‐.230 Revised.  Sections 20.38.200 through  20.38.230 (Downtown Overlay District) of the Port Orchard Municipal Code are hereby revised  to read as follows:    20.38.200 Downtown overlay district (map designation ‐dod).   (1) Boundaries. The DOD consists of three subareas: the central DOD subarea, DOD west  gateway subarea, and DOD east gateway subarea shall consist of all real property located within  the area depicted on the comprehensive plan DOD map.   (2) Purposes. The purposes of the DOD are to:  (a) Implement the land use goals and policies set forth in the comprehensive plan.  (b) Provide for the development of an integrated mixed use downtown district that  contains office, service, retail, residential and recreational uses within close proximity to one  another.  (c) Maintain view corridors.  (d) Identify significant environmental impacts and ensure appropriate mitigation with  attention to sustainable or low‐impact development.  (e) Encourage environmentally sustainable development.  (f) Promote economic development and job creation in the city. (g) Encourage the  development of buildings with ground floor retail with office uses and residential uses above.  (h) Promote a walkable community by encouraging the development of public open  spaces, waterfront access, and pedestrian‐friendly walkways.  (l) Locate and combine parking areas in order to minimize the number of points of access  to and from Bay Street.  (n) Promote greater public transportation availability within Port Orchard and across  Sinclair Inlet during the evening hours to improve access to/from the DOD.     20.38.201 DOD – Permitted uses.   All uses listed below are permitted uses. No other uses shall be permitted in the central  DOD, unless said use is accessory to the principal permitted use or uses. Uses within the east and  west “gateways” may include uses allowed within the underlying zone or any of the central DOD  uses.    (1) On lots that do not abut Bay Street the following are permitted uses:  (a) Single‐family attached dwellings.  (b) Multifamily dwellings above the first floor, including but not limited to condominiums.  (c) Amusement/entertainment including but not limited to theaters, bowling,  amusement arcades; but excluding adult entertainment.  (d) Barbers and beauticians.  (e) Bed and breakfasts.  (f) Boat dealers; provided no inventory shall be allowed on site.  Page 28 of 260 Ordinance No. __‐18    Page 7 of 16  (g) Conference centers.  (h) Daycare.  (i) Dock.  (j) Commercial recreation.  (k) General business services.  (l) Health services, including offices, patient clinics, and medical/dental laboratories.  (m) Hotels and motels.  (n) Library.  (o) Liquor and wine stores.  (p) Marinas and marine supply.  (q) Museums.  (r) Parks.  (s) Parking lots and parking structures.  (t) Post office.  (u) Professional offices and services, including financial, accounting, and legal.  (v) Public agency offices.  (w) Retail sales and services listed as permitted uses in a commercial or mixed use zones,  except for motor vehicle dealers, auto supply stores, gas stations, boat dealers, adult  entertainment, and fuel dealers.  (x) Trails.  (y) Water transportation facilities.  (z) Medical marijuana cooperatives as permitted in this chapter.    (2) On lots that abut Bay Street the following are permitted uses:  (a) Single‐family attached dwellings above the first floor.  (b) Multifamily dwellings above the first floor, including but not limited to condominiums.  (c) Amusement/entertainment including but not limited to theaters, bowling,  amusement arcades; but excluding adult entertainment.  (d) Barbers and beauticians.  (e) Bed and breakfasts above the first floor.  (f) Boat dealers; provided no inventory shall be allowed on site.  (g) Conference centers.  (h) Daycare above the first floor.  (i) Dock.  (j) Commercial recreation.  (k) General business services, except bail bonds and similar uses under SIC Code 7389 are  prohibited from the ground floor and must be located above the ground floor.  (l) Health services, including offices, patient clinics, and medical/dental laboratories  above the first floor.  Page 29 of 260 Ordinance No. __‐18    Page 8 of 16  (m) Hotels and motels.  (n) Library.  (o) Liquor and wine stores.  (p) Marinas and marine supply.  (q) Museums.  (r) Parks.  (s) Parking lots and parking structures.  (t) Post office.  (u) Professional offices and services, including but not limited to financial, accounting, and  legal as follows:  (i) Between Frederick Ave and Harrison Ave: Permitted above the first floor.  (ii) On lots located west of Frederick Ave and East of Harrison Ave: Permitted.  (v) Public agency offices above the first floor.  (w) Retail sales and services listed as permitted uses in a commercial or mixed use zone,  except for motor vehicle dealers, auto supply stores, gas stations, boat dealers, adult  entertainment, and fuel dealers.  (x) Trails.  (y) Water transportation facilities.  (z) Tattoo parlors shall only be allowed on or above the second floor.  (aa) Medical marijuana cooperatives as permitted in this Title.     20.38.203 DOD – Conditional uses.   Uses that require a conditional use permit:  (1) Any retail store or complex of retail stores with more than 40,000 square feet of total  combined floor area that is otherwise allowed as a permitted use;     20.38.204 DOD – Conditional uses, decision criteria.   Applicable standards for granting a conditional use permit are as follows:   (1) Meets the criteria set forth in Chapter 20.50 POMC;     20.38.205 DOD – Lot area.   No minimum lot size is required within the central DOD area.     20.38.206 DOD – Lot coverage.   Development shall comply with the maximum land coverage requirements for the  underlying zone, as set forth in Subtitle VI of this Title; provided, there is no maximum lot  coverage for development on either side of Bay Street between Harrison Avenue and Orchard  Avenue.     20.38.207 DOD – Minimum setback requirements.   Page 30 of 260 Ordinance No. __‐18    Page 9 of 16  (1) Except as otherwise required by the shoreline master program and critical areas  ordinance, as now or hereafter amended, there is no minimum setback from a property line that  does not abut a street right‐of‐way or alley.   (2) There is no minimum setback from a property line that abuts a street right‐of‐way  provided there is a 10‐foot‐wide pedestrian walkway. If there is inadequate right‐of‐way to  establish a 10‐foot‐wide pedestrian walkway, then the building shall be set back a sufficient  distance to accommodate a 10‐foot‐wide pedestrian walkway.   (3) The setback from a property line that abuts an alley shall comply with the  requirements for the underlying zone as set forth in Subtitle VI.     20.38.208 DOD – Structure and measurements.   (1) For purposes of the DOD, structure and building height shall include: Roof forms and  decorative elements not intended for occupancy; mechanical penthouses and elevator overruns  and machine rooms; parapets; and all other roof structures.  (2) Where existing grade and finished grade are different, the lower of either existing  grade or finished grade shall be used to calculate vertical height. For those lots that are between  Bay Street and Prospect Street/Alley and currently abut Bay Street, the existing Bay Street  elevation shall be the basis for measuring structure height.  (3) For those lots within the DOD abutting Bay Street, the Bay Street elevation shall be  the basis for measuring building height.  (4) For those properties in the DOD gateway abutting Bethel Avenue, Bethel Avenue shall  be the basis for measuring building height.     20.38.209 DOD – Allowable building heights.  Building heights may vary based on location of parcel within the DOD and by the  opportunity to achieve a higher structure if certain amenities are incorporated into the  development design.     20.38.210 DOD – Heights within the central DOD and DOD east and west gateways on the north  side of Bay Street.                                                            The maximum allowable building height limit shall be 27 feet, which may be increased up  to 39 feet when the applicant provides water access and/or views amenities or other special  amenities in accordance with POMC 20.38.214.    20.38.211 DOD – Heights within the central DOD and DOD east and west gateways south of Bay  Street.   For lots that are between Bay Street and Prospect Street/Alley and abut Bay Street, the  maximum allowable building height limit shall be 39 feet, which may be increased up to 55 feet  when the applicant: provides water access and/or views amenities or other special amenities  in  accordance with POMC 20.38.214.   Page 31 of 260 Ordinance No. __‐18    Page 10 of 16    20.38.212 DOD – Heights for lots that do not abut Bay Street.   The maximum allowable building height limit shall be 27 feet, which may be increased up  to 39 feet when the applicant:  provides water access and/or views amenities or other special  amenities in accordance with POMC 20.38.214.     20.38.213 DOD – Gateways heights for those lots abutting Bethel Avenue.   The maximum allowed building height limit shall be 39 feet, which may be increased up  to 55 feet when the applicant provides water access and/or views amenities or other special  amenities in accordance with POMC 20.38.214.     20.38.214 DOD – Amenities for maximum building and structure height.   Maximum building heights may be increased in accordance with POMC 20.38.210 to  20.38.213 when water access and/or views amenities or other special amenities are provided as  prescribed in this section.  The amenities listed below may not be suitable for all sites and may  require additional city and state approvals (i.e shoreline permits).  Height bonuses will not be  approved in the absence of required permits when applicable.  The amenities listed below are  weighted using a point system.  In order for a height increase to be granted pursuant to POMC  20.38.210 to 20.38.213, an applicant shall provide amenities worth at least 3 points from the  following list:    (1) Construct a public water access corridor and sidewalk through the site or along the site’s  edge where no such access preexists.  The sidewalk shall be a minimum of 12‐feet in width  with public access provided in an easement or through another legal instrument. (2  points).  (2) For Waterfront Development, construct a water viewing platform at the water’s edge  measuring at least 400 square feet. (2 points)  (3) For Waterfront development. Construction of 14‐foot paved pedestrian pathway along  the entire waterfront in a 20‐foot easement. (1‐point per 100 lineal feet of pathway  constructed.  For properties less than 100 linear feet in width, 1 point shall be awarded  for a pathway that spans the property.)  (4) Construct a water feature. (1 point)  (5) For waterfront development, a harbor access opportunity by means of public access to a  pier constructed in a manner consistent with the city’s shoreline master program and  connected by a minimum five‐foot‐wide public pathway to the frontage street. A  minimum of 10 feet of open water on each side shall surround the pier. (2 points)  (6) For waterfront development, a harbor access opportunity by means of public access to a  small boat landing available for transient use by rowboats, canoes, dinghies, kayaks, etc.,  constructed in a manner consistent with the city’s shoreline master program and  connected by a minimum five‐foot‐wide public pathway to the frontage street. A  Page 32 of 260 Ordinance No. __‐18    Page 11 of 16  minimum of 10 feet of open water on each side shall surround the small boat landing. (1  point)  (7) Construct an enclosed plaza (such as an atrium or galleria) consisting of a publicly  accessible continuous open space located within a building and covered to provide  overhead weather protection while admitting natural daylight and which meets the  following design standards:  a. The space has a dimension ratio of not more than 5:1 (length: width);  b. Seating is provided at one seat for each 100 square feet of public space;  c. At least five percent of the area must be landscaped;  d. Must be accessible to the public at least during normal business hours;  e. Must be signed (interior and exterior) to identify the enclosed plaza is available  for public use; and  f. Must be visible from the building’s primary public entrance. (1 point)  (8) Public Restroom. A room or rooms containing toilets and lavatories for the use of the  general public, with only limited control for purposes of personal safety and which are:  a. Accessible to the public at least during normal business hours;  b. ADA Accessible;  c. Signed for Public Use;  d. Not Otherwise required by law. (1 Point)    20.38.215 DOD – Parking requirements.   The general parking standards set forth in Chapter 20.124 POMC shall apply unless a more  specific provision is set forth in the DOD specific parking standards in Subtitle VI.     20.38.221 DOD – Covered walkway.   All development within the central DOD either fronting Bay Street or fronting Sidney  Avenue north of Bay Street shall meet the following additional standard:  (1) Existing City‐Owned Covered Walkway. With respect to property where there is an  existing city‐owned covered walkway, a property owner who is constructing a new building shall  either replace the existing city‐owned covered walkway with an identical structure or propose an  alternative form of weather protection such as a canopy, second floor exterior deck, or similar  protective structure that extends not less than five feet over the sidewalk. The building owner  shall be responsible for maintaining and repairing any such alternative structure in an attractive  manner for the life of the building. Vinyl or soft plastic canopies shall not be allowed. In addition,  a performance bond shall be required in an amount to be determined by the city engineer to  assure that the existing city‐owned covered walkway on the adjacent properties is not damaged  and the new structure is built as designed and approved.  (2) No Existing City‐Owned Covered Walkway. With respect to property where there is no  existing city‐owned covered walkway, at least 50 percent of the building frontage on either the  Bay Street or Sidney Avenue side of the building located north of Bay Street shall include weather  Page 33 of 260 Ordinance No. __‐18    Page 12 of 16  protection in the form of a canopy, second floor exterior deck, or similar protective structure that  extends not less than five feet over the sidewalk. The building owner shall be responsible for  maintaining and repairing any such alternative structure in an attractive manner for the life of  the building. Vinyl or soft plastic canopies shall not be allowed.     20.38.223 DOD – Landscaping requirements.   The general landscape standards set forth in this Title shall apply unless a more restrictive  provision is set forth in the DOD specific landscape standards.    20.38.224 DOD – Pedestrian walkway requirements.   Pedestrian walkways within the central DOD shall meet the following requirements:  (1) If the subject property is adjacent to a street, it shall provide a pedestrian walkway  that shall be constructed of concrete or unit pavers, a minimum of 10 feet in width as measured  from the face of the street curb to the face of the structure, and shall extend the entire frontage  of the property adjacent to a street. If the pedestrian walkway cannot be accommodated within  existing public right‐of‐way, the difference shall be made up with a public easement over private  property or right of way dedication. Buildings may cantilever over the pedestrian walkways  provided the building extension does not overpower the pedestrian space or create a tunnel,  cave or similarly confined spatial effect.  Additional city approvals may be required to allow a  building to project into the right of way.    SECTION 6.  POMC Sections 20.38.600‐.633 Repealed.  Sections 20.38.600 through  20.38.633 (Tremont Street Corridor Overlay District) of the Port Orchard Municipal Code are  hereby repealed in their entirety.    SECTION 7. POMC Sections 20.124.200 ‐ .240 Repealed.  Sections 20.124.200 through  20.124.240 (Development Standards – Parking and Circulation) of the Port Orchard Municipal  Code are hereby repealed in their entirety.    SECTION 8. POMC Sections 20.128.230 ‐ .239 Repealed.  Sections 20.128.230 through  20.128.239 (Development Standards – Landscaping) of the Port Orchard Municipal Code are  hereby repealed in their entirety.    SECTION 9.  POMC Chapter 20.100 Revised.  POMC Chapter 20.100 of the Port Orchard  Municipal Code is hereby revised to read as follows:    Chapter 20.100  DEVELOPMENT STANDARDS – DESIGN GUIDELINES    Sections:  Page 34 of 260 Ordinance No. __‐18    Page 13 of 16  20.100.010    Purpose.  20.100.020    Block and lot layouts.  20.100.030    Roadway elements.    20.100.010 Purpose.  (1) The purpose of this section is to ensure that developments are compact, pedestrian‐ friendly, provide necessary infrastructure and services, and contribute to the character of the  town and surrounding neighborhoods,  by providing building and site design standards that:  (a) Reduce the visual impact of large residential buildings from adjacent streets and  properties;  (b) Enhance the aesthetic character of large residential buildings;  (c) Contain sufficient flexibility of standards to encourage creative and innovative site and  building design;  (d) Meet the on‐site recreation needs of project residents;  (e) Enhance aesthetics and environmental protection through site design; and  (f) Allow for continued or adaptive re‐use of historic resources while preserving their  historic and architectural integrity.  (2) These guidelines do not alter the land uses or densities allowed in the underlying  zoning districts defined in this code. Projects shall comply with all relevant criteria set forth in  this chapter.     20.100.020 Block and lot layouts.  (1) Blocks should have sufficient width to provide for a maximum of two tiers of lots of  appropriate depths. Exceptions should be permitted in blocks adjacent to major streets,  railroads, waterways, or involving unique site conditions that make this requirement impractical.  (2) Lots to be created within a proposed site plan or subdivision should comply with the  following requirements:   (a) Every lot should have a minimum frontage of 25 feet on a public or privately dedicated  right‐of‐way. A repair and maintenance access should be provided to all lots by site plan or plat  easement and property deed. Required easements shall be shown on the face of the site plan or  plat.  (b) Lot lines should be at right angles to street lines or radial to curvilinear streets unless  a variation will result in a better street or lot plan.  (c) Dimensions of corner lots should be large enough to allow for front yard setbacks off  both streets.  (d) Corner lots should be graded to provide sufficient sight clearance at intersections.     20.100.030 Roadway elements.  (1) Right‐of‐Way Dedications.   Page 35 of 260 Ordinance No. __‐18    Page 14 of 16  (a) All site plans and subdivisions should provide direct access to at least one existing  improved and publicly dedicated street.  (b) When a proposed site plan or subdivision is abutting an existing street or streets with  a right‐of‐way of lesser width than specified by city code, the applicant may be required as a  condition of approval to deed additional right‐of‐way width and to improve said right‐of‐way to  the design specifications of the city engineer. The city may require dedication of right‐of‐way in  excess of standards in the following cases:  (i) Where additional width is necessary to maintain continuity with the adjoining rights‐ of‐way; and   (ii) Where additional width is necessary to maintain alignment with adjoining streets and  sidewalks improvements or to allow for provision of sidewalks or bicycle facilities.  (iii) Dead‐end streets shall be used on access streets only and shall terminate in a cul‐de‐ sac. Streets which dead‐end and which would normally be continued if the adjacent property  were developed should be shown as temporary turnarounds. The land beyond the normal right‐ of‐way for such streets shall revert to the abutting property owners when the street is continued.  (c) Half‐streets shall not be allowed.  (2) Street Layouts.  (a) The street within and adjacent to a site plan or subdivision should be classified and  designed to comply with the road standards as adopted by city resolution or ordinance,  comprehensive plan and major street map of the city. Major streets should refer to designated  arterial and collector streets and minor streets should refer to access streets and cul‐de‐sacs.  (b) Proposed streets should extend to the boundary lines of the proposed site plan or  subdivision in order to provide for the future development of adjacent tracts unless prevented  by natural or manmade conditions or unless such extension is determined to be unnecessary or  undesirable by the planning commission or city council.  (c) The street pattern for commercial site plans and subdivisions should be designed to  expedite traffic movement, reduce conflicts between various types of land uses including  pedestrian and bicycle access, and coordinate the location of proposed buildings with vehicular  loading and parking facilities. To the extent practical and feasible, commercial site plans should  provide common driveways and integral access through or between the property and adjacent  properties and surrounding residential neighborhoods.  (d) The street pattern for industrial site plans and subdivisions should be designed to  expedite traffic movement, reduce conflicts between various types of land uses including  pedestrian access, and coordinate the location of proposed buildings with airport, railroad,  waterfront, and vehicular loading and parking facilities.  (3) Street Signage. Public street names shall conform to the city of Port Orchard system.  Street signs shall be installed as designated by the city engineer before final site plan or plat  approval.     Page 36 of 260 Ordinance No. __‐18    Page 15 of 16    SECTION 10.  Severability.  If any section, sentence, clause or phrase of this ordinance  should be held to be invalid or unconstitutional by a court of competent jurisdiction, such  invalidity or unconstitutionality shall not affect the validity of constitutionality of any other  section, sentence, clause or phrase of this ordinance.    SECTION 11.  Corrections.  Upon the approval of the city attorney, the city clerk and/or  code publisher is authorized to make any necessary technical corrections to this ordinance,  including but not limited to the correction of scrivener’s/clerical errors, references, ordinance  numbering, section/subsection numbers, and any reference thereto.    SECTION 12.  Effective Date.  This ordinance shall be published in the official newspaper  of the city and shall take full force and effect on April 1, 2018.  A summary of this ordinance in  the form of the ordinance title may be published in lieu of publishing the ordinance in its entirety.     PASSED by the City Council of the City of Port Orchard, APPROVED by the Mayor and attested  by the City Clerk in authentication of such passage this 27th day of February 2018.                               Robert Putaansuu, Mayor    ATTEST:            SPONSOR:                              Brandy Rinearson, MMC, City Clerk     Bek Ashby, Councilmember    APPROVED AS TO FORM:                       Sharon Cates, City Attorney           PUBLISHED:    EFFECTIVE DATE:                  Page 37 of 260 Ordinance No. __‐18    Page 16 of 16      ATTACHED:  EXHIBIT 1  (CHAPTER 20.127, DESIGN STANDARDS)  Page 38 of 260 ORDINANCE NO. ____  ‐ EXHIBIT 1    CHAPTER 20.127  DESIGN STANDARDS    ARTICLE I INTRODUCTION  20.127.010 Purpose.  20.127.020 Applicability and compliance.  20.127.030 Optional design review board project recommendation.  20.127.040 Supplemental submittal requirements.  20.127.050 Pre‐submittal design review.  20.127.060 Departures.    ARTICLE II BLOCK FRONTAGE STANDARDS    20.127.100 Purpose.  20.127.110 Applicability and compliance.  20.127.120 How to use this chapter.  20.127.130 Community design framework maps.  20.127.140 About the transparency standards.  20.127.150 Storefront block frontage standards.  20.127.160 Landscaped block frontage standards  20.127.170 Varied block frontage standards.  20.127.180 Marine block frontage standards.  20.127.190 Gateway block frontage standards.  20.127.200 Internal roadway storefront frontage standards.  20.127.210 Other block frontage standards.  20.127.220 Trail/Park frontage standards.  20.127.230 Special residential frontage standards along sidewalks and internal walkways.  20.127.240 Where a property fronts onto multiple streets/frontage designations.  20.127.250 High visibility street corners.  20.127.260 Community design framework master plan.    ARTICLE III SITE PLANNING STANDARDS    20.127.300 Purpose.  20.127.310 Applicability and compliance.  20.127.320 Relationship to adjacent properties.  Page 39 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 2 of 111   20.127.330 Non‐motorized circulation and design.  20.127.340 Vehicular circulation and parking.  20.127.350 On‐site open space.  20.127.360 Location and design of service areas and mechanical equipment.    ARTICLE IV BUILDING DESIGN STANDARDS    20.127.400 Purpose.  20.127.410 Applicability and compliance.  20.127.420 Building character.  20.127.430 Building massing and articulation.  20.127.440 Building details.  20.127.450 Building materials.  20.127.460 Blank wall treatments     Page 40 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 3 of 111   CHAPTER 20.127 Article I - INTRODUCTION 20.127.010 - Purpose. This chapter implements the Port Orchard Comprehensive Plan. Overall, the purpose of this chapter is to: (1) Provide clear objectives for those embarking on the planning and design of development projects in Port Orchard. (2) Preserve and protect the public health, safety, and welfare of the citizens of Port Orchard. (3) Ensure that new commercial and multi-household development is of high quality and beneficially contributes to Port Orchard’s character. (4) Upgrade the visual appearance of Port Orchard’s principal vehicular corridors. (5) Ensure that new developments within existing neighborhoods are compatible with, and enhance the character of, Port Orchard’s neighborhoods. (6) Promote an increase in walking and bicycling throughout the city. (7) Enhance the livability of Port Orchard’s residential developments. (8) Maintain and enhance property values within Port Orchard.   Page 41 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 4 of 111   20.127.020 - Applicability and compliance. (1) Applicability. The provisions of this chapter apply to all development within Port Orchard, except: (a) Detached single-family and two-family(duplex) dwellings in any configuration. Single Family and Duplex Design Standards are found in Chapter 20.139 POMC. (b) Properties within the designated Old Clifton Industrial Park. See the figure below for a map clarifying the location of properties which are exempt.   Figure 20.127.020(1) Old Clifton Industrial Park   (c) The director may waive these provisions in other Employment – Industrial/Office zoned properties where they are screened from view from the public right of way and adjacent non Employment – Industrial/Office properties by a minimum 20-foot wide landscaped buffer meeting the requirements of Table 20.128.296 for Urban Buffers – Full Screening or by preservation of comparable existing landscaping on the site. (2) Relationship to other codes and documents. Where provisions of this chapter conflict with provisions in any other section of the Port Orchard Design Standards, this chapter prevails unless otherwise noted herein. Page 42 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 5 of 111   (3) For building additions, remodels, and site improvements, three different thresholds have been established to gauge how the design standards in this chapter are applied to such projects. See Figure 20.127.020(3) below for examples of site development and the respective types of improvements required under each of the three levels of improvements. (a) Level I Improvements include all exterior remodels, building additions, and/or site improvements that affect the exterior appearance of the building/site or cumulatively increase the gross floor area by up to 20 percent of the gross square footage that existed three years prior to the date of permit issuance. The requirement for such improvements is only that the proposed improvements meet the standards and do not lead to further nonconformance with the standards. For example, if a property owner decides to replace a building façade’s siding, then the siding must meet the applicable exterior building material standards, but elements such as building articulation (see POMC 20.127.430) would not be required. (b) Level II Improvements include all improvements that cumulatively increase the gross floor area by 20 percent or more, but not greater than 75 percent, of the gross square footage that existed three years prior to the date of permit issuance. All standards that do not relate to repositioning the building or reconfiguring site development apply to Level II Improvements. For example, if a property owner of an existing home in the BP Zone wants to convert the home to an office and build an addition equaling 45 percent of the current building’s area, then the following elements would apply: (i) The location and design of the addition/remodel must be consistent with the block frontage standards (see Article II of this chapter), to the extent possible given the location of the existing building. For such developments seeking additions to buildings where an off-street parking location currently does not comply with applicable parking location standards, building additions are allowed provided they do not increase any current non-conformity and generally bring the project closer into conformance with the standards. See Figure 20.127.020(3) for an example of this. (ii) Comply with applicable site planning and design elements (see Article III of this chapter). (iii) Comply with all building design provisions of Article IV of this chapter, except architectural scale and materials provisions related to the existing portion of the building where no exterior changes are proposed. The entire building must comply with building elements/details, materials, and blank wall treatment standards of POMC 20.127.450. (iv) The proposed improvements shall comply with the off-street parking, landscaping, and signage provisions of Chapters 20.124, 20.128, and 20.132 POMC. (c) Level III Improvements include all improvements that cumulatively increase the gross floor area by more than 75 percent of the gross square footage that existed three years prior to the date of permit issuance. Such developments must conform to ALL applicable standards.    Page 43 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 6 of 111     Figure 20.127.020(3) Examples of improvement types and required compliance.   Page 44 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 7 of 111   (4) Review for compliance. Proposals for development, including design standard departure requests, shall be reviewed for consistency with the design standards as found in this chapter in conjunction with every underlying permit application(s) (i.e. building permit, stormwater drainage permit, conditional use permit, binding site plan, etc.) at each stage of the development. The city recognizes that every project is unique and that permits are not always submitted in a single package simultaneously. For instance, a project may require a conditional use permit, building permit, land disturbing activity permit, and stormwater drainage permit. It is common that a building permit application be submitted after site development activities have begun. It is also common to develop building pads for future construction as part of an approved development. 20.127.030 - Optional Design Review Board project recommendation. Applicants for development subject to the design standards contained in this chapter may optionally request that the city’s Design Review Board provide project review and a recommendation on the application. When requested by the applicant, the Design Review Board shall review permit applications for consistency with this chapter and make a recommendation to the director or hearing examiner, as appropriate to the permit type, who shall give substantial weight to the recommendation of the Design Review Board as long as that recommendation does not conflict with the provisions of this chapter and is consistent with its purposes. Requests for optional Design Review Board project recommendations shall be made at the time of permit application submittal. 20.127.040 - Supplemental submittal requirements. A pre-application meeting is strongly recommended to determine which of the below listed supplemental application materials are needed for a specific development in order to determine compliance with the design standards. Applications subject to review under this chapter may be deemed incomplete if they are missing any of the following materials, as needed to determine compliance with the design standards: (1) Block frontage standards. (a) Identification of the block frontage type(s) applicable to the development. (b) A site plan and/or other plans illustrating proposed improvements and how the block frontage standards are being met, including (where applicable): (i) Building envelope location and setbacks/dimensions. (ii) Site elevation/topography at minimum two-foot intervals. (iii) Parking location and vehicular access design. (iv) Percentage of street frontage that is occupied by parking areas and garage entries. (v) Weather protection elements and dimensions/percentages. (vi) Façade transparency elements and dimensions/percentages. (vii) Storefront interior dimensions, including floor to ceiling height and storefront depth. (viii) Landscaping elements (common or scientific name and size) and design (layout and location). Page 45 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 8 of 111   (ix) Right-of-way improvements and dimensions (including planting strip and sidewalk). (x) Undeveloped areas, including critical areas and associated buffers). (2) Site planning standards. A site plan and/or other plans illustrating proposed improvements and how the site planning standards are being met, including (where applicable): (a) Building envelope location and setbacks/dimensions. (b) Site elevation/topography at minimum two-foot intervals. (c) Building elevations of all façades, including the location of doors, windows, and balconies. (d) The location and height of adjacent structures within 25 feet of the property proposed for development. (e) Non-motorized circulation elements, including materials, dimensions, and necessary details. (f) Parking location and vehicular access design, including materials, curb edge, lane configurations, dimensions, and other relevant details to support compliance. (g) Existing and proposed pedestrian-oriented space, usable residential open space, and other recreational features, including design elements, materials, and necessary details. (h) Location, design, and configuration of service areas and mechanical equipment. (i) Landscaping elements (common or scientific name and size) and design (layout and location). (j) Right-of-way improvements and dimensions (including planting strip and sidewalk). (3) Building design standards. Graphics illustrating proposed improvements and how the building design standards are being met, including (where applicable): (a) Building elevations showing: (i) Exterior materials. (ii) Doors and windows and associated design details. (iii) Roofline design and dimensions. (iv) Details on proposed exterior materials and finish. (v) Blank wall treatment details. (b) Building plan view drawings showing: (i) Façade articulation and dimensions. (ii) Entry locations and design. (c) Three dimensional graphics emphasizing: (i) Building massing and articulation. (ii) How the development (proposed improvements) fit within the surrounding context. The graphic must illustrate the general massing of buildings within 50 feet of the site. (4) Departures. If any departures are requested, such elements must be clearly identified in the above materials. Documentation to support how such proposed departures meet the applicable approval criteria must be included. Page 46 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 9 of 111   20.127.050 - Pre-submittal design review. (1) It is the city’s intent to offer a pre-submittal design review process to allow applicants to vet their building and site designs prior to completing full architectural and engineering construction plans required for technical plan review and permit application submittal. Applicants seeking pre-submittal design review may request that a preliminary review of conceptual site and/or building plans be conducted by the director o evaluate consistency with the design standards found in this chapter. (2) Anyone seeking pre-submittal design review shall: (a) Complete an application form. (b)Pay the appropriate fee as set by resolution. s (b) Submit conceptual plans along with the materials listed in POMC 20.127.040 to the Department of Community Development. (3) The directorshall review the request for pre-submittal design review and provide a pre-submittal design review letter and/or marked up plans describing which portions of the conceptual design meet and do not meet the design standards (4) Any letter and/or marked up plans generated in a pre-submittal design review shall not be considered a final decision and are only intended to assist an applicant in the preparation of complete application materials. 20.127.060 - Departures. (1) Overview and purpose. This chapter provides for a number of specific departure opportunities to development standards. For brevity in tables, departure opportunities are noted with the  symbol. The purpose of this section is to provide applicants with the option of proposing alternative design treatments, provided such departures meet the “purpose” of the particular standard and any additional departure criteria set forth for the particular departure opportunity. (2) Departures are voluntary. This provision allows the flexibility for applicants to propose alternative designs on a voluntary basis as provided herein. (3) Variances versus departures. Variances, as set forth in Chapter 20.28 POMC, require conditions in place on the property, not created by the property owner, that create practical difficulties or unnecessary hardships in complying with the applicable development regulations. Such conditions are not necessary in order to qualify for departures, which can be proposed as an alternative to complying with specific design standards in this chapter provided they comply with approval criteria listed in subsection (6) of this section. (4) Applicability. Departure opportunities are available only to those specific standards that allow for departures. (5) Review procedures. Departure requests are to be reviewed in conjunction with the underlying development permit and processed as set forth in POMC 20.127.020(1) and Chapters 20.22, 20.24, 20.25 POMC. (6) Approval criteria. Project applicants must successfully demonstrate to the reviewing authority (the director or hearing examiner, as appropriate to the permit type) how the proposed departure meets the purpose(s) of the standard and other applicable departure criteria that apply to the specific standard. Page 47 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 10 of 111   (7) Documentation. For each departure approved, the reviewing authority must make findings that document the manner in which the departure satisfies the approval criteria in subsection (6) above. The findings are to be maintained with project application records for the purpose of providing consistency in decision-making by the city. Page 48 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 11 of 111   Article II - BLOCK FRONTAGE STANDARDS 20.127.100 - Purpose. (1) To provide standards to implement the Comprehensive Plan and applicable adopted sub-area plans. (2) To design sites and orient buildings with an emphasis on compatible development and creating a comfortable walking environment. (3) To provide standards that recognize the need for a system of streets and block frontages. 20.127.110 - Applicability and compliance. The provisions of this Article apply to all development within Port Orchard, except detached single- family and two-family(duplex) dwellings in any configuration. (Single Family and Duplex Design Standards are found in Chapter 20.139 POMC) Also: (1) Applicability. (a) See POMC 20.127.020(1) for clarification on the types of development to which these standards apply. (b) See POMC 20.127.020(2) for the relationship between the provisions in this Article and other documents and codes. (c) See POMC 20.127.020(3) for the application of building additions and remodels and site improvements. (2) The default block frontage for new streets in commercial and mixed-use zones is Other (POMC 20.127.210) unless a designation is already provided. The default block frontage for undesignated streets within annexed land is Varied (POMC 20.127.170). (3) The block frontage designations apply to development on both sides of the street except where otherwise specified on the maps. For example, on a street with two designations, the designation on the east side of the street applies to properties on the east side of the street. 20.127.120 - How to use this chapter. (1) About the maps. The maps together with the block frontage standards in POMC 20.127.150-250 guide the look and feel of development in commercial and multi-household areas throughout Port Orchard when viewed from the street. The provisions herein recognize that there is a hierarchy of different streets and block frontage types ranging from the pedestrian-oriented storefronts to arterial streets/frontages that warrant greater flexibility in the design of frontages. The block frontage standards address site planning and building design elements including: (a) Building location and orientation. (b) Parking lot location. (c) Window transparency. (d) Weather protection. (e) Landscaping. Page 49 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 12 of 111   The community design framework maps also identify high visibility street corner sites that warrant special design treatment. Refer to POMC 20.127.250 for high visibility street corner requirements. (2) Block frontage standards for individual properties depend on the type of street properties front onto. Thus, consider the following steps in using this Article: (a) Go to the maps in POMC 20.127.130 to find the property and the block frontage type designation for the street or streets fronting the property. For properties in residential zones, the standards for Landscaped block frontages apply (POMC 20.127.160). For properties that front onto multiple streets, see POMC 20.127.240. (b) Table 20.127.120(2) summarizes standards for each of the designated block frontage types. Go to the appropriate section in this Article for the detailed and applicable block frontage standards for applicable block frontage type designation.   Page 50 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 13 of 111   Table 20.127.120(2) Summary of block frontage types. Design Cross Section Example Parking Location Other Key Provisions Storefront  Surface parking lots shall be located to the rear, below, or above storefronts. Parking on the side and front of buildings is prohibited.  Special façade transparency and weather protection provisions  Minimum commercial space depth  No ground floor residential uses except lobbies for upper level units Landscape  Parking is preferred to the rear of the building, but is allowed on the side. For multi-building developments, no more than 50 percent of the street frontage may be occupied by parking and drive aisles. Parking in front is prohibited.      Landscaping to soften façades, screen blank wall surfaces, and screen parking  Provide minimum façade transparency for non- residential uses (variable depending on building setback)  Minimum façade transparency for residential buildings Varied Storefront or Landscape Marine Storefront or Landscape  Parking is preferred to the side, above, or below buildings. No more than 50 percent of the street frontage may occupied by parking and drive aisles. However, the City recognizes the challenges of developing waterfront properties as well as the limitations created in the Shoreline Master Program. Therefore, departures to allow parking to be located at the front of buildings (between the building and the street) may be approved provided design features successfully mitigate the visual impacts of the parking area on the streetscape. Gateway  No parking lot location standards, except that a 10’ buffer of landscaping between the street and off street parking areas  For multi-building developments, surface and structured parking areas (ground floor) are limited to no more than 60 percent of the street frontage  Minimum building setback is 25 feet  At least one building entrance must be visible and accessible from the street Page 51 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 14 of 111   Table 20.127.120(2) Summary of block frontage types. Design Cross Section Example Parking Location Other Key Provisions Other Storefront or Landscape  No parking lot location standards, except that a 10’ buffer of landscaping between the street and off street parking areas  Special façade transparency and weather protection provisions  At least one building entrance must be visible and accessible from the street     Page 52 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 15 of 111   (3) Changes to the block frontage designation for new and existing streets may be made through the following procedures: (a) Text amendment per Chapter 20.06, Code Amendments. (b) Community Design Framework Master Plan per POMC 20.127.260. 20.127.130 - Community design framework maps. (1) Figure 20.127.130 below is an overview map of the applicable planning areas within Port Orchard. Examine the map to determine which map or figure relates to individual properties. (2) Figures 20.127.130(1-16) include community design framework maps for applicable mixed-use and nonresidential zones throughout Port Orchard.   Figure 20.127.130 Port Orchard community design framework maps index.      Page 53 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 16 of 111   Figure 20.127.130(1) Map #1 - Downtown West.      Page 54 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 17 of 111   Figure 20.127.130(2) Map #2 - Downtown East.    Page 55 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 18 of 111   Figure 20.127.130(3) Map #3 - County Campus.    Page 56 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 19 of 111   Figure 20.127.130(4) Map #4 - Lower Mile Hill.    Page 57 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 20 of 111   Figure 20.127.130(5) Map #5 - Upper Mile Hill.    Page 58 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 21 of 111   Figure 20.127.130(6) Map #6 - Bethel North.    Page 59 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 22 of 111   Figure 20.127.130(7) Map #7 - Lund Bethel.    Page 60 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 23 of 111   Figure 20.127.130(8) Map #8 - Bethel South.    Page 61 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 24 of 111   Figure 20.127.130(9) Map #9 - Sedgwick Bethel SR16.    Page 62 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 25 of 111   Figure 20.127.130(10) Map #10 - Bethel Cedar.    Page 63 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 26 of 111   Figure 20.127.130(11) Map #11 - Bethel Lider.    Page 64 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 27 of 111   Figure 20.127.130(12) Map #12 - Tremont.      Page 65 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 28 of 111   Figure 20.127.130(13) Map #13 - Cedar Heights.      Page 66 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 29 of 111   Figure 20.127.130(14) Map #14 - Sidney Glen.      Page 67 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 30 of 111   Figure 20.127.130(15) Map #15 - Sidney Sedgwick.      Page 68 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 31 of 111   Figure 20.127.130(16) Map #16 - McCormick Woods.     Page 69 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 32 of 111   20.127.140 - About the transparency standards. All block frontage designations contain distinct minimum façade transparency standards. The purpose of these standards are to maintain “eyes on the street” for safety and create a welcoming pedestrian environment. Table 20.127.140 below includes details in how they are measured.   Table 20.127.140 Clarification of transparency standards Transparency zones Storefront Ground floor non-residential and non-storefront Residential buildings and residential portions of mixed-use buildings The transparency zone is on the ground floor between 30 inches and 10 feet above sidewalk grade The transparency zone is between 30 inches and 8 feet above grade All vertical surfaces of the façade are used in the calculations Other Transparency Provisions Windows must be transparent Ground level window area for storefronts and other non-residential uses that is covered, frosted, or perforated in any manner that obscures visibility into the building must not count as transparent window area. Exception: Window signs conforming with POMC 20.132.280 may be counted as transparent window area provided the areas generally around the sign are transparent. Display windows Display window may be used for up to 50 percent of non-residential transparency requirements provided they are at least 30 inches deep and allow changeable displays. Tack-on display cases as in the far right Page 70 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 33 of 111   example don’t qualify as transparent window are(1) Integrated display windows Tack-on display cases Structured parking facilities Where structured parking facilities occupy a portion of the façade, any openings simulating windows may be used to help comply with transparency requirements. Parking garage with windows Parking garage without windows     Page 71 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 34 of 111   20.127.150 - Storefront block frontage standards. (1) Description/purpose. Storefront block frontages are the most vibrant and active shopping and dining areas within the city and serve the purpose of attracting pedestrians to enliven the streetscape. Blocks designated as Storefront blocks include continuous storefronts placed along the sidewalk edge with small scale shops and/or frequent business entries.   Figure 20.127.150(1) Storefront vision and key standards.     Page 72 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 35 of 111   (2) Standards. All development as set forth in 20.127.130 on sites containing a Storefront block frontage designation must comply with the following standards (on applicable block frontages):   Table 20.127.150(2) Storefront block frontage standards. Element Standards Examples & Notes Ground floor Land use Non-residential uses specified in Chapter 20.46 POMC, except for lobbies associated with residential or hotel/motel uses on upper floors. Floor to ceiling height 15 feet minimum (applies to new buildings only). Retail space depth 20 feet minimum (applies to new buildings only),  Building placement Required at front property line/back edge of sidewalk. Additional setbacks are allowed for widened sidewalks, pedestrian-oriented space [POMC 20.127.350(4)], or where additional future right of way acquisition is planned by the city. Building entrances Must face the street. For corner buildings, entrances may face the street corner. Façade transparency 60 percent minimum.  Also see POMC 20.127.140 for additional clarification on transparency standards. Weather protection Weather protection with 8 to 15 feet vertical clearance at least 6 feet in minimum depth along at least 80 percent of façade.  Retractable awnings may be used to meet these requirements. Weather protection must not obstruct utility poles or street trees. Weather protection shall comply with WSDOT standards for setback from the face of the curb and may have the effect of reducing the minimum weather protection depth. For downtown properties on Bay Street and adjacent to the city-owned marquee, new development may utilize the existing marquee (subject to approval by the Public Works Director) or new independent weather protection to meet this provision. Page 73 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 36 of 111   Table 20.127.150(2) Storefront block frontage standards. Element Standards Examples & Notes Parking location Also see Chapter 20.124 POMC for related parking requirements New surface or ground level parking areas must be placed to the side or rear of structures and are limited to 60 feet of street frontage.  Provide a 6 feet minimum buffer of landscaping between the street and off street parking areas meeting the standards of Chapter 20.128 POMC.  Sidewalk width 12 feet minimum between curb edge and storefront, including a minimum walking surface width of 8 feet and a clear/buffer zone with street trees.   (3) Departure criteria. Departures from the above standards that feature the  symbol will be considered by the reviewing authority (the director or hearing examiner, as appropriate), provided the alternative proposal meets the purpose of the standards, plus the following criteria: (a) Retail space depth. Reduced depths will be considered where the applicant can successfully demonstrate the proposed alternative design and configuration of the space is viable for a variety of permitted retail uses; (b) Façade transparency. The proposed alternative design treatment of façade area between ground level windows provides visual interest to the pedestrian and mitigates impacts of any blank wall areas. No less than 40 percent of the façade between 30 inches and ten feet above the sidewalk may be approved with a departure; (c) Weather protection. Other proposed alternative design treatments must provide equivalent weather protection benefits; and (d) Parking location. There must be an acceptable tradeoff in terms of the amount and quality of storefront area that is integrated with the development and the applicable parking location Page 74 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 37 of 111   departure. Plus, the alternative must include design features to successfully mitigate the visual impact of additional parking areas along designated Storefront streets. (e) Sidewalk width. Alternative designs may be considered where topographical challenges exist. Alternative designs must be able to accommodate safe and comfortable pedestrian traffic anticipated for full block development.   Page 75 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 38 of 111   20.127.160 - Landscaped block frontage standards. (1) Description/purpose. The Landscaped block frontage designation emphasizes landscaped frontages and clear pedestrian connections between buildings and the sidewalk and serves the purpose of including attractive vegetation within the streetscape. This designation applies to all streets designated Landscaped in POMC 20.127.130, Community design framework maps, and the all development in residential zones.   Figure 20.127.160(1) Landscaped block frontage vision and key standards.     Page 76 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 39 of 111   (2) Standards. All development as set forth in 20.127.130 on sites containing a Landscaped block frontage designation must comply with the following standards (on applicable block frontages):   Table 20.127.160(2) Landscaped block frontage standards. Element Standards Examples & Notes Ground floor: Land use See Chapter 20.46 POMC for permitted use details. Building placement 10’ minimum front setback, except where greater setbacks are specified in the district in Chapter 20.122 POMC or where future right of way need and/or acquisitions have been identified in city plans.  See POMC 20.127.230 for special design provisions associated with ground level residential uses adjacent to a sidewalk. Building entrances Building entrances must be visible and directly accessible from the street.  For uses that front on multiple mixed designated block frontages, an entry along both streets is encouraged, but not required. Façade transparency 25 percent minimum for buildings design with ground level non- residential uses.  15 percent minimum for residential uses.  Windows must be provided on all habitable floors of the façade. Also see POMC 20.127.140 for additional clarification on transparency standards. Façade transparency example. Weather protection Provide weather protection at least 3 feet deep over primary business and residential entries. Page 77 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 40 of 111   Table 20.127.160(2) Landscaped block frontage standards. Element Standards Examples & Notes Parking location Also see Chapter 20.124 POMC for related parking requirements Parking must be placed to the side, rear, below or above uses. For multi- building developments, surface and structured parking areas (ground floor) are limited to no more than 50 percent of the street frontage. Private or shared garage entries must occupy no more than 50 percent of façade width. Provide a 10 feet minimum buffer of landscaping between the street and off street parking areas meeting the standards of Chapter 20.128 POMC.  Landscaping Also see Chapter 20.128 POMC for related landscaping standards The area between the street and building must be landscaped, private porch or patio space, and/or pedestrian-oriented space. For setbacks adjacent to buildings with windows, provide low level landscaping that maintains views between the building and the street. Also provide plant materials that screen any blank walls and add visual interest at both the pedestrian scale and motorist scale. For extended wall areas, provide for a diversity of plant materials and textures to maintain visual interest from a pedestrian scale. Example of low level landscaping that screens foundation walls, provides visual interest, and maintains views from dwelling units to the street. Sidewalk width 6-foot minimum sidewalks are required. Wider sidewalks may be required where designated in other code sections or in the public works standards.   (3) Departure criteria. Departures from the above standards that feature the  symbol will be considered by the reviewing authority (the director or hearing examiner, as appropriate), provided the alternative proposal meets the purpose of the standards, plus the following criteria: Page 78 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 41 of 111   (a) Building entrances. Block frontages with steep slopes and/or those facing busy arterial streets and very limited pedestrian traffic mat warrant some flexibility to this standard (particularly in residential districts). (b) Façade transparency. The proposed alternative design treatment of façade area between ground level windows provides visual interest to the pedestrian and mitigates impacts of any blank wall areas. No less than 40 percent of the façade between 30 inches and ten feet above the sidewalk may be approved with a departure. (c) Parking location. There must be an acceptable tradeoff in terms of the amount and quality of landscaped area that is integrated with the development and the applicable parking location departure. Plus, the alternative must include design features to successfully mitigate the visual impact of additional parking areas along designated Landscaped streets.   Page 79 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 42 of 111   20.127.170 - Varied block frontage standards. (1) Description/purpose. The Varied block frontage designation serves areas that accommodate a mixture of ground floor uses and allows a diversity of development frontages for the purpose of contributing to the visual character of the street and enhancing the pedestrian environment.   Figure 20.127.170(1) Varied block frontage options and standards. Storefront Frontage Landscaped Frontage OR   (2) Standards. All development as set forth in POMC 20.127.130 on sites containing a Varied block frontage have the option to comply with either the Storefront or Landscaped block frontage provisions as set forth above, with the following modifications (on applicable block frontages):   Table 20.127.170(2) Varied block frontage standards. Element Standards Examples & Notes Building placement Buildings may be placed up to the sidewalk edge provided they meet Storefront standards set forth above. 10’ minimum front setback for other buildings, except where greater setbacks are specified in the district per Chapter 20.122 POMC.  Additional setbacks may be required where future right of way need and/or acquisitions have been identified in city plans. See POMC 20.127.230 for special design provisions associated with ground level residential uses adjacent to a sidewalk.   Page 80 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 43 of 111   Table 20.127.170(2) Varied block frontage standards. Element Standards Examples & Notes Façade transparency Any storefront buildings on these block frontages must meet the Storefront block frontage transparency standards above.  40 percent minimum for buildings designed with non-residential uses on the ground floor within 10’ of sidewalk.  25 percent minimum for buildings designed with non-residential uses on the ground floor.  15 percent minimum for residential buildings.  Windows must be provided on all habitable floors of the façade. Also see POMC 20.127.140 for additional clarification on transparency standards. Façade transparency example - non- residential use. Façade transparency example - residential use.   (3) Departure criteria. Departures from the above standards that feature the  symbol will be considered by the reviewing authority (the director or hearing examiner, as appropriate), provided the alternative proposal meets the purpose of the standards, plus the following criteria: (a) Minimum setback. For residential uses, provide design treatments that create an effective transition between the public and private realm. This could include a stoop design or other similar treatments that utilize a low fence, retaining wall, and/or hedge along the sidewalk.      Page 81 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 44 of 111   Figure 20.127.170(3) Stoop examples.        Page 82 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 45 of 111   20.127.180 - Marine block frontage standards. (1) Description/purpose. The Marine block frontage designation serves areas that accommodate a mixture of ground floor uses and allows a diversity of development frontages for the purpose of contributing to the visual character of the street and enhancing the pedestrian environment. (2) Standards. All development as set forth in POMC 20.127.130 on sites containing a Marine block frontage have the option to comply with either the Storefront or Landscaped block frontage provisions as set forth above, with the following modifications (on applicable block frontages). Additionally, all development within the 200-foot shoreline zone must comply with the requirements of the City’s Shoreline Master Program, including but not limited to requirements for location (including setbacks from the shoreline), allowable uses within the applicable shoreline environment designation, view protection and public access.   Table 20.127.180(2) Marine block frontage standards. Element Standards Examples & Notes Building placement Buildings may be placed up to the sidewalk edge provided they meet Storefront standards set forth above. 10 feet minimum front setback for other buildings, except where greater setbacks are specified in the district per Chapter 20.122 POMC.  Additional setbacks may be required where future right of way need and/or acquisitions have been identified in city plans. See POMC 20.127.230 for special design provisions associated with ground level residential uses adjacent to a sidewalk.   Façade transparency Any storefront buildings on these block frontages must meet the Storefront block frontage transparency standards above.  40 percent minimum for buildings designed with non-residential uses on the ground floor within 10 feet of sidewalk.  25 percent minimum for buildings designed with non-residential uses on the ground floor within 20 feet of the sidewalk.  15 percent minimum for residential buildings.  Also see POMC 20.127.140 for additional clarification on transparency standards. Façade transparency example - non- residential use. Page 83 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 46 of 111   Table 20.127.180(2) Marine block frontage standards. Element Standards Examples & Notes Windows must be provided on all habitable floors of the façade. Façade transparency example - residential use. Parking location Parking must be placed to the side, below, or above uses. No more than 50 percent of the street frontage may be occupied by parking and drive aisles.  Parking in the front requires a departure (see 20.127.180(3)(c)). Parking to the rear may only be approved in conjunction with a variance and/or shoreline variance. The construction of any parking within a shoreline area must be consistent with the requirements of the city’s shoreline master program. No more than 50 percent of the street frontage may be occupied by parking and drive aisles. A 10-ft minimum buffer of landscaping must be provided between the street and off-street parking areas, which meets the landscaping requirements of Chapter 20.128. New parking structures must feature landscaped setbacks at least 10 feet in width.   (3) Departure criteria. (a) Minimum setback. For residential uses, provide design treatments that create an effective transition between the public and private realm. This could include a stoop design or other similar treatments that utilize a low fence, retaining wall, and/or hedge along the sidewalk. Page 84 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 47 of 111   (b) Façade transparency. The proposed alternative design treatment of a façade area between ground level windows shall provide visual interest to the pedestrian and mitigate impacts of any blank wall areas. Up to a 40 percent reduction in the minimum amount of façade transparency may be approved via departure. (c) Parking location. Parking may be located in front of a building (between a building and an adjacent street) if other parking locations are demonstrated to be infeasible due to topography, property shape or size, or other contextual circumstances. When a departure is requested to allow parking in front of a building, the parking must provide an acceptable tradeoff in terms of the amount and quality of landscaped area that is integrated with the development and must include design features to successfully mitigate the visual impact of additional parking areas along the street.   Page 85 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 48 of 111   20.127.190 - Gateway block frontage standards. (1) Description/purpose. The Gateway block frontage designation serves strategic areas fronted by highways or other high visibility arterials that feature heavy vehicular traffic. These standards serve the purpose of providing attractive landscaped frontages, limiting the extent of visible surface parking, and accommodating the needs of pedestrians.   Figure 20.127.190(1) Gateway block frontage vision.   (2) Standards. All development as set forth in POMC 20.127.130 on sites containing the Gateway block frontage designation must comply with the Landscaped block frontage provisions as set forth above, with the following modifications:   Table 20.127.190(2) Gateway frontage standards. Element Standards Examples & Notes Building placement The minimum setback for buildings is 25 feet.  Building entrances At least one (publicly accessible for commercial buildings) building entrance must be visible and directly accessible from the street.  Page 86 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 49 of 111   Table 20.127.190(2) Gateway frontage standards. Element Standards Examples & Notes Parking location Parking must be placed to the side, rear, below or above uses.  For multi-building developments, surface parking and the ground floor of structured parking areas are limited to no more than 60 percent of the street frontage.  A 25 feet buffer of landscaping between the street and off street parking areas meeting the performance standards of POMC 20.128.  (3) Departure criteria. See the departure criteria for Landscaped frontages, subsection 20.127.160(3).   Page 87 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 50 of 111   20.127.200 - Internal roadway storefront frontage standards. (1) Description/purpose. The Internal roadway storefront block frontage designation is intended to apply to some existing commercial storefront areas that are located on internal roadways or parking lots. The purpose of this designation is to reinforce and enhance the storefront environment if and when changes occur over time.   Figure 20.127.200(1) Internal roadway storefront frontage vision.     Page 88 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 51 of 111   (2) Standards. Development as set forth in POMC 20.127.130 on sites containing the Internal roadway storefront block frontage designation must comply with the Storefront block frontage standards as set forth above, with only the following modifications:   Table 20.127.200(2) Internal roadway storefront block frontage standards. Element Standards Façade transparency At least 50 percent of ground floor between 30 inches and 10 feet above the sidewalk.  Landscaping Trees must be integrated along the sidewalk every 50 feet of lineal frontage on average. Trees may be in tree grates or in planting strips. Sidewalk width 12 feet minimum between curb edge and storefront, including a minimum walking surface width of 8 feet and a clear/buffer zone with street trees.    (3) Departure criteria. See the departure criteria for Storefront frontages, POMC 20.127.150(3)   Page 89 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 52 of 111   20.127.210 - Other block frontage standards. (1) Description/purpose. All other block frontages in districts that are not designated in the design framework maps are provided greater flexibility with regards to the design of development frontages. These block frontages include a combination of side streets (where most uses front on other adjacent streets) and service oriented streets (often characterized by industrial or service types of uses). While there is greater flexibility in the amount of transparency of façade and the location of surface and structured parking, the purpose of these standards is to ensure that development frontages along these streets provide visual interest at all observable scales and meet the design objectives of the city. (2) Standards. All development as set forth in POMC 20.127.130 with applicable block frontage designations must comply with standards below (on applicable block frontages):   Table 20.127.210(2) Other block frontage standards. Element Standards Ground floor land use See Chapter 20.46 POMC for permitted use details. Building placement Where allowed in the applicable zoning district, buildings may be placed up to the sidewalk edge provided Storefront block frontage standards above are met (except where otherwise noted herein). 10 feet minimum front setback for other buildings, except where greater setbacks are specified in the district per Chapter 20.122 POMC.  See POMC 20.127.230 for special design provisions associated with ground level residential uses adjacent to a sidewalk. Building entrances Building entrances facing the street are encouraged. At a minimum, at least one building entry visible and directly accessible from the street is required. Where buildings are setback from the street, pedestrian connections are required from the sidewalk. Façade transparency For storefronts, at least 60 percent of ground floor between 30 inches and 10 feet above the sidewalk is required.  Other buildings designed with non-residential uses on the ground floor within 10 feet of sidewalk, at least 30 percent of the ground floor between 4-8 feet above the sidewalk.  Other buildings, at least 10 percent of the entire façade (all vertical surfaces generally facing the street).  Window area that is glazed over or covered in any manner that obscures visibility into the storefront space shall not count as transparent window are(1) Weather protection At least 3 feet deep over primary business and residential entries. Parking location There are no parking lot location restrictions. Page 90 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 53 of 111   Table 20.127.210(2) Other block frontage standards. Element Standards Also see Chapter 20.124 POMC for related parking requirements A 10 feet buffer of landscaping between the street and off street parking areas meeting the performance standards of Chapter 20.128 POMC is required.  Landscaping Also see Chapter 20.128 POMC for related landscaping standards The area between the street and building must be landscaped and/or include private porch or patio space. For setbacks adjacent to buildings with windows, provide low level landscaping that maintains views between the building and the street. Also provide plant materials that screen any blank walls and add visual interest at both the pedestrian scale and motorist scale. For extended wall areas, provide for a diversity of plant materials and textures to maintain visual interest from a pedestrian scale. Sidewalk width Where storefront buildings are proposed, sidewalks must meet Storefront block frontage standards above. Otherwise, 6-foot wide minimum sidewalks are required.   (3) Departure criteria. Departures from the above standards that feature the  symbol will be considered by the reviewing authority (the director or hearing examiner, as appropriate) provided the alternative proposal meets the purpose of the standards, plus the following criteria: (a) Minimum setback. Provide design treatments that create an effective transition between the public and private realm. This could include a stoop design to other similar treatments that utilize a low fence, retaining wall, and/or hedge alone the sidewalk. (b) Façade transparency. The design treatment of a façade and/or landscape element provides visual interest to the pedestrian and mitigates impacts of any blank wall area.   Page 91 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 54 of 111   20.127.220 - Trail/Park frontage standards. Trails referenced in the community design framework maps in POMC 20.127.130 aligned adjacent to a street are subject to the applicable block frontage designation for the street. For trails referenced in the community design framework maps that are not adjacent to streets, developments fronting such trails must comply with the Other block frontage standards set forth in POMC 20.127.210.   Figure 20.127.220 Trail/Park frontage examples The development in the left image includes a courtyard that orients towards the trail. The low fence allows visibility between the uses, yet divides public and private space in an acceptable manner. The right image illustrates an active commercial use fronting on the trail.   Page 92 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 55 of 111   20.127.230 - Special residential frontage standards along sidewalks and internal walkways. For residences with ground floor living spaces facing a sidewalk or pedestrian path in a residential or mixed use development, the building must feature at least one of the public/private space transition elements described below. The objective of this standard is to ensure privacy and security for residents, and an attractive and safe walkway that complements the qualities of the adjoining residences within a residential complex. (1) Raised deck or porch option. Provide at least a 60 square foot porch or deck raised at least one foot above grade. The porch or deck must be at least six feet wide, measured perpendicular to the building face. (The deck may be recessed into the unit floor plan so that deck does not extend from the building face a full six feet.) A low fence, rail or hedge, two feet to four feet high, may be integrated between the sidewalk or internal walkway and deck or porch. (2) Front setback options. Provide a minimum ten-foot setback between the sidewalk or internal walkway and the face of the residence. Design options for the front setback: (a) Landscaped area, meeting the provisions of Chapter 20.128 POMC. (b) Semi-private patio space screened by a low fence or hedge (see POMC 20.128, Landscaping). (3) Raised ground floor. If the residence’s ground floor is a minimum of three feet above the grade adjacent to the building, then the landscaped area in (2)(b), may be reduced to four feet wide (except where greater setbacks are specified for the applicable zoning district in Chapter 20.122 POMC). Departures: Other transition design measure that adequately protects the privacy and comfort of the residential unit and the attractiveness and usefulness of the walkway at least as effectively as options (1) through (3) above. See Figure 20.127.230 below for examples of the above treatments.      Page 93 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 56 of 111   Figure 20.127.230 Acceptable public/private transitional space design between sidewalk or walkways and ground level residential units. The upper left image uses a low fence and landscaped setback. The right images use landscaped terraces and elevated ground level units. The lower left image uses a landscaped berm between the walkway and semi-private open space.     Page 94 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 57 of 111   20.127.240 - Where a property fronts onto multiple streets/frontage designations. Where a property fronts onto more than one street and each street has a different frontage designation, each building frontage must comply with the standards for the block frontage upon which it fronts, with the following clarifications: (1) Where a conflict exists between frontage standards, the review authority will apply the standards of a block frontage pursuant to the following order of preference: (a) Storefront. (b) Varied. (c) Marine. (d) Landscaped. (e) Gateway. (f) Other. Items (2)-(5) below clarify how the order of preference works for particular frontage elements. (2) Building Location: For corner sites with Landscaped block frontage on one street and Storefront or Varied on another, a Storefront frontage may wrap around the corner (on the Landscaped block frontage side) for up to a half block width or no more than 120 feet (whichever is more). (3) Entrances: For corner sites, entrances on both streets are encouraged, but only one entrance is required. For corner sites with frontage on a Storefront block frontage on one side, an entrance must be placed on the Storefront block frontage side. For corner sites with a mix of designations that do not include a Storefront block frontage, the entry must be placed in the order of preference identified above. Departures may be considered, provided the location and design of the entry and block frontage treatments are compatible with the character of the area and enhance the character of the street. (4) Transparency: For corner sites at least one block frontage must meet the applicable transparency standards (based on the order of preference above). For the second block frontage, the review authority may approve a reduction in the minimum amount of transparency by 50 percent. For street corners with the same designations on both frontages, buildings must employ the full transparency on the dominant frontage (based on the frontage width or established neighborhood pattern). (5) Parking: Surface parking (including ground floor parking in a structure) adjacent to a street corner is not allowed, except: (a) Corner lots with non-designated frontages (Other) on both streets. (b) Other combination of block frontages, except those with a Storefront designation, via a departure and subject to the applicable departure criteria.      Page 95 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 58 of 111   Figure 20.127.240 Clarifying block frontage standards on street corners.   20.127.250 - High visibility street corners. (1) Description/purpose. The high visibility street corner requirements apply to those sites designated as such on the community design framework maps in POMC 20.127.130. The purpose is to accentuate street corners with high visibility to the public. (2) Designation criteria. High visibility street corners may be designated in: (a) Special high visibility intersections in business districts. (b) Intersections with a high level of pedestrian activity. (c) Special high visibility gateway intersections leading into the city or a particular business district. (d) Existing or planned intersections that are intended to become the focal point of a particular business district or neighborhood center. (3) Standards. Sites located on high visibility street corners must meet the following requirements: (a) Buildings must be located within 20 feet of the street corner. (b) At least one of the following special features must be included (Figure 20.127.250 below illustrates acceptable examples): (i) Corner plaza. (ii) Cropped building corner with a special entry feature. (iii) Decorative use of building materials at the corner. (iv) Distinctive façade articulation. Page 96 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 59 of 111   (v) Sculptural architectural element. (vi) Other decorative elements that meet the purpose of the standards.    Figure 20.127.250 Acceptable high visibility street corner /gateway site examples.   Building 1 includes a corner tower. Building 2 feature cropped building corners with decorative elements. Building 3 uses a decorative canopy. Building 4 uses a change in building materials and façade articulation at the corner. Building 5 incorporates a plaza at the corner. Image 6 shows a decorative landscaped area with a trellis and neighborhood gateway sign.   2  1  3  5 4  6  Page 97 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 60 of 111   20.127.260 - Community design framework master plan. Recently annexed or rezoned commercial or mixed-use properties along with large undeveloped sites necessitate a different approach to applying block frontage standards. The provisions below identify the purpose, applicable sites, block frontage designation options, and special standards for developing community design framework master plans. Such master plans are also an option for property owners to change designations on existing community design framework maps (POMC 20.127.130). (1) Purpose. (a) To provide a thoughtful and fair process to plan for the development of large and new commercial and mixed-use sites consistent with Port Orchard’s Comprehensive Plan. (b) To promote the arrangement of streets, buildings, open space, parking and service areas that creates a strong sense of community and enhances the character of Port Orchard. (c) To avoid uncoordinated patterns of development that waste valuable land, compromise vehicular and pedestrian access, and degrade the character of Port Orchard. (2) Applicable sites. (a) Recently annexed sites zoned as one of the commercial or mixed-use zoning districts. (b) Sites recently rezoned to one of the commercial or mixed-use zoning districts that are not addressed in the community design framework maps in POMC 20.127.130. (3) Block frontage designations options. (a) Prior to site development of applicable sites, a community design framework master plan must be developed, approved and adopted into the Port Orchard Comprehensive Plan per the procedures set forth in Chapter 20.04, Comprehensive Plan Amendments. The master plans must include: (i) New streets and internal roadways along with block frontage designations (types included in this section). (ii) Any designated high visibility street corners. (iii) Any planned open spaces, trails, and shared use paths. (iv) Any special phasing conditions. (v) Other special design conditions unique to the site and plan that must be implemented with future site plan development. (b) Community design framework master plans may utilize any existing block frontage designations that border the site, or include an alternative block frontage designation type or types, subject to master plan approval. (c) Alternatively, site plan development may occur on applicable sites without an approved and recorded community design framework master plan provided all block frontages comply with the standards for Varied block frontages as set forth in subsection (4) of this section.   Page 98 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 61 of 111   (4) Design standards. Community design framework master plans must meet the purpose as set forth above plus the following parameters for specific sites:   Table 20.127.260(4) Community design framework master plan design standards The provisions below are intended to guide the design of individual community design framework master plans. They are referred to as standards, since all proposed plans must successfully demonstrate how they comply with the provisions herein. All Sites  Configure site to create a pedestrian-oriented focal point. Such a focal point could be a main street (storefront), a central square surrounded by storefronts or other similar features.  Larger sites have greater expectations in the amount of Storefront designated frontages.  Goals, policies and concepts from adopted plans must be used to help determine compliance with these standards.   Figure 20.127.260(4) Development examples. Examples of commercial centers configured to create a pedestrian-oriented focal point. Parking areas are carefully located to provide convenience while minimizing impacts to the visual and pedestrian environment.     Page 99 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 62 of 111   (5) Review process and application requirements. (a) Community design framework master plans must be processed as a Type II decision set forth in POMC 20.22.040. (b) Community design framework master plans are subject to application requirements set forth in Chapter 20.24 POMC. Supplemental application submittal requirements include: (i) A conceptual site development plan that identifies the following elements (if applicable): (A) Proposed new public and private streets (including any public rights-of-way). (B) Proposed block frontage designations. (C) Proposed land use(s) concept (to the extent anticipated or desired). (D) Proposed non-motorized circulation elements. (E) Proposed pedestrian-oriented focal point and/or other open spaces or recreational features. (F) Critical areas and buffers. (G) Utility areas. (H) Proposed or potential development phases. (ii) Other information as necessary to support compliance with the design standards set forth in subsection (4) of this section.   Page 100 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 63 of 111   Article III - SITE PLANNING STANDARDS 20.127.300 - Purpose. (1) To preserve and protect the public health, safety, and welfare of the citizens of Port Orchard. (2) To promote the thoughtful layout of buildings, parking areas, circulation, service areas, landscaping, and amenity elements that enhances Port Orchard’s visual character, promotes compatibility between developments and uses, and enhances the function of developments. Also see the individual “purpose” statements for each section in this Article. 20.127.310 - Applicability and compliance. (1) See POMC 20.127.020(1) for clarification on the types of development to which these standards apply. (2) See POMC 20.127.020(2) for the relationship between the provisions in this Article and other documents and codes. (3) See POMC 20.127.020(3) for the application of building additions and remodels and site improvements. 20.127.320 - Relationship to adjacent properties. (1) Purpose. (a) To promote the functional and visual compatibility between developments. (b) To protect the privacy of residents on adjacent properties. (2) Balconies adjacent to side property lines abutting residentially zoned properties. Balconies or rooftop decks within 15 horizontal feet of a side and rear property line abutting a residentially zoned property must feature a railing system that is at least 50 percent opaque. Specifically, 50 percent of the area below the railing must be a sight-obscuring structure. Departures will be allowed where it is determined that the proposed design will not create a compatibility problem in the near- and long-term based on the unique site context.     Page 101 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 64 of 111     Figure 20.127.320(2) Privacy standards for balconies within 15 feet of side property lines.     (3) Light and air access and privacy along the side and rear property lines. Buildings or portions thereof containing multi-household dwelling units whose only solar access (windows) is from the applicable side of the building (facing towards the side property line) must be set back from the applicable side or rear property lines at least 15 feet. See Figures 20.127.320(2) and (3). Departures will be allowed where it is determined that the proposed design will not create a compatibility problem in the near- and long-term based on the unique site context.        Page 102 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 65 of 111   Figure 20.127.320(3) Solar access and privacy standards for multi-household residential buildings along side/rear property lines. Where side setbacks are required. Where there are no side setbacks and where windowless firewalls may be built up to the property line.     Page 103 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 66 of 111   20.127.330 - Non-motorized circulation & design. (1) Purpose. (a) To improve the pedestrian and bicycling environment by making it easier, safer, and more comfortable to walk or ride among residences, to businesses, to the street sidewalk, to transit stops, through parking lots, to adjacent properties, and to connections throughout the city. (b) To enhance access to on- and off-site areas and pedestrian/bicycle paths. (2) Access to sidewalk. All buildings must feature pedestrian connections to a sidewalk per applicable block frontage standards in Article II of this chapter. See subsection (4) of this section for access design requirements.   Figure 20.127.330(2) Examples of direct pedestrian access to buildings from the street.   (3) Internal circulation. (a) For sites with multiple buildings, pedestrian paths or walkways connecting businesses and residential entries on the same development site must be provided. Routes that minimize walking distances must be utilized to the extent practical. Departures will be allowed where steep slopes prevent a direct connection or where an indirect route would enhance the design and/or use of a common usable open space. See subsection (4) of this section for walkway design standards.    Page 104 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 67 of 111     Figure 20.127.330(3)(a) Internal and external pedestrian connections are important.   (b) Sites with residential units. Provide direct pedestrian access between all ground related unit entries and a public street or to a clearly marked walkway network or open space that has direct access to a public street. Residential developments must provide a pedestrian circulation network that connects all main entrances on the site to other areas of the site, such as: (i) Parking areas. (ii) Recreational areas. (iii) Common outdoor areas. (iv) Any pedestrian amenities. For townhouses or other residential units fronting the street, the sidewalk may be used to meet this standard.    Page 105 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 68 of 111     Figure 20.127.330(3)(b)(i) Direct walkways between the street and dwelling units are required. The entries of the example on the left connect directly to a public sidewalk while the entries in the right example connect to a common path that extends to the sidewalk.   Figure 20.127.330(3)(b)(ii) Examples of attractive pedestrian connection through a residential development.   (c) Crosswalks are required when a walkway crosses an on-site paved area accessible to vehicles. Crosswalks must contain contrasting material (such as concrete) and/or patterns (such as stamped asphalt), excluding painted surfaces. (d) Pedestrian walkways through parking lots. Developments with 50 parking spaces or more must provide specially marked or paved walkways through parking areas. At least one walkway must be provided every four rows of parking or at a maximum spacing of 200 feet. The walkways must provide a safe connection to the building entrance and meet the walkway design standards set forth in subsection (4) of this section. See examples below.   Page 106 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 69 of 111   Figure 20.127.330(3)(d) Parking area walkway standards and examples. Note the location of the parking lot walkway in the upper right example (connecting shops in one building to the main entry of a grocery store). Note in the both examples that the concrete walkway extends into the vehicular area to provide a highly visible and safe crosswalk.   (e) Connections to adjacent properties (including parks and trails). Except for when adjacent properties have less than five dwelling units, provide pedestrian walkways that connect to adjacent properties. Public sidewalks in the right-of-way shall not count towards this requirement. Departures will be allowed where it is determined that internal connections are not necessary or practical due to shallow lot depths, steep slopes, or other contextual challenges. (f) Barriers that limit future pedestrian access are prohibited. Gates that limit access to employees are permitted. See subsection (4) of this section for walkway design standards.   Page 107 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 70 of 111   (4) Walkway design. (a) All internal pedestrian walkways must have a minimum five-foot-wide unobstructed walking surface, except where wider walkways are prescribed in this Article or where the applicable uses and context dictate wider walkways. (b) Where parking is adjacent to perpendicular or angled parking, an extra two feet of walkway width must be provided to mitigate for parked vehicles overhanging the walk way. (c) Pedestrian walks must be separated from structures at least three feet for landscaping except where the adjacent building façade meets the Storefront block frontage standards per POMC 20.127.120(2). Departures will be considered where other landscaping and/or façade design treatments to provide attractive walkways are proposed. Examples include sculptural, mosaic, bas-relief artwork, or other decorative treatments that meet the purpose. Figure 20.127.330(4)(c) below provides one example.   Figure 20.127.330(4)(c) Standards for internal walkways adjacent to buildings. Internal walkways adjacent to building walls that do not meet storefront façade standards must provide at least three feet of landscaping to enhance the character of the walkway. The reviewing authority will consider alternative treatments, such as decorative walls (right example).     Page 108 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 71 of 111   (d) Walkway design where multi-tenant commercial or mixed-use buildings 100 feet or more in length abut parking lots. Such walkways must feature a 12-foot wide sidewalk with: (i) Eight feet minimum unobstructed width. (ii) Trees, as approved by the director or hearing examiner, placed at an average of 50 feet on- center and placed in grates or in planting strips as set forth in subsection (iii) of this section. Departure: Breaks in the tree coverage will be allowed near major building entries to enhance visibility. (iii) Planting strips may be used between any vehicle access or parking area and the walkway, provided that the trees required above are included and the walkway meets the applicable width standards herein and the combined walkway and planting strip is at least 12 feet wide. (iv) See also POMC 20.127.340(4), internal roadway design.   Figure 20.127.330(4)d Example of a successful pedestrian sidewalk between parking lot and storefront.     Page 109 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 72 of 111   20.127.340 - Vehicular circulation & parking. The standards herein supplement the provisions of public works standards and Chapter 20.124 POMC. Where there is a conflict, the provisions herein apply, except that the public works director may override this this requirement and apply the public works standard for a driveway if the public works director finds that a failure to apply the public works standards will result in a threat to public safety. (1) Purpose. (a) To create a safe, convenient, and efficient network for vehicle circulation and parking. (b) To enhance the visual character of interior access roads. (c) To minimize conflicts with pedestrian circulation and activity. (2) Driveway provisions. (a) Driveways must comply with the public works standards. Where there is a conflict between the driveway provisions in this chapter and those in the public works standards, the driveway provisions in this chapter apply, except that the public works director may override this this requirement and apply the public works standard for a driveway if the public works director finds that a failure to apply the public works standards will result in a threat to public safety. (b) Drive aisles must meet the standards set forth in POMC 20.124.270, Off-street parking design standards. (c) Minimize parking lot entrances, drive aisles, and other vehicle access routes onto private property from a public right-of-way through the following means: (i) Driveway lanes crossing a public sidewalk must be no wider than the minimum required per entry or exit lane. The city may impose additional restrictions to parking lot and vehicle access points to reduce impacts to public safety, pedestrian movement, on-street vehicle circulation, and visual qualities. (ii) Minimize the number of driveway entrances and comply with the public works standards for driveway entrances. (iii) The reviewing authority may require joint drive aisles serving adjacent developments when joint access is physically and legally available. (iv) Minimize conflicts between entries and vehicle parking and maneuvering areas. (v) At street corner sites, drive aisles must be located on the lowest classified roadway and as close as practical to the property line most distant from the intersection, unless the reviewing authority finds there is a compelling reason to the contrary. (d) Standards for driveways for front-loaded townhouses and other similar attached housing types. (i) Individual driveways are limited to a single lane 12-feet wide. (ii) Driveways shared between two attached units are limited to 20 feet in width. (iii) Front loaded townhouses or other similar attached housing types must be at least 30 feet wide to qualify for individual or shared driveways.     Page 110 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 73 of 111   Figure 20.127.340(2)(d) Driveway standards for front-loaded attached housing types. The left image shows an acceptable front loaded townhouse example in plan view, where individual units are at least 30 feet wide. The below example does not meet that requirement.   (e) Port Orchard Boulevard access. Access from Port Orchard Boulevard except for areas with a designated block frontage as shown in the community design framework maps in POMC 20.127.130 shall be prohibited. (3) Inter-site connectivity. The provision of through vehicle access connections between commercially or non-residentially zoned properties is required except where the reviewing authority determines it is infeasible or undesirable (e.g., where it is determined that such a vehicle connection would impact safe pedestrian movement). See Article II of this chapter for specific block frontage standards. Vehicle access may be in the form of a dedicated or private alley, connected or shared parking lots, shared drive aisles, or similar features. (4) Internal roadway design. (a) To increase the function and appearance of internal roadways on large sites (greater than two acres), street trees and sidewalks must be provided on all internal access roadways, excepting access roads designed solely for the purpose of service (e.g. waste pick-up) and loading. (b) In some instances where traffic speed and volume are low, the reviewing authority may approve a street where vehicle, bicycle and pedestrian movement are mixed such as in a “woonerf” or “shared street”. Woonerf streets must feature traffic calming and safety measures as well as landscape and amenity features as determined by the reviewing authority.    Page 111 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 74 of 111     Figure 20.127.340(4) Good internal roadway examples. The examples above include angled parking and planter strips with street trees. Pedestrian-scaled lighting also contributes to the character in the upper right image. The above left image illustrates a thoroughfare lane with a row of street trees. A sidewalk is included on one side of the street to provide a strategic connection between businesses. The right image illustrates the curbless “woonerf” design where travel speeds are low and lanes are shared between pedestrians and vehicles.   (c) Drive-through facilities. Where allowed, drive through facilities (e.g., drive-up windows) must comply with the following. (i) Drive-through lanes, including waiting and holding lanes, must be buffered from the street and internal walkways by one or both of the following: (A) A planting strip at least five feet wide with continuous plantings of evergreen shrubs and/or trees that will, at maturity, provide a continuous evergreen screen at least four feet tall. (B) A wall at least three feet high constructed of brick, stone or siding materials that matches the principal walls of the building to which the sign applies Page 112 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 75 of 111   Departure: Alternative screening schemes may be approved provided they include both the wall and a substantial vegetative screen. The landscaping must comply with Chapter 20.128 POMC. (ii) Drive-through lanes must not restrict pedestrian access between a public sidewalk and on- site buildings. Walkways must not be located within required stacking space as set forth in the public works standards. (iii) This section contains standards for drive-through lanes and facilities. Signs associated with drive-through lane are regulated under POMC 20.132.050 (7). 20.127.350 - On-site open space. (1) Purpose. (a) To create useable space that is suitable for leisure or recreational activities for residents. (b) To create open space that contributes to the residential setting. (c) To provide plazas that attract shoppers to commercial areas. (d) To provide plazas and other pedestrian oriented spaces in commercial areas that enhance the employees’ and public’s opportunity for active and passive activities, such as dining, resting, people watching, and recreational activities. (e) To enhance the development character and attractiveness of commercial development. (2) Usable residential open space. (a) All multi-household development, including multi-household portions of mixed-use development, must provide minimum usable open space equal to 100 square feet per dwelling unit for studio and one-bedroom dwellings and 150 square feet per dwelling unit for dwellings with two or more bedrooms. Developments adjacent to or across the street from a public park can qualify for a 50 percent reduction in the required open space via a departure, where it is determined that both the park and access to the park help to meet the usable open space purpose. The required open space may be provided in a combination of ways: (i) Shared open space. 100 percent of the required open space may be in the form of shared open space available to all residents and meeting the requirements of subsection (2)(b) of this section. Shared open space may be in the form of courtyards, front porches, patios, play areas gardens or similar spaces. (ii) Ground level private outdoor space. 100 percent of the required open space may be provided by ground level outdoor space that is adjacent and directly accessible to the subject unit. Such open spaces must be enclosed by a fence and/or hedge at least 32 inches in height to qualify. Ground level private open space in excess of minimum requirements must not be used in the calculations for determining the minimum useable open space requirements for other units in the development. (iii) Balconies. Up to 50 percent of the required open space may be provided by private balconies provided they are at least 36 square feet with no dimension less than six feet. Individual balconies in excess of minimum requirements must not be used in the Page 113 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 76 of 111   calculations for determining the minimum useable open space requirements for other units in the development. (iv) Common indoor recreation areas. Up to 50 percent of the required open space may be provided by common indoor recreation areas meeting the requirements of subsection (2)(c) of this section. (v) Shared roof decks. For mixed-use buildings, up to 100 percent of the required open space may be provided by shared roof decks located on the top of buildings which are available to all residents and meet the requirements of subsection (2)(d) of this section. Roof decks in mixed-use buildings shall not be accessible to commercial tenants, employees, or customers. (b) Shared open space. Shared open space can include landscaped courtyards or decks, entrance plazas, gardens with walkways, children’s play areas, pools, and water features provided they are accessible to all residents of the development. Accessible areas used for storm water retention or other multipurpose recreational and/or green spaces that meet the design criteria herein may qualify as shared open space. Special requirements for common usable open spaces include the following: (i) Shared open space must be located in centralized areas that are visible from units within the development. (ii) Required setback areas must not count as shared open space unless the design of the space meets the standards herein. (iii) Shared open space must feature no dimension less than 15 feet in order to provide functional leisure or recreational activity (unless otherwise noted herein). (iv) Shared open space must feature paths or walkable lawns, landscaping, seating, lighting, and play structures, sports courts, or other pedestrian amenities to make the area more functional and enjoyable for a range of users. (v) Shared open space must be separated from ground level windows, streets, service areas and parking lots with landscaping, fencing, and/or other acceptable treatments that enhance safety and privacy for both the shared open space and dwelling units. (vi) When possible, the space should be oriented to receive sunlight, face east, west or preferably south. (vii) Stairways and service elements located within or on the edge of shared open space must not be included in the open space calculations. (viii) Shared porches may qualify as shared open space provided they are at least 8 feet in depth and 96 square feet in total area. (ix) The space must be accessible to all residents of the development. (x) Natural, artificial, and stormwater ponds may be included in the shared open space. A maximum of 50 percent of the pond surface area, as measured when the pond is at its maximum designed depth, may be counted towards the minimum requirements of subsection (2)(a) of this section. Ponds must be integrated with trails and other features listed above to qualify as shared open space.   Page 114 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 77 of 111   Figure 20.127.350(2)(b)(i) Shared open space examples. The upper examples include a combination of open lawn area for informal recreation plus walkways and decorative landscape areas to enhance the setting for residents. The left image above includes a covered gathering space with outdoor grills adjacent to a landscaped commons with a central walkway. The right image includes a pond/wetland type area with boardwalk and seating areas.        Page 115 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 78 of 111   Figure 20.127.350(2)(b)(ii) Acceptable and unacceptable examples of ponds as open space. The above images show an acceptable example of using a pond as shared open space. Lawns, gentle slopes, and a perimeter walking path are integrated into this amenity. The above image shows a stormwater pond that would not qualify as shared open space. The pond is fenced, inaccessible to users of the development, and it is lined by steep rocky banks.   (c) Indoor recreational areas. Such spaces must meet the following conditions: (i) The space must be located in a visible area, such as near an entrance, lobby, or high traffic corridors. (ii) Space must be designed specifically to serve interior recreational functions and not merely be leftover unrentable space used to meet the open space requirement. Such space must include amenities and design elements that will encourage use by residents. (d) Shared rooftop decks. Such spaces must meet the following requirements: Page 116 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 79 of 111   (i) Space must feature hard surfacing and provide amenities such as seating areas, landscaping, and/or other features that encourage use. (ii) Space must integrate landscaping elements that enhance the character of the space and encourage its use. (iii) Space must incorporate features that provide for the safety of residents, such as enclosures, railings, and appropriate lighting levels.   Figure 20.127.350(2)(d) Rooftop deck examples.   (3) Usable commercial open space. New developments with non-residential uses (except for development within the Employment – Industrial/Office zone) on sites with a total site area greater than 0.5 acre must provide open space equal to at least two percent of the gross square footage of the development. The open space may be in the form of pedestrian-oriented space per subsection (4) of this section, garden, play area or other open space feature that serves both as a visual amenity and a place for human activity. Portions of sidewalks that are wider than 12 feet and which meet the standards of pedestrian-oriented space may be counted toward this requirement. For this specific standard, “Site area” includes all land needed for the non-residential portion of the project including parking, service areas, access and required landscaping. Non-residential open space features must be approved by the reviewing authority. Departure: Open space area may be reduced to one percent of the development envelope if the reviewing authority finds the project includes exceptional design features and elements that meet the purpose of the standards. This includes open spaces that feature a combination of design (site materials, amenities, and configuration) and location/context that clearly exceed typical plaza designs found in the region.        Page 117 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 80 of 111   Figure 20.127.350(3) Example site development integrating usable commercial open space.   (4) Pedestrian-oriented space design criteria. This subsection describes the requirements and desired characteristics of pedestrian-oriented space (which may be used to meet the requirements of subsection (3) of this section). (a) Required pedestrian-oriented space features. (i) Visual and pedestrian access into the site from a street, private access road, or publicly- accessible parking area. (ii) Paved walking surfaces of either concrete or approved unit paving. (iii) The spaces must be located in or adjacent to areas with significant pedestrian traffic to provide interest and security, such as adjacent to or visible from a building entry. (iv) At least two linear feet of seating area (a bench or ledge at least 16 inches deep and appropriate seating height) or one individual seat per 60 square feet of plaza area or open space. (v) Landscaping components that add visual interest and are not a visual barrier. This could include planting beds, raised planters, and/or potted plants. (b) Desirable pedestrian-oriented space features. (i) Pedestrian amenities, such as site furniture, lighting, artwork, drinking fountains, shade structures or other similar features. (ii) Adjacent buildings with transparent windows and doors covering at least 50 percent of the façade between 30 inches and 10 feet above the ground level. (iii) Pedestrian weather protection, alcoves, seating, or other features along building edges to allow for outdoor gathering. (iv) Concrete or unit paving. (c) Features prohibited within a pedestrian-oriented space. Page 118 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 81 of 111   (i) Asphalt pavement. (ii) Adjacent service areas (e.g., trash areas) that are not separated with landscaping, as required in POMC 20.127.360, Location and design of service areas and mechanical equipment. (iii) Adjacent chain-link fences. (iv) Adjacent "blank walls" without "blank wall treatment" (see POMC 20.127.460(3)). (v) Outdoor storage.   Figure 20.127.350(4)(i) Example of standards applied to a small pedestrian-oriented space.   Page 119 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 82 of 111   Figure 20.127.350(4)(ii) Desirable examples of pedestrian-oriented space. The left example above is a colorful plaza with outdoor seating, landscaping elements and direct access to adjacent retail uses. The upper right image is a commons area with adjacent covered areas. A covered outdoor gathering space (left) may be used to meet pedestrian-oriented space requirements. In the right image, the widened sidewalk area may be counted as pedestrian-oriented space.   (5) Useable mixed-use open space. Developments with a mix of residential and non-residential uses may double-count useable open space for both residential units and commercial square footage, provided the double-counted open space meets the requirements of both subsections (2) and (3) of this section. Page 120 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 83 of 111   20.127.360 - Location and design of service areas and mechanical equipment. (1) Purpose. (a) To minimize adverse visual, odor, and noise impacts of mechanical equipment, utility cabinets and service areas at ground and roof levels. (b) To provide adequate, durable, well-maintained, and accessible service and equipment areas. (c) To protect residential uses and adjacent properties from impacts due to location and utilization of service areas. (2) Location of ground related service areas and mechanical equipment. (a) Service areas (loading docks, trash dumpsters, compactors, recycling areas, electrical panels, and mechanical equipment areas) must be located for convenient service access while avoiding negative visual, auditory, olfactory, or physical impacts on the streetscape environment and adjacent residentially zoned properties. Service areas must be sited for alley access if available. The director and/or hearing examiner may require evidence that such elements will not significantly impact neighboring properties or public areas. (For example, noise damping specifications may be required for fans located near residential zones.) (b) Exterior loading areas. Exterior loading areas for commercial uses must not be located within 20 feet of a single family residentially zoned property Departure opportunity: Exterior commercial loading areas are exempt from this standard if the reviewing authority finds such a restriction does not allow feasible development and alternative design measures can successfully mitigate potential negative impacts. For example, areas and drives may be required to be separated from the residential lot by a masonry wall at least eight feet high. (c) Service areas must not be visible from the sidewalk and adjacent properties. Where the reviewing authority finds that the only option for locating a service area is an area visible from a public right-of-way, resident/customer parking area, internal walkway or pedestrian area, or from an adjacent property, the area must be screened with structural and landscaping screening measures provided in subsection (3) of this section and Chapter 20.128, Landscaping. Departure opportunity: Service elements accessible from an alley are exempt from screening requirements. (d) Design for safety. Other provisions of this section notwithstanding, service areas used by residents must be located to avoid entrapment areas and other conditions where personal security is potentially a problem. Pedestrian-scaled lighting or other measures may be required to enhance security. (e) Locate and shield noise-producing mechanical equipment, such as fans, heat pumps, etc. to minimize sounds and reduce impacts to adjacent residentially zoned properties.    Page 121 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 84 of 111     Figure 20.127.360(2) Service element location. Locate service elements to reduce impacts on the residential and pedestrian environment, and provide appropriate enclosure   (3) Screening of ground related service areas and mechanical equipment. (a) Where screening of ground level service areas is called for [see subsection (2) of this section], adhere to the following: (i) A structural enclosure must be constructed of masonry, heavy-gauge metal, or decay- resistant material that is also used with the architecture of the main building. The reviewing authority may allow materials other than those used for the main building if the finishes are similar in color and texture or if the proposed enclosure materials are more durable than those for the main structure. The walls must be sufficient to provide full screening from the affected roadway, pedestrian areas or adjacent use. The enclosure may use overlapping walls to screen dumpsters and other materials (see Figure 20.127.360(3) below). (ii) Gates must be made of heavy-gauge, site-obscuring material. Chain link or chain link with slats is not an acceptable material for enclosures or gates. (iii) Where the inside of service enclosures are visible from surrounding streets, walkways, and buildings, an opaque or semi-opaque horizontal cover or screen must be used to mitigate unsightly views. The horizontal screen/cover should be integrated into the enclosure design and compatible with adjacent development. Page 122 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 85 of 111   (iv) Collection points must be located and configured so that the enclosure gate swing does not obstruct pedestrian or vehicle traffic, or does not require that a hauling truck project into any public right-of-way. Ensure that screening elements allow for efficient service delivery and removal operations. (v) The service area must be paved. (b) The sides and rear of service enclosures must be screened with landscaping at least five feet wide in locations visible from the street, parking lots, and walkways to soften views of the screening element and add visual interest. Departures from the provisions of subsections (3)(a) and (3)(b) above will be considered provided the enclosure and landscaping treatment meet the purpose of the standards and add visual interest to site users.   Figure 20.127.360(3) Acceptable screening enclosures.   (4) Utility meters, electrical conduit, and other service utility apparatus. (a) These elements must be located and/or designed to minimize their visibility to the public. Project designers are strongly encouraged to coordinate with applicable service providers early All three examples use durable and attractive enclosures with trees and shrubs to soften views of the enclosures from the side. The lower left example uses a trellis structure on top – a desirable example particularly where the top of the enclosures are visible from surrounding buildings, streets, and walkways (due to topography or building heights). Page 123 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 86 of 111   in the design process to determine the best approach in meeting these standards. If such elements are mounted in a location visible from the street, pedestrian walkway, shared open space, or shared auto courtyards, they must be screened with vegetation and/or integrated into the building’s architecture.   Figure 20.127.360(4) Utility meter location and screening - good and bad examples. Place utility meters in less visible locations. The upper and lower left examples are successfully tucked away in a less visible location and/or screened by vegetation. The right images are poorly executed and would not be permitted in such visible locations. Such meters must be coordinated and better integrated with the architecture of the building.     Page 124 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 87 of 111   (5) Location and screening of roof mounted mechanical equipment. (a) All rooftop mechanical equipment, including air conditioners, heaters, vents, and similar equipment must be fully screened from public view both at grade and from higher buildings with the exception of solar panels and roof-mounted wind turbines. Screening must be located so as not to interfere with operation of the equipment. (b) For rooftop equipment, all screening devices must be well integrated into the architectural design through such elements as parapet walls, false roofs, roof wells, clerestories, or equipment rooms. Screening walls or unit-mounted screening is allowed but less desirable. Wood must not be used for screens or enclosures. Louvered designs are acceptable if consistent with building design style. Perforated metal is not permitted (c) The screening materials must be of material requiring minimal maintenance, and must be as high as the equipment being screened. (d) Locate and shield noise-producing mechanical equipment, such as fans, heat pumps, etc. to minimize sounds and reduce impacts to adjacent residentially zoned properties.     Figure 20.127.360(5) Examples of how to screen roof-mounted mechanical equipment. The examples above use walls to screen rooftop mechanical equipment from view from the street.   Page 125 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 88 of 111   Article IV - BUILDING DESIGN STANDARDS 20.127.400 - Purpose. See the individual “purpose” statements for each section in this Article. 20.127.410 - Applicability and compliance. (1) See POMC 20.127.020(1) for clarification on the types of development to which these standards apply. (2) See POMC 20.127.020(2) for the relationship between the provisions in this Article and other documents and codes. (3) See POMC 20.127.020(3) for the application of building additions and remodels and site improvements. 20.127.420 - Building character. (1) Purpose. (a) To promote buildings with an architectural character that reflects the region’s aesthetic and is based on human scaled design details, durable high quality materials, sustainable design measures, and respond uniquely to the site’s context. (b) To emphasize that high quality design is most critical to Port Orchard’s high visibility sites and corridors. (c) To avoid generic, corporate architectural design that degrades the character and identity of Port Orchard. (2) Corporate architecture. (a) Architecture that is defined predominately by corporate identity features and is difficult to adapt to other uses is prohibited. For example, some franchise convenience uses have very specific architectural features (such as a distinctive roofline design that functions as a sign) that reinforce their identity. As tenants change in these types of buildings, these corporate identity features can negatively impact the character of the area and identity of new tenants. These features can also be very expensive to reconfigure and adapt to new uses. (b) Exemptions. This prohibition does not apply the Bravo Terrace and Sedgwick Road areas identified in Figure 20.127.420.    Page 126 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 89 of 111     Figure 20.127.420 Areas exempt from the prohibition of corporate architecture.     Page 127 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 90 of 111   20.127.430 - Building massing & articulation. (1) Purpose. (a) To employ façade articulation techniques that reduce the perceived scale of large buildings and add visual interest from all observable scales. (b) To create clear and welcoming building entries. (2) Façade articulation - non-residential. Storefronts and other buildings with non-residential uses on the ground level façade must include articulation features every 40 feet (maximum) to create a pattern of small storefronts. At least three of the following features must be employed at intervals no greater than 40 feet: (a) Window patterns and/or entries. (b) Use of weather protection features. (c) Use of vertical piers/columns. (d) Change in roofline per subsection (6) of this section. (e) Change in building material or siding style. (f) Other design techniques that effectively reinforce a pattern of small storefronts compatible with the building’s surrounding context. Other features that could be used to meet the standards on block frontages that are not designated as Storefront (g) Vertical elements such as a trellis with plants, green wall, art element. (h) Providing vertical building modulation of at least 12 inches in depth if tied to a change in roofline per subsection (6) of this section or a change in building material, siding style, or color. Departure: Other articulation features may be used provided they meet the purpose of the standards and the design criteria set forth in subsection (4) of this section.   Page 128 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 91 of 111   Figure 20.127.430(2) Façade articulation examples. The left image uses window patterns, weather protection elements, and roofline modulation. The photo example to the right also includes window patterns and weather protection along with a change in masonry texture and color to articulate the façade. The lower example illustrates how a multitenant retail building can successfully be articulated (windows, weather protection, vertical building modulation, and roofline changes)   (3) Façade articulation - residential. Residential buildings must include articulation features at intervals that relate to the location/size of individual units within the building (or no more than every 30 feet) to break up the massing of the building and add visual interest and compatibility to the surrounding context. At least three of the following features must be employed at intervals no greater than the unit interval or 30 feet (whichever is less): (a) Use of windows and/or entries. (b) Change in roofline per subsection (6) of this section. (c) Change in building material, siding style, and/or window pattern. (d) Providing vertical building modulation of at least 12 inches in depth if tied to a change in roofline modulation per subsection (6) of this section or a change in building material, siding style, or Page 129 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 92 of 111   color. Balconies may be used to qualify for this option if they are recessed or projected from the façade by at least 18 inches. Juliet balconies or other balconies that appear to be tacked on to the façade will not qualify for this option unless they employ high quality materials and effectively meet the purpose of the standards. (e) Vertical elements such as a trellis with plants, green wall, art element. (f) Other design techniques that effectively break up the massing at no more than 30-foot intervals. Departures: Other articulation features will be considered provided they meet the purpose of the standards and the design criteria set forth in subsection (4) of this section.   Figure 20.127.430(3) Residential façade articulation examples. Below examples use a combination of vertical building modulation, window patterns, material changes, and roofline modulation.   (4) Departure criteria associated with articulation standards. Proposals must meet the purpose of the standards. The following criteria will be considered in determining whether the proposed articulation treatment meets the “purpose”. (a) Consider the type and width of the proposed articulation treatment and how effective it is in meeting the purpose given the building’s current and desired context (per Port Orchard’s Comprehensive Plan or applicable adopted subarea plan). Page 130 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 93 of 111   (b) Consider the applicable block frontage designation. Undesignated block frontages warrant more flexibility than block frontages designated as Varied or Landscaped. (c) Consider the size and width of the building. Smaller buildings warrant greater flexibility than larger buildings. (d) Consider the quality of façade materials in concert with doors, windows, and other façade features and their ability to add visual interest to the street from a pedestrian scale and more distant observable scales.   Figure 20.127.430(4) Façade articulation departure examples. This building would be a good departure example. Its two clear articulation features are the window patterns and the entry/building modulation feature (3 minimum are required). However, the overall effectiveness of these articulation features combined with the high quality of materials and detailing and the relatively small width of the building help it meet the purpose of the standards.   (5) Maximum façade width. For most buildings, small scale articulation techniques (see subsections (2) and (3) above) are sufficient to reduce the perceived scale of buildings, add visual interest, and contribute to the pedestrian environment. Larger buildings need more substantial articulated/modulated features to break up the massing and add visual interest. Building façades wider than 100 feet must include at least one of the following features to break up the massing of the building and add visual interest. Building walls facing alleys, rear or side yards are not subject to the standards herein, except for zone edge properties, when adjacent to a lower intensity zoning district. Page 131 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 94 of 111   (a) Provide vertical building modulation at least 20 feet deep and 30 feet wide. For multi-story buildings, the modulation must extend through more than one-half of the building floors. (b) Use of a contrasting vertical modulated design component featuring all of the following: (i) Component extends through all floors above the first floor fronting on the street. Exception: upper floors that are set back more than ten feet horizontally from the façade are exempt. (ii) Utilizes a change in building materials that effectively contrasts with the rest of the façade. (iii) Component is modulated vertically from the rest of the façade by an average of six inches. (iv) Component is designed to provide roofline modulation per subsection (6) of this section. (c) Façade employs building walls with contrasting articulation that make it appear like two distinct buildings. To qualify for this option, these contrasting façades must employ all of the following: (i) Different building materials and/or configuration of building materials. (ii) Contrasting window design (sizes or configurations). (d) Departures will be considered provided the design meets the purpose of the standards. Supplemental consideration for approving alternative designs: (i) Width of the façade. The larger the façade, the more substantial articulation/ modulation features need to be. (ii) Block frontage designation. Storefront designated block frontages warrant the most scrutiny while undesignated streets warrant more flexibility. (iii) The type of articulation treatment and how effective it is in meeting the purpose given the building’s context.    Page 132 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 95 of 111     Figure 20.127.430(5)(i) Illustrating maximum façade width standards. Less than 100 feet wide: Meets standard More than 100 feet wide: Does not meet standard   Building incorporates a 20-foot x 30-foot courtyard along the façade to effectively break it up into smaller components: Meets standard.     Page 133 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 96 of 111     Figure 20.127.430(5)(ii) Façade width good and bad examples. Both buildings use modulated entry features to help break up the perceived massing and add visual interest. The left building (about 110 feet wide) uses an articulated partial third floor along with smaller articulation treatments on the main floors to effectively break up the perceived scale and add visual interest (this would be a good departure example). The building to the right would not be an acceptable example. While the articulated features on the lower floors help, the monotony of the very long upper floor and roofline would not be acceptable.   (6) Roofline modulation. In order to qualify as a façade articulation feature in subsections (2), (3), and (5) of this section, rooflines must employ one or more of the following: (a) For flat roofs or façades with horizontal eave, fascia, or parapet, the minimum vertical dimension of roofline modulation is the greater of two feet or 0.1 multiplied by the wall height (finish grade to top of the wall) when combined with vertical building modulation techniques described in subsections above. Otherwise, the minimum vertical dimension of roofline modulation is the greater of four feet or 0.2 multiplied by the wall height. (b) A pitched roofline or gabled roofline segment of at least 20 feet in width. Buildings with pitched roofs must include a minimum slope of 5:12 and feature modulated roofline components at the interval required per the applicable standard above. (c) A combination of the above. Departures: Other designs will be considered provided the roofline modulation design effectively reduces the perceived scale of the building and adds visual interest.    Page 134 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 97 of 111     Figure 20.127.430(6) Acceptable examples of roofline modulation. Roofline modulation examples for flat roofs. The bottom left building illustrates a pitched roof example and the bottom right building includes a combination of flat and gabled rooflines.     Page 135 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 98 of 111   20.127.440 - Building details. (1) Purpose: (a) To encourage the incorporation of design details and small-scale elements into building façades that are attractive at a pedestrian scale. (b) To integrate window design that adds depth, richness, and visual interest to the façade. (2) Façade details - non-residential and mixed-use buildings. All commercial and mixed-use buildings must be enhanced with appropriate details. All new buildings and additions associated with Level II and III Improvements (see POMC 20.127.020) must employ at least one detail element from each of the three categories below for each façade articulation interval (see POMC 20.127.430). For example, a building with 120 feet of street frontage with a façade articulated at 40-foot intervals will need to meet the standards for each of the three façade segments below. (a) At least one window and/or entry treatment, such as the following, must be employed for each articulation interval: (i) Display windows divided into a grid of multiple panes. (ii) Transom windows. (iii) Roll-up windows/doors. (iv) Other distinctive window treatment that meets the purpose of the standards. (v) Recessed entry. (vi) Decorative door. (vii) Other decorative or specially designed entry treatment that meets the purpose of the standards.     Figure 20.127.440(2)(a) Examples of decorative or specially designed windows and entries. C  B A  Page 136 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 99 of 111   Figure 20.127.440(2)(a) Examples of decorative or specially designed windows and entries. Examples of decorative or specially designed windows and entries. A = openable storefront window. B = transom windows. C = openable window with decorative details. D = decorative window shades. E = Decorative door. F = recessed entry.     D E E  Page 137 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 100 of 111   (b) At least one building element or façade detail, such as the following, must be employed for each articulation interval: (i) Custom-designed weather protection element such as a steel canopy, cloth awning, or retractable awning. (ii) Decorative building-mounted light fixtures. (iii) Bay windows, trellises, towers, and similar elements. (iv) Decorative, custom hanging sign(s) (option only available for building remodels). (v) Other details or elements that meet the purpose of these standards.   Figure 20.127.440(2)(b) Examples of attached elements that enhance the visual intrigue of the building. Examples of elements attached to façade that enhance the visual intrigue of the building. A = retractable awning. B = custom hanging bike rack and repair station integrated as a storefront design element. C = decorative façade/sign lighting D and E = custom decorative canopy. F decorative tower.     C B A  D F E  Page 138 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 101 of 111   (c) At least one building material and other façade element, such as the following, must be employed for each articulation interval: (i) Use of decorative building materials/use of building materials. Examples include decorative use of brick, tile, or stonework. (ii) Artwork on building, such as a mural or bas-relief sculpture. (iii) Decorative kick-plate, pilaster, base panel, or other similar feature. (iv) Hand-crafted material, such as special wrought iron or carved wood. (v) Other details that meet the purpose of the standards. “Custom,” “decorative,” or “hand-crafted” elements referenced above must be distinctive or “one-of-a-kind” elements or unusual designs that require a high level of craftsmanship. Departures will be considered provided the façade (at the overall scale and at the individual articulation scale) meets the purpose of the standards above.   Figure 20.127.440(2)(c) Examples of decorative surface materials. Examples of decorative surface materials. A = decorative brick/design. B = decorative tile-work and column pattern. C = decorative medallion. D = decorative mosaic tile work. E = decorative bulkhead. F = Decorative materials and design.   A  B  C  F  E  D  Page 139 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 102 of 111   (3) Window design standards. All windows (except storefront display windows) must employ designs that add depth and richness to the façade. At least one of the following features must be included to meet this requirement: (a) Recess windows at least two inches from the façade. (b) Incorporate window trim (at least three inches wide) around windows (c) Incorporate other design treatments that add depth, richness, and visual interest to the façade. Departures from the window standards above will be considered provided the design meets the purpose of the standards.   Figure 20.127.440(3) Acceptable and unacceptable window design examples. Recessed and/or trimmed windows above. The window in the left image lacks any other detail that adds visual interest. However, the right example, with its prominent black sash and muntins and frieze/apron details above and below the windows would be acceptable departure design.     Page 140 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 103 of 111   (4) Cornice/roofline design for flat roofs. Non-residential and mixed-use buildings employing a flat roof must employ a distinctive roofline that effectively provides an identifiable “top” to the building, including one of the following (Figure 20.127.440(4) below illustrates acceptable and unacceptable examples): (a) A traditional cornice line or a contemporary interpretation of a traditional cornice line. Such rooflines must be proportional to the size and scale of the building. (b) Understated cornice lines are permitted depending on the materials and design of the base and middle elements in reinforcing the base/middle/top configuration. Rooftop solar units are permitted, provided the placement and design of units visible from the surrounding streetscape are carefully integrated into the overall design concept of the building. Departure: Alternative roofline designs may be acceptable provided the building design, collectively, meets the purpose of the standards. For example, adding additional articulation treatments and/or detailing may help the building meet the departure criteria.   Figure 20.127.440.D Examples of buildings employing confident and distinctive rooflines.       Building 1 uses a dramatic overhanging cornice at the corner. The left portion of Building 1 uses a very simple cornice line - to go with the upper level setback. Building 2 uses a traditional cornice line. 2 1  Page 141 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 104 of 111   Figure 20.127.440.D Examples of buildings employing confident and distinctive rooflines.        Building 3 uses capped projecting columns along with an understated cornice line. Building 4 uses a very simple roofline - which is acceptable in this case due to the prominence of the wooden canopy.   (5) Articulated building entries. The primary building entrance for an office building, hotel, apartment building, public or community-based facility or other multi-story commercial building must be designed as a clearly defined and demarcated standout architectural feature of the building. Such entrances must be easily distinguishable from regular storefront entrances on the building. Such entries must be scaled proportional to the building. See Figure 20.127.440(5) below for good examples.   Figure 20.127.440(5) Acceptable building entry examples.     4  3  Page 142 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 105 of 111   20.127.450 - Building materials. (1) Purpose. (a) To encourage the use of durable, high quality, and urban building materials that minimize maintenance cost and provide visual interest from all observable vantage points. (b) To promote the use of a distinctive mix of materials that helps to articulate façades and lends a sense of depth and richness to the buildings. (c) To place the highest priority on the first floor in the quality and detailing of materials at the pedestrian scale. (2) Quality building materials. Applicants must use high quality durable materials. This is most important for the base of buildings, particularly for commercial and mixed-use buildings where the façade is sited close to sidewalks. At a minimum, stone, brick or tile masonry, or architectural concrete (first two feet only) must be used (excluding window and door areas) for the first floor of cladding on non-residential or mixed-use buildings and the first two feet of residential buildings. (3) Special conditions and limitations for concrete block (also known as concrete masonry unit or CMU). Concrete block may be used as a cladding material if it is incorporated with other permitted materials and/or incorporates a combination of textures and/or colors to add visual interest. For example, combining split or rock-façade units with smooth blocks can create distinctive patterns. The figure below illustrates acceptable concrete block use/designs.   Figure 20.127.450(3) Acceptable concrete block use/design. CMU is the primary cladding for the corner element above, but secondary to brick on the main façade s. The corner element uses a combination of decorative split faced CMU closer to the sidewalk and smooth- faced CMU that is colored to look more like traditional white terra cotta tiles. The above façade illustrates an acceptable alternative example, as CMU is used as the primary cladding material. Note the use of split-façade CMU’s above each of the awnings and coupled with the use of smooth-façade CMU’s on the vertical columns (which employ black accent tiles for added interest).     Page 143 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 106 of 111   (4) Special conditions and limitations for metal siding. Metal siding may be used as a secondary cladding material if it is incorporated with other permitted materials and complies with the following standards: (a) It must feature visible corner molding and trim and must not extend lower than two feet above grade. Masonry, concrete, or other durable material must be incorporated between the metal siding and the ground plane. (b) Metal siding must be factory finished with a matte, non-reflective surface. (c) Use of at least two colors of metal siding on the façade is encouraged but not required. Departures: Other designs will be considered provided the material’s integration and overall façade composition meets the purpose of the standards.   Figure 20.127.450(4) Acceptable metal siding examples. The use of metal siding in each example above is secondary to masonry. The left and right images are more contemporary in character, whereas the middle image is more rustic and industrial, with more refined windows.     Page 144 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 107 of 111   (5) Special conditions and limitations for the use of Exterior Insulation and Finish System (EIFS). Such material/finishes may be used as a decorative accent cladding material if incorporated with other permitted materials and compliant with the following: (a) EIFS is limited to no more than 20 percent of the total façade area and may not be the primary cladding material. (b) EIFS must feature a smooth or sand finish only. (c) EIFS must be trimmed in wood, masonry, or other material and must be sheltered from weather by roof overhangs or other methods. (d) EIFS must not extend lower than eight feet above grade. Concrete, masonry, or other durable material must be used for ground level wall surfaces to provide a durable surface where damage is most likely. Departures to allow up to 50 percent coverage of the façade and other design treatments will be considered provided the material’s integration and overall façade composition meets the purpose of the standards.   Figure 20.127.450(5) Acceptable and unacceptable EIFS examples. Note the use of brick and decorative concrete block on the ground level and EIFS on the second floor of the left image. The window treatments visible on the second floor add depth and interest to the façade. The right image employs EIFS between the window and sidewalk - this design is prohibited.   (6) Special conditions and limitations for cementitious wall board paneling/siding. Such material may be used provided it meets the following provisions: (a) Cement board paneling/siding may not be used on the ground floor of non-residential or mixed- use buildings where adjacent to a sidewalk or other pedestrian path. (b) Where cement board paneling/siding is the dominant siding material, the design must integrate a mix of colors and/or textures that are articulated consistent with windows, balconies, and modulated building surfaces and are balanced with façade details that add visual interest from the ground level and adjacent buildings. Departures: Other designs will be considered provided the material’s integration and overall façade composition meets the purpose of the standards. Page 145 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 108 of 111     Figure 20.127.450(6) Acceptable and unacceptable cementitious wall board examples. The above building uses cementitious wall board in different textures and colors to help articulate the façade. The white color replicates the board and batten style in the left image and green color in the right image effectively replicates horizontal wood siding. The wall board panels covering a large area in a single color would not meet the purpose of the standards. The right image is a better example and combines larger panels (dark maroon color) with horizontal wall board siding (beige color) as effective articulation features. Below is a similar acceptable example. Page 146 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 109 of 111   Figure 20.127.450(6) Acceptable and unacceptable cementitious wall board examples. Another acceptable wall board example replicating board and batten style with horizontal siding integrated with different colors and roofline modulation.     Page 147 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 110 of 111   20.127.460 - Blank wall treatments. (1) Purpose. (a) To avoid untreated blank walls. (b) To retain and enhance the character of Port Orchard’s streetscapes. (2) Blank wall definition. A wall (including building façades and retaining walls) is considered a blank wall if it is over ten feet in height, has a horizontal length greater than 15 feet, and does not include a transparent window or door.   Figure 20.127.460(2) Blank wall definition.   (3) Untreated blank walls visible from a public street, pedestrian-oriented space, common usable open space, or pedestrian walkway are prohibited. Methods to treat blank walls can include: (a) Display windows at least 16 inches of depth to allow for changeable displays. Tack on display cases do not qualify as a blank wall treatment. (b) Landscape planting bed at least five feet wide or a raised planter bed at least two feet high and three feet wide in front of the wall with planting materials that are sufficient to obscure or screen at least 60 percent of the wall’s surface within three years. (c) Installing a vertical trellis in front of the wall with climbing vines or plant materials. (d) Installing a mural as approved by the reviewing authority. (e) Special building detailing that adds visual interest at a pedestrian scale. Such detailing must use a variety of surfaces; monotonous designs will not meet the purpose of the standards. For large visible blank walls, a variety of treatments may be required to meet the purpose of the standards.    Page 148 of 260     DRAFT PORT ORCHARD DESIGN STANDARDS Revised: February 21, 2018 Page 111 of 111     Figure 20.127.460(3) Acceptable and unacceptable blank wall treatments. The left image illustrates that heavy landscaping can be very effective in treating a large blank wall. The building in the middle image uses a combination of planted trellises and display ads integrated with the building’s architecture along a façade facing a drive-through. The example in the right image simply doesn’t use enough treatments and the result is a stark and unwelcome streetscape.   Page 149 of 260 DRAFT Port Orchard Design Standards  2/14/2018  OVERVIEW  (1) Project Goals The Design Standards are a key tool in implementing the goals and policies of Port Orchard’s Comprehensive Plan. Specific goals:  Provide clear objectives for those embarking on development projects in Port Orchard.  Ensure that new commercial and multi-household development is of high quality and beneficially contributes to Port Orchard’s character.  Promote Port Orchard’s quality of life for residents and businesses  Upgrade the visual appearance of Port Orchard’s principal vehicular corridors.  Ensure that new developments within existing neighborhoods are compatible with, and enhance the character of, Port Orchard’s neighborhoods.  Promote an increase in walking and bicycling throughout the city.  Maintain and enhance property values within Port Orchard. (II) Suggested Regulatory Approach: Providing Predictability AND Flexibility The Design Standards seek to provide a combination of predictability and flexibility that fits the Port Orchard situation. We’ve often called this the “Guidard” approach – which strategically integrates standards and guidelines. Our suggested way to accomplish this is to:  Provide clear minimum standards so applicants and decision makers understand what the base requirements are. This is where we need to be clear about what’s the minimum acceptable compliance level, whether it’s the amount of façade transparency along a street, the amount of usable open space that’s required, or the maximum width of a building before some form of articulation or modulation is needed to break up the building’s massing.  Offer a number of ways of meeting particular standards. For example, many standards include a toolbox of options, whereby the applicant needs to accomplish one or more of the choices. This allows the applicant some flexibility in designing the project. It also allows the applicant some control over design and materials costs. On our end, we need to make sure that the minimum standards meet the city’s design objectives, but aren’t so difficult to achieve that they increase costs excessively or overly restrict design.  Offer strategic departure opportunities. These allow applicants to propose alternative techniques to comply with specific standards. Unlike variances, departures are voluntary options. Applicants need to demonstrate how such alternative designs meet the purpose and other special departure criteria. We suggest that departures are offered only for certain standards where flexibility is warranted. Page 150 of 260     1      DESIGN STANDARDS ‐  REVISIONS TO EXISTING CODE        Repeal Ordinance 1478 prohibiting access from Port Orchard Boulevard.    Chapter 2.78  DESIGN REVIEW BOARD    2.78.010 Purpose of board.  The purpose of the design review board (DRB) is:  (1)  Tto review development applications associated with development in the downtown overlay district  area. The DRB will review applications and makeprovide  recommendations to the director of planning  regarding the an applications’ consistency with the City’s adopted design guidelinesstandards.   (2) To review completed projects and evaluate design outcomes for the purposes of determining  whether amendments to the design standards (POMC 20.128‐131) should be recommended, and to  make recommendations to the Planning Commission and City Council for amendments to the City’s  Design Standards as found in POMC 20.128.     2.78.020 Definitions.  (1) “Board” or “DRB” means the design review board.  (2) “Director” means the director of planningDepartment of Community Development Director or  designee.  (3) “Design guidelinesstandards” means the design and building standards for the downtown overlay  district as now or hereafter adopted by city council resolution or ordinance.adopted in sections 20.128.  (Ord. 006‐08 § 1; Ord. 035‐07 § 1).    2.78.030 Board established – Membership.  (1) Appointment. There is created a design review board consisting of not less than five and not more  than seven members who shall be appointed by the mayor subject to confirmation by the city council.  Vacancies occurring otherwise than upon the expiration of terms may be filled for the unexpired terms  by the mayor subject to confirmation by the city council.  (2) Membership. A five‐member board shall consist of three lay members who reside within city limits or  reside within the Port Orchard urban growth area and have an interest in architecture, building, or  design, and two professional members who reside within city limits or reside within the Port Orchard  urban growth area or own a business within the city of Port Orchard, and who are desired to have  expertise in any one of the following fields: architecture, landscape architecture, urban design/planning,  structural engineering, graphic, industrial, and interior design, building or carpentry, or similar  disciplines. A seven‐member board shall consist of four lay members and three professional members  who meet the qualifications set forth above.  (3) Compensation. Board members shall serve without compensation.     2.78.040 Terms of membership.  (1) Terms. The initial terms of the appointed positions by position number shall expire on December  31st of the year set opposite said position number as follows:  Lay Position No. 1 – 2009;  Page 151 of 260     2      Lay Position No. 2 – 2010;  Lay Position No. 3 – 2011;  Lay Position No. 4 – 2011;  Professional Position No. 5 – 2009;  Professional Position No. 6 – 2010;  Professional Position No. 7 – 2011.  Thereafter the terms of membership for members shall be three years. No person shall serve more than  two full consecutive terms. An appointment to fill a portion of an unexpired term less than one year in  length shall not be considered a full term.  (2) Removal. When a member misses three consecutive meetings without excuse by the board, the  position may be declared vacant by a majority vote of the other members of the board.     2.78.050 Meetings.  (1) Meetings. The board shall meet at such times deemed necessary for conducting business.  (2) Quorum. No business shall be conducted without a quorum at the meeting. A quorum shall exist  when the meeting is attended by a majority of the members of the board, which may include the  chairperson.  (3) Chairperson. The board shall elect one of its members to serve as chairperson for a term of one year.  The chairperson may be elected to serve one consecutive additional term, but not for more than two  successive terms.  (4) Voting. All actions of the board shall be represented by a vote of the membership. Unless otherwise  provided in this chapter and Chapter 18.94 POMC, a simple majority of the members present at the  meeting in which action is taken shall approve any action taken. The chairperson may vote at the  meetings.  (5) Rules and Procedures. The board may adopt rules and procedures it deems necessary for the  conducting of business.     2.78.060 Powers and duties.  The board is not delegated any executive or legislative power, authority or responsibility and is not  acting on behalf of the city council or the mayor but rather serves in an advisory capacity and makes  recommendations to the director. The powers and duties of the board shall consist of the following:  (1) Preapplication Meeting. One member of the board shall, whenever possible, attend the pre‐ application meeting with staff and the proponent of a project that is subject to design guidelines. The  chairperson shall be responsible for ensuring that this duty is rotated among the board’s members.  (21) Application Review. Review all applications for building permits in areas having adopted design  guidelines compliance with design standards as prescribed elsewhere in this code and make  recommendations regarding the consistency of projects with adopted design standards. The board shall  review the application for consistency with the applicable design guidelines and make a  recommendation to the director.  (3) Biannual Review. Not later than September 30, 2009, and every two years thereafter, provide the  mayor and city council with a written report setting forth the board’s assessment of the design  guidelines, in light of the applications reviewed in the prior two years, and recommending changes to  the design guidelines that are intended to reinforce the purpose of the design guidelines and to provide  greater clarity to applicants.  (42) Annual Review and Recommendations.  The Board shall meet at least once annually to review  completed projects and evaluate design outcomes for the purposes of determining whether  amendments to the design standards (POMC 20.128) are required.  The design review board shall make  Page 152 of 260     3      its recommendation, even if it recommends that no changes are required, prior to December 31 every  year.  (3) Such other design‐related matters as shall be referred to the board for review and recommendation  by the mayor or city council.     2.78.070 Conflict of interest.  A member of the board shall not participate in review of a project for which the member has a conflict  of interest.     2.78.0780 Administrative support.  The planning Department of Community Developmentdepartment shall provide administrative support  for the board.     CHAPTER 20.38    20.38.200 Downtown overlay district (map designation ‐dod).   (1) Boundaries. The DOD consists of three subareas: the central DOD subarea, DOD west gateway  subarea, and DOD east gateway subarea shall consist of all real property located within the area  depicted on the comprehensive plan DOD map.   (2) Unless exempt pursuant to POMC 20.38.226, no city permit or approval shall be issued for,  and no person shall start, any development that is subject to the design review process until  the development has received design review approval.  (32) Purposes. The purposes of the DOD are to:  (a) Implement the land use goals and policies set forth in the comprehensive plan.  (b) Provide for the development of an integrated mixed use downtown district that contains office,  service, retail, residential and recreational uses within close proximity to one another.  (c) Encourage imaginative site and building design and development while maintaining viewMaintain  view corridors and a small town feel.  (d) Identify significant environmental impacts and ensure appropriate mitigation with attention to  sustainable or low‐impact development.  (e) Encourage environmentally sustainable development.  (f) Promote economic development and job creation in the city.  (g) Encourage energy conservation in building design and layout.  (h) Promote an integrated system of pedestrian‐friendly walkways and parking areas.   (i) Enhance the city’s waterfront character while maintaining the maritime presence.  (jg) Encourage the development of buildings with ground floor retail with office uses and residential  uses above.  (kh) Promote a walkable community by encouraging the development of public open spaces, waterfront  access, and pedestrian‐friendly walkways.  (l) Locate and combine parking areas in order to minimize the number of points of access to and from  Bay Street.  (m) Encourage architectural and site designs that serve as gathering places in wet and dry  conditions.  (n) Promote greater public transportation availability within Port Orchard and across Sinclair Inlet during  the evening hours to improve access to/from the DOD.     Formatted: Space After: 0 pt, Line spacing: single Page 153 of 260     4      20.38.201 DOD – Permitted uses.   All uses listed below are permitted uses. No other uses shall be permitted in the central DOD, unless  said use is accessory to the principal permitted use or uses. Uses within the east and west “gateways”  may include uses allowed within the underlying zone or any of the central DOD uses.  (1) On lots that do not abut Bay Street the following are permitted uses:  (a) Single‐family attached dwellings.  (b) Multifamily dwellings above the first floor, including but not limited to condominiums.  (c) Amusement/entertainment including but not limited to theaters, bowling, amusement arcades; but  excluding adult entertainment.  (d) Barbers and beauticians.  (e) Bed and breakfasts.  (f) Boat dealers; provided no inventory shall be allowed on site.  (g) Conference centers.  (h) Daycare.  (i) Dock.  (j) Commercial recreation.  (k) General business services.  (l) Health services, including offices, patient clinics, and medical/dental laboratories.  (m) Hotels and motels.  (n) Library.  (o) Liquor and wine stores.  (p) Marinas and marine supply.  (q) Museums.  (r) Parks.  (s) Parking lots and parking structures.  (t) Post office.  (u) Professional offices and services, including financial, accounting, and legal.  (v) Public agency offices.  (w) Retail sales and services listed as permitted uses in a commercial or mixed use zones, except for  motor vehicle dealers, auto supply stores, gas stations, boat dealers, adult entertainment, and fuel  dealers.  (x) Trails.  (y) Water transportation facilities.  (z) Medical marijuana cooperatives as permitted in this chapter.  (2) On lots that abut Bay Street the following are permitted uses:  (a) Single‐family attached dwellings above the first floor.  (b) Multifamily dwellings above the first floor, including but not limited to condominiums.  (c) Amusement/entertainment including but not limited to theaters, bowling, amusement arcades; but  excluding adult entertainment.  (d) Barbers and beauticians.  (e) Bed and breakfasts above the first floor.  (f) Boat dealers; provided no inventory shall be allowed on site.  (g) Conference centers.  (h) Daycare above the first floor.  (i) Dock.  (j) Commercial recreation.  Page 154 of 260     5      (k) General business services, except bail bonds and similar uses under SIC Code 7389 are prohibited  from the ground floor and must be located above the ground floor.  (l) Health services, including offices, patient clinics, and medical/dental laboratories above the first floor.  (m) Hotels and motels.  (n) Library.  (o) Liquor and wine stores.  (p) Marinas and marine supply.  (q) Museums.  (r) Parks.  (s) Parking lots and parking structures.  (t) Post office.  (u) Professional offices and services, including financial, accounting, and legal above the first floor.  (v) Public agency offices above the first floor.  (w) Retail sales and services listed as permitted uses in a commercial or mixed use zone, except for  motor vehicle dealers, auto supply stores, gas stations, boat dealers, adult entertainment, and fuel  dealers.  (x) Trails.  (y) Water transportation facilities.  (z) Tattoo parlors shall only be allowed on or above the second floor.  (aa) Medical marijuana cooperatives as permitted in this Titlepter.     20.38.202 DOD – Nonconforming uses.   (1) All existing nonresidential uses other than the uses specified in POMC 20.38.201 shall be  legally nonconforming uses. Provided, an existing nonresidential use may be expanded if the  expansion does not more than double the square footage of the use as it existed on the  effective date of these regulations.  (2) All existing single‐family detached residential uses shall be legally nonconforming uses and  may be expanded, altered, or rebuilt provided the structure continues to comply with this  subtitle.     20.38.203 DOD – Conditional uses.   Uses that require a conditional use permit:  (1) Any retail store or complex of retail stores with more than 40,000 square feet of total combined floor  area that is otherwise allowed as a permitted use;   (2) Any building or structure that exceeds the maximum allowable building heights set forth in  POMC 20.38.211 through 20.38.213 and that is otherwise allowed as a permitted use.     20.38.204 DOD – Conditional uses, decision criteria.   Applicable standards for granting a conditional use permit are as follows:   (1) Meets the criteria set forth in Chapter 20.50 POMC;   (2) Project will be designed in accordance with the design standards set forth in POMC  20.38.217 through 20.38.223; and  (3) The applicant agrees to provide a special amenity or amenities as listed in POMC 20.38.214  with a monetary value of one percent of the value of the new/proposed building and land. This  Formatted: Space Before: 0 pt, After: 0 pt Formatted: Space Before: 0 pt, After: 0 pt Page 155 of 260     6      requirement shall be in addition to any amenity(ies) that the applicant is providing in order to  exceed the basic allowable structure height.     20.38.205 DOD – Lot area.   No minimum lot size is required within the central DOD area. It is the intent of this title that each  enterprise or use be located on a site commensurate with its use and sufficient to meet the  requirements for off‐street parking, loading and unloading, and setbacks.     20.38.206 DOD – Lot coverage.   Development shall comply with the maximum land coverage requirements for the underlying zone, as  set forth in Subtitle V of this Title; provided, there is no maximum lot coverage for development on  either side of Bay Street between Harrison Avenue and Orchard Avenue.     20.38.207 DOD – Minimum setback requirements.   (1) Except as otherwise required by the shoreline master program and critical areas ordinance, as now  or hereafter amended, there is no minimum setback from a property line that does not abut a street  right‐of‐way or alley.   (2) There is no minimum setback from a property line that abuts a street right‐of‐way provided there is a  10‐foot‐wide pedestrian walkway. If there is inadequate right‐of‐way to establish a 10‐foot‐wide  pedestrian walkway, then the building shall be set back a sufficient distance to accommodate a 10‐foot‐ wide pedestrian walkway.   (3) The setback from a property line that abuts an alley shall comply with the requirements for the  underlying zone as set forth in Subtitle VI.     20.38.208 DOD – Structure and measurements.   (1) For purposes of the DOD, structure and building height shall include: Roof forms and decorative  elements not intended for occupancy; mechanical penthouses and elevator overruns and machine  rooms; parapets; and all other roof structures.  (2) Where existing grade and finished grade are different, the lower of either existing grade or finished  grade shall be used to calculate vertical height. For those lots that are between Bay Street and Prospect  Street/Alley and currently abut Bay Street, the existing Bay Street elevation shall be the basis for  measuring structure height.  (3) For those lots within the DOD abutting Bay Street, the Bay Street elevation shall be the basis for  measuring building height.  (4) For those properties in the DOD gateway abutting Bethel Avenue, Bethel Avenue shall be the basis  for measuring building height.     20.38.209 DOD – Allowable building heights.  Building heights may vary based on location of parcel within the DOD and by the opportunity to achieve  a higher structure if certain amenities are incorporated into the development design.     20.38.210 DOD – Heights within the central DOD and DOD east and west gateways on the north side of  Bay Street.                                                            The maximum allowable building height limit shall be 27 feet, which may be increased up to 39  feet when the applicant:   (1) Meets the requirements for a conditional use permit, as set forth in Chapter 20.50 POMC;   Page 156 of 260     7      (2) P provides water access and/or views amenities or other special amenities a special amenity(ies) in  accordance with POMC 20.38.2144 with a monetary value of one percent of the value of the  new/proposed building and land; and.  (3) Complies with the requirements of POMC 20.38.218 regarding reduced floor area above 27  feet. Provided, in no circumstances shall the maximum allowable structure height exceed 27  feet, which may be increased up to 39 feet when the conditions listed in subsection (1) of this  section are satisfied.     20.38.211 DOD – Heights within the central DOD and DOD east and west gateways south of Bay Street.   For lots that are between Bay Street and Prospect Street/Alley and abut Bay Street, the  maximum allowable building height limit shall be 39 feet, which may be increased up to 55 feet  when the applicant:   (1) Meets the requirements for a conditional use permit, as set forth in Chapter 20.50 POMC;   (2) Provides  provides water access and/or views amenities or other special amenities a special  amenity(ies) in accordance with POMC 20.38.214214. with a monetary value of one percent of  the value of the new/proposed building and land; and  (3) Complies with the requirements of POMC 20.38.218 regarding reduced floor area above 39 feet.  Provided, in no circumstances shall the maximum allowable structure height exceed 39 feet, which may  be increased up to 55 feet when the conditions listed in subsection (2) of this section are satisfied.     20.38.212 DOD – Heights for lots that do not abut Bay Street.   The maximum allowable building height limit shall be 27 feet, which may be increased up to 39  feet when the applicant:    (1) Meets the requirements for a conditional use permit, as set forth in Chapter 20.50 POMC;   (2) P provides a water access and/or views amenities or other special amenitiesspecial amenity(ies)  in accordance with POMC 20.38.2144 with a monetary value of one percent of the value of the  new/proposed building and land; and  (3) Complies with the requirements of POMC 20.38.218 regarding reduced floor area above 27 feet.  Provided, in no circumstances shall the maximum allowable structure height exceed 27 feet, which may  be increased up to 39 feet when the conditions listed in subsection (2) of this section are satisfied.     20.38.213 DOD – Gateways heights for those lots abutting Bethel Avenue.   The maximum allowed building height limit shall be 39 feet, which may be increased up to 55 feet with a  conditional use permit (CUP) when the applicant p:   (1) Meets the requirements for a conditional use permit, as set forth in Chapter 20.50 POMC;   (2) Provides a water access and/or views amenities or other special amenities special amenity(ies) in  accordance with POMC 20.38.214 with a monetary value of one percent of the value of the  new/proposed building and land; and  (3) Complies with the requirements of POMC 20.38.219 regarding reduced floor area above 39 feet.  Provided, in no circumstances shall the maximum allowable structure height exceed 39 feet, which may  be increased up to 55 feet when the conditions listed in subsection (2) of this section are satisfied.     20.38.213 214 DOD – Amenities for maximum building and structure height.   Maximum building heights may be increased in accordance with POMC 20.38.210 to 20.38.213 when  water access and/or views amenities or other special amenities are provided as prescribed in this  Formatted: Space Before: 0 pt, After: 0 pt Formatted: Space Before: 0 pt, After: 0 pt Page 157 of 260     8      section.  The amenities listed below may not be suitable for all sites and may require additional city and  state approvals (i.e shoreline permits).  Height bonuses will not be approved in the absence of re quired  permits when applicable.  The amenities listed below are weighted using a point system.  In order for a  height increase to be granted pursuant to POMC 20.38.210 to 20.38.213, an applicant shall provide  amenities worth at least 3 points from the following list:One or more special amenities at a cost at  least equal to the monetary values set forth in POMC 20.38.211 and 20.38.212 are required to  be provided whenever a development proposes to exceed the maximum allowable building  height or structure height, or as provided in POMC 20.38.210. Under no circumstances shall a  building exceed the maximum structure height except as provided in POMC 20.38.211 and  20.38.212. The design of each amenity will be reviewed to ensure that it is appropriate for the  proposed location and provides for a public benefit. All amenities must be maintained for the  life of the building. All amenities must be constructed on the site of the proposed development.   Any one of the following meets the requirement for a special amenity:  (1) Construct a public water access corridor and sidewalk through the site or along the site’s edge  where no such access preexists.  The sidewalk shall be a minimum of 12‐feet in width with  public access provided in an easement or through another legal instrument. (2 points).  (2) For Waterfront Development, construct a water viewing platform at the water’s edge measuring  at least 400 square feet. (2 points)  (3) For Waterfront development. Construction of 14‐foot paved pedestrian pathway along the  entire waterfront in a 20‐foot easement. (1‐point per 100 lineal feet of pathway constructed.   For properties less than 100 linear feet in width, 1 point shall be awarded for a pathway that  spans the property.)  (4) Construct a water feature. (1 point)  (1) Exterior public space that meets all of the following design standards:  (a) The space has a dimension ratio of not more than 5:1 (length: width);  (b) Seating is provided at one seat for each 100 square feet of public space;  (c) Incorporates a variety of trees and other plantings covering at least 20 percent of the  space;  (d) Includes art or water features;  (e) Maximizes solar exposure during the summer; and  (f) Provides access and visibility from the nearest public sidewalk or walkway or signage  to indicate the same.  (2) A water feature that provides access and visibility from the nearest public sidewalk  or walkway or signage to indicate the same.  (3) Public access opportunity by means of a 10‐foot‐wide public sidewalk or walkway  between buildings for the entire length of the property such that the pathway is  perpendicular to an existing public sidewalk and provides mid‐block access between  existing buildings. At least 20 percent of the area shall be landscaped.  (4) For waterfront development, a water view opportunity by means of a 10‐foot‐wide  public pathway along the property perimeter down one side line of the property for the  entire length of the property to mean higher high water, bulkhead, or to the waterside  face of a structure, whichever is further waterward, then across the waterside face of  the property or structure.  Formatted: Space Before: 0 pt, After: 0 pt, Numbered + Level: 1 + Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" + Indent at: 0.5" Page 158 of 260     9      (5) Water view opportunity by means of a public viewing platform. The minimum area of  the platform shall be 25 percent of the structure’s footprint. The platform may have  access that is independent from the primary access in and out of the building. The  platform shall also contain landscaping elements. Railings around the platform may  exceed the maximum height permitted for the structure. In addition, the public viewing  platform shall comply with the following requirements:  (a) Seating shall be provided at one seat for each 100 square feet of public space;  (b) Incorporate a variety of trees and other plantings covering at least 20 percent of the  space;  (c) Include art or water features; and  (d) Has direct solar exposure during the summer.  (1) (6) For waterfront development, a harbor access opportunity by means of public access  to a pier constructed in a manner consistent with the city’s shoreline master program  and connected by a minimum five‐foot‐wide public pathway to the frontage street. A  minimum of 10 feet of open water on each side shall surround the pier. (2 points)  (5)   (6) (7) For waterfront development, a harbor access opportunity by means of public access to a  small boat landing available for transient use by rowboats, canoes, dinghies, kayaks, etc.,  constructed in a manner consistent with the city’s shoreline master program and connected by a  minimum five‐foot‐wide public pathway to the frontage street. A minimum of 10 feet of open  water on each side shall surround the small boat landing. (1 point)    (2) (8) For waterfront development, a harbor access opportunity by means of public access  to transient moorage for up to two 30‐foot boats, which must have a minimum water depth of  eight feet, must be easily accessible to visiting boats, and posted with signage that can be read  at a distance of 100 feet.  (9) A vegetated roof as defined in the “Low Impact Development Technical Guidance  Manual for Puget Sound” (January 2005), as now or hereafter amended. Provided, a  minimum of 50 percent of the total rooftop area of the building, excluding the space  occupied by mechanical equipment, shall meet the requirements of a vegetated roof. As  used herein, the rooftop area is not limited to the uppermost portion of the building but  includes all roof areas.  (10) With regards to the special amenities described in subsections (1), (2), and (3) of  this section, nothing shall prohibit two or more property owners from combining their  several special amenity obligations into a single amenity; provided, the amenity is  constructed on at least one of the parcels being developed. When two or more property  owners combine their special amenity obligations, then the requirements for the  combined single amenity shall be 100 percent of what would otherwise have been  required if done separately.  (11) With regards to the special amenities described in subsections (1) and (2) of this  section, a property owner may apply to the city to contribute to an amenity to be built  on public land within the central DOD; provided the property owner must contribute an  Formatted: Space Before: 0 pt, After: 0 pt, Numbered + Level: 1 + Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" + Indent at: 0.5" Formatted: No bullets or numbering Formatted: Space Before: 0 pt, After: 0 pt, Numbered + Level: 1 + Numbering Style: 1, 2, 3, … + Start at: 1 + Alignment: Left + Aligned at: 0.25" + Indent at: 0.5" Page 159 of 260     10      amount equal to two percent of the value of the new/proposed building and land. The  city shall have sole discretion to accept or reject the application as it deems appropriate.  (3)(7) (12) An Construct an enclosed plaza (such as an atrium or galleria) consisting of a  publicly accessible continuous open space located within a building and covered to provide  overhead weather protection while admitting natural daylight and which meets the following  design standards:  a. The space has a dimension ratio of not more than 5:1 (length: width);  b. Seating is provided at one seat for each 100 square feet of public space;  c. At least five percent of the area must be landscaped;  d. Must be accessible to the public at least during normal business hours;  e. Must be signed (interior and exterior) to identify the enclosed plaza is available for  public use; and  f. Must be visible from the building’s primary public entrance. (1 point)  (4)(8) Public Restroom. A room or rooms containing toilets and lavatories for the use of the  general public, with only limited control for purposes of personal safety and which are:  a. Accessible to the public at least during normal business hours;  b. ADA Accessible;  c. Signed for Public Use;  d. Not Otherwise required by law. (1 Point)    20.38.215 DOD – Parking requirements.   The general parking standards set forth in Chapter 16.4520.124 POMC shall apply unless a more  restrictive specific provision is set forth in the DOD specific parking standards in Subtitle VI.     20.38.216 DOD – Design and building standards.   The design and building standards set forth in POMC 20.38.218 through 20.38.225 shall be  interpreted and applied so as to promote development that is compatible with the city’s  historic character and the scale of existing buildings, to maintain views, and to create a  pedestrian‐friendly environment, and shall be used during the Design Review Board (DRB)  review of all development applications.   20.38.217 DOD – Rooftop mechanical equipment and roof design.   (1) Rooftop mechanical equipment shall be concealed from view by a roof form integrated with  the overall architecture of the building, either by locating the equipment within the structure or  concealing it from view behind a parapet that is at least as high as the equipment. Views of  rooftop mechanical equipment from nearby hillsides shall be minimized.  (2) Roof design shall reduce the mass and scale of buildings, add visual interest and prevent  glare. Flat roofs shall have parapets or screening to conceal the roof and mechanical  equipment. Sloping roofs shall have three or more roof planes. When designing rooftops visible  from hillsides, special attention shall be given to prevention of reflective glare and  placement/design of mechanical equipment. Roof gardens or vegetated roofs, as defined in  POMC 20.38.214(9), are encouraged. Roof ridgelines that are perpendicular to Bay Street are  encouraged.   20.38.218 DOD – Structure height modulation.   If the structure height of a building exceeds 39 feet, its height shall be modulated as follows:  Formatted: Space Before: 0 pt, After: 0 pt Page 160 of 260     11      (1) If a building’s facade is within 10 feet of a sidewalk, plaza, courtyard, or similar pedestrian  area, then at no higher than 20 feet in height, as measured from finished grade, and at each  floor or story above 20 feet its height shall be modulated by adding building elements such as a  wing of the building, trellis, lower roof overhand, horizontal projection at least two feet deep,  awning, balcony, or other architectural feature to reduce the apparent height to a more human  scale.  (2) For structures on lots that are between Bay Street and Prospect Street/Alley and that abut  Bay Street, above 39 feet, the gross floor area shall be not more than 75 percent of the gross  floor area immediately below, which shall be designed and constructed to create view corridors  perpendicular to Bay Street on one or both sides of the structure that rises in excess of 39 feet  in height.  (3) For structures north of Bay Street or south of Bay Street that do not abut Bay Street, above  27 feet, the gross floor area shall be not more than 75 percent of the gross floor area  immediately below, which shall be designed and constructed to create view corridors  perpendicular to Bay Street on one or both sides of the structure that rises in excess of 27 feet  in height.  (4) All view corridors should be located to maximize the views and solar access of neighboring  lots.  20.38.219 DOD – Building facades.   (1) A building facade, whether the front, side, or rear of the building, that exceeds 50 feet in  length shall be broken down into smaller elements by jogging the wall in or out a minimum of  four feet for at least 10 feet of length, or by adding an element such as a porch, recessed entry,  bay window, projecting trellis, or similar substantial architectural feature at least four feet deep  by 10 feet wide by one story high, at intervals so that no continuous wall plane is more than 50  feet in length.  (2) Any sidewalk level building facade that faces a downtown street shall have at least 30  percent of the street level frontage area in transparent glass windows.  (3) Every building north of Bay Street that is on a waterfront lot shall have attractive front  facade qualities on both the street frontage and the side facing the waterfront.   20.38.220 DOD – Service and loading areas.   Dumpsters, loading platforms, storage areas, and similar functions shall be screened from  public rights‐of‐way and adjacent properties by attractive view‐obstructing fencing, dense  landscaping, or other improvements. Screening shall be at least six feet in height and shall be  complementary to building design and materials. The use of a chain link‐slat combination for  fencing is prohibited. On waterfront lots, dumpsters and storage areas shall be located to the  side of the building, and not between the building and the water. Wherever possible, adjoining  property owners are encouraged to designate a common area for dumpsters and storage.     20.38.21621 DOD – Covered walkway.   All development within the central DOD either fronting Bay Street or fronting Sidney Avenue north of  Bay Street shall meet the following additional standard:  (1) Existing City‐Owned Covered Walkway. With respect to property where there is an existing city‐ owned covered walkway, a property owner who is constructing a new building shall either replace the  Page 161 of 260     12      existing city‐owned covered walkway with an identical structure or propose an alternative form of  weather protection such as a canopy, second floor exterior deck, or similar protective structure that  extends not less than five feet over the sidewalk provided it is structurally sound and consistent with the  design guidelines set forth in these regulations. The building owner shall be responsible for maintaining  and repairing any such alternative structure in an attractive manner for the life of the building. Vinyl or  soft plastic canopies shall not be allowed. In addition, a performance bond shall be required in an  amount to be determined by the city engineer so as toto assure that the existing city‐owned covered  walkway on the adjacent properties is not damaged and the new structure is built as designed and  approved.  (2) No Existing City‐Owned Covered Walkway. With respect to property where there is no existing city‐ owned covered walkway, at least 50 percent of the building frontage on either the Bay Street or Sidney  Avenue side of the building located north of Bay Street shall include weather protection in the form of a  canopy, second floor exterior deck, or similar protective structure that extends not less than five feet  over the sidewalk. The building owner shall be responsible for maintaining and repairing any such  alternative structure in an attractive manner for the life of the building. Vinyl or soft plastic canopies  shall not be allowed.     20.38.222 DOD – Building exteriors and materials.   (1) High‐quality materials and colors should bring a visually interesting experience into the  streetscape. Color should be carefully considered in relation to the overall design of the  building and surrounding buildings. Variations in materials and colors should be generally  limited to what is required for contrast or to accentuate architectural features. Piecemeal  embellishments and frequent changes in materials are to be avoided. Building design and  materials should embody the distinctive characteristics of the late nineteenth and early  twentieth centuries.  (2) Exterior building facades should be constructed of high‐quality and durable materials such  as brick, concrete tinted a subdued or earthen color, sandstone, similar stone facing material,  wood siding or other building materials consistent with this section. Aluminum, painted metal,  wood, and other materials may be used for signs, window and door sashes and trim, and for  similar purposes when compatible with adjacent uses. Materials and colors should be used with  consistency on all sides of a building. Materials which are prohibited on the exterior facades  include beveled metal siding, mirrored glass, and vinyl siding.     20.38.21723 DOD – Landscaping requirements.   The general landscape standards set forth in this Title shall apply unless a more restrictive provision is  set forth in the DOD specific landscape standards.    20.38.21824 DOD – Pedestrian walkway requirements.   Pedestrian walkways within the central DOD shall meet the following requirements:  (1) If the subject property is adjacent to a street, it shall provide a pedestrian walkway that shall be  constructed of concrete or unit pavers, a minimum of 10 feet in width as measured from the face of the  street curb to the face of the structure, and shall extend the entire frontage of the property adjacent to  a street. If the pedestrian walkway cannot be accommodated within existing public right‐of‐way, the  difference shall be made up with a public easement over private property or right of way dedication.  Buildings may cantilever over the pedestrian walkways provided the building extension does not  Page 162 of 260     13      overpower the pedestrian space or create a tunnel, cave or similarly confined spatial effect.  Additional  city approvals may be required to allow a building to project into the right of way.  (2) Pedestrian walkways must be visually distinct from parking lot and driveway surfaces and  shall be characterized by concrete or masonry materials. Walkways must be functionally  separate from parking lots and driveways except where the crossings are located. Plans shall  indicate details regarding pedestrian walkway surface treatments, planned interruptions,  widths, course and lighting.    20.38.225 DOD – Design review process.   (1) Application. The design and building standards set forth for the DOD sections of this chapter  (POMC 20.38.200 through 20.38.231) apply to the following activities within the central DOD:  (a) Developing an undeveloped site;  (b) Constructing or locating a new building on a developed site;   (c) Adding a new floor area to an existing building; or  (d) Changing the exterior appearance of over 20 percent of a facade visible from a public right‐ of‐way, park, or the water.  (2) Exemptions. The following activities are exempt from the design review and building  standards set forth in this section:  (a) Any activity which does not require a building permit;  (b) Any activity on the exterior of a building for which the total cost or fair market value,  whichever is higher, does not exceed $5,000;  (c) Interior work which does not alter the exterior of the structure; or  (d) Normal building maintenance including the repair or maintenance of structural members.    20.38.226 DOD – Preapplication meeting.   The proponent of a development project subject to design review shall meet with staff and one  member of the design review board (DRB) at a pre‐application meeting to identify and review  applicable design guidelines. Staff shall identify the appropriate permit process, provide a list of  application materials, and provide design recommendations based upon applicable standards.  This pre‐application meeting shall be part of the overall land use or building preapplication  meeting covering other project‐related issues.     20.38.227 DOD – Application requirements.   Applications for design review shall be submitted to the planning department and shall consist  of a completed application on a form prescribed by the planning department, the appropriate  fee and the following materials:  (1) Preliminary architectural renderings with elevations and details of architectural features,  but not construction ready documents.  (2) The type and finished color of exterior siding, windows and roofing to be used, signs and  trim to the extent known. The applicant is encouraged but not required to provide sample  colors of all factory finished materials.  (3) Site plan (including landscaping details if required) drawn to scale no smaller than one inch  equals 30 feet showing location and size of all structures, buffer areas, yards, open spaces,  Formatted: Space Before: 0 pt, After: 0 pt Formatted: Space Before: 0 pt, After: 0 pt Formatted: Space Before: 0 pt, After: 0 pt Formatted: Space Before: 0 pt, After: 0 pt Page 163 of 260     14      common areas or plazas, walkways, and parking areas sufficiently complete to show  comprehensive project design.  (4) Details on how mechanical and utility equipment will be screened.  (5) Color, type, and specification of all fencing materials.  (6) The type, model, color, location, height, wattage, and area of illumination for all outdoor  light fixtures.  (7) The type, model, location, and color of all outdoor furniture, trash receptacles, accessories,  and such other items as the director of planning deems necessary for effective review.     20.38.228 DOD – Design review procedure and appeals.   After the applicant has attended a preapplication meeting pursuant to POMC 20.38.227 and  submitted a complete design review application pursuant to POMC 20.38.228 then the  development project shall be considered in the following manner:  (1) The planning director shall schedule a meeting with the applicant and the DRB. The planning  department shall send notice of the meeting to property owners within 300 feet of the subject  property. The meeting shall be open to the public and shall consist of a presentation by the  applicant, or his representative, that focuses on how the proposed design meets the criteria of  the applicable design and building standards. The DRB will ask clarifying questions and take  public comment.   (2) The DRB shall review the application materials to determine whether the proposed  development meets the identified standards. The DRB shall provide a written recommendation  to the director for approval, approval with conditions, or denial.  (3) It is possible that an alternative design or departure from the design standards may fulfill  the intent and objectives of the applicable design standards and this chapter, while not  complying with the requirements of those standards. The DRB may recommend approval or  approval with conditions for an application that proposes an alternative design or departure  from the design standards provided:  (a) The recommendation is approved by three‐quarters or more of the appointed members of  the DRB;   (b) The alternative design or design departure is consistent with the purposes, intent, and  objectives of the applicable design standards;  (c) Approval will not constitute a grant of special privilege inconsistent with the limitation upon  uses of properties in the vicinity of the subject property; and   (d) Due to the physical characteristics and/or existing buildings on the site or on abutting  properties, or due to unique characteristics of the site, strict adherence to the applicable design  standards would create an unreasonable hardship for the applicant or would be unsafe.  (4) The applicant may request additional meetings with planning staff or the DRB, for instance,  in circumstances where the applicant has subsequently made extensive revision and desires  reconsideration of his request. Should the proposed development be found to have one or  more standards that have not been successfully addressed, the DRB or staff will work with the  applicant to remedy, if possible, the identified circumstances. If it is not possible to come to a  workable solution, the DRB may recommend denial of the proposal.  Formatted: Space Before: 0 pt, After: 0 pt Page 164 of 260     15      (5) Once the planning director has received the DRB’s recommendation, an open record hearing  before the city council shall be scheduled for the application or both the application and the  underlying permit application.   (6) The DRB’s recommendation shall hold substantial weight. Following the public hearing and  consideration of the DRB’s recommendation, the city council shall grant, deny, or conditionally  approve the design features of the proposed development. Any deviation from the DRB’s  recommendation shall be documented in the city council’s findings and conclusions.  (7) The city council’s decision shall be a final decision and is appealable to Kitsap County  superior court.     20.38.229 DOD – Duration of approval.   (1) Time Limit. Construction on development projects that receive design approval shall  commence within 12 months from the date of design approval, or the city council’s approval  shall be null and void unless the applicant submits a fully completed application for an  extension of time prior to the expiration date. For the purposes of this section, the date of  approval shall be the date on which the city council’s took final action on design approval. In  the event of an appeal, the date of approval shall be the date on which a final decision is  entered by a court of competent jurisdiction.  (2) Time Extension. The applicant may apply for a one‐time extension of up to one year by  submitting a letter, prior to the date that approval lapses, to the planning director along with  any other supplemental documentation which the director may require, which demonstrates  that circumstances beyond the applicant’s control are preventing timely compliance. In the  event of an appeal, the one‐year extension shall commence from the date a final decision is  entered in favor of such extension. The applicant shall include with the letter of request such  fee as the city may require, if any.   (3) Review of Request for Extension. The review of a request for an extension shall be reviewed  by the planning director as an administrative determination.     20.38.230 DOD – Approval runs with the land.   Subject to the time limits set forth in POMC 20.38.230, the design approval for a project shall remain in  force upon a change of ownership of the site, business, or use that was the subject of the permit  application. In the event the new owner desires to change existing design aspects that are otherwise  regulated by applicable design and building standards, then the new owner must submit a new  application for design review and comply with the provisions of this chapter.    20.38.600 Tremont Street corridor overlay district (TRMT) (map designation ‐trmt).   (1). Boundaries. The TRMT is an overlay district which shall be delineated on the city’s official zoning  map.   (2). Purposes. The purpose of the Tremont Street corridor overlay district (TRMT) is to:  a. Provide site development standards which establish minimum regulations for all development  within the specific plan area and which contribute to a high quality of development; and  b. Create an attractive gateway to Port Orchard along one of the primary corridors that visitors  would utilize to reach the downtown city center and waterfront.    Formatted: Space Before: 0 pt, After: 0 pt Formatted: Space Before: 0 pt, After: 0 pt Page 165 of 260     16      20.38.601 TRMT – Compliance with Design Standards.  Compliance with the TRMT standards is required for all new construction of structures and for  modifications to an existing structure whereby the interior square footage of an existing structure is  increased by 50 percent or more.      20.38.602 TRMT – Exemptions.   The following actions are exempt from the TRMT standards:  (1). The modification of existing single‐family structures;  (2). Demolition of existing structures;  (3). Any interior building remodeling or alterations that are not included in POMC Section 16.20.601;  and  (4). The repair of existing structure exteriors provided that exterior materials are replaced in kind or  are brought into compliance with, POMC Sections 16.20.600 through 16.20.633, except where the  threshold in 16.20.601 is met or exceeded.    20.38.603 TRMT – Preapplication meetings encouraged.   All applicants for new development within the TRMT overlay district, except for those actions which are  exempt in POMC 20.38.602, are encouraged to complete a preapplication meeting process with the city  prior to submitting applications for a master development permit and/or building permits. While  preapplication meetings are encouraged, applications for building permits may be submitted at any  time.   20.38.604 TRMT – Project application requirements.  (1) In order to develop property in the TRMT zone, a property owner must obtain a stormwater  management permit and a building permit as required by this Title. A property owner may submit these  permit applications separately or concurrently, but a building permit will not issue prior to approval of  the clearing and grading permit.   (2) At the time the stormwater management permit application is submitted for development in the  TRMT zone, the following materials shall be submitted to make the application complete:   (a) A narrative of the overall project description which demonstrates how it is consistent with the TRMT  design standards and any other applicable city standards, and such other information as will assist in  establishing that the proposal meets the TRMT requirements and purposes.  (b) A site development plan, which consists of:   (i) Vicinity map with adjoining street location and names;  (ii) Property boundaries and directions;  (iii) Public and private easements;   (iv) Adjacent land uses for site context purposes;   (v) Proposed building envelopes for all structures including proposed entryway locations and building  orientation to streets;  (vi) A landscape plan including plant lists by name; quantities and size of plantings including the  identification of existing significant trees (over 36 inches in diameter) to be retained; and landscape  perimeter and screen;  (vii) A parking and access plan including: parking entry location from the street; entry construction  details; stall types delineated and dimensioned; location of disabled parking; and parking tabulation  information including shared parking with adjoining uses (within 100 feet).  (c) In addition to the elements of a complete building permit application, building permit applications for  development in the TRMT shall additionally include the following drawings:  (i) Building elevations;  Page 166 of 260     17      (ii) Refuse container enclosure and gate details;  (iii) Wall sections and details; and  (iv) The type and finished color of exterior siding, windows and roofing to be used, signs and trim to the  extent known.   20.38.605TRMT – Review process.  The permit processing requirements for stormwater management permit applications are described in  Chapter 20.150 POMC. The permit processing requirements for building permit applications are  described in Subtitle II.   20.38.606 TRMT – Appeals.  The hearing examiner’s decision with regard to a TRMT permit shall be appealable to the city council.  The city council shall be the city’s final action for the purpose of any and all appeals.    20.38.608 TRMT – Front yard setbacks.   Front yard setbacks shall be 20 feet for all buildings. Monument signs may encroach into a front yard  setback provided they are set back at least five feet from the front property line and any sidewalk. No  parking may encroach into the front yard setback. All front yard setbacks shall be landscaped.    20.38.609 TRMT – Side yard setbacks.   No side yard setback is required except in the following conditions:  (1) Where adjacent to a residential district or land use a 10‐foot side yard setback is required.   (2) Where the side yard is adjacent to a public street, the building setback shall be 10 feet. Parking areas  and monument signs may encroach into a side yard setback provided they are set back at least five feet  from the side property line and any sidewalk. All side yard setback areas shall be landscaped.     20.38.610 TRMT – Rear yard setbacks.   No rear yard setback is required except in the following conditions:  (1) Where adjacent to a residential district or land use, then a 15‐foot rear yard setback is required.   (2) Parking and monument signs may encroach into a rear yard setback provided they are set back at  least five feet from the rear property line. All rear yard setbacks shall be landscaped.     20.38.611 TRMT – Lot coverage.   The maximum allowable lot coverage by structures shall be 100 percent for commercial/office uses less  required parking area, landscaping, and setbacks. Residential and multiple‐family developments shall  conform to lot coverage found within their respective zone designations.     20.38.612 TRMT – Minimum street frontage.   The minimum street frontage for any commercial/office development shall be no less than 100 feet. If  necessary, lots of 150 feet or less shall design parking facilities to adjoin future adjacent developments  (combined street access).     20.38.613 TRMT – Building height.   The maximum building height shall be 33 feet as measured to the top of the gable or pitch of the roof.  Uninhabited architectural elements such as spires, towers or rooflines may extend to 35 feet.     20.38.614 Blank walls.   (1) Blank Wall Definition. A wall (including building facades and retaining walls) is considered a blank  wall if:   Page 167 of 260     18      (a) A ground floor wall or portion of a ground floor wall over six feet in height has a horizontal length  greater than 15 feet and does not include a transparent window or door; or   (b) Any portion of a ground floor wall having a surface area of 400 square feet or greater and does not  include a transparent window or door.   Figure: Blank Wall Definition.  (2) Blank Wall Standards. Untreated blank walls visible from a public street or pedestrian pathway are  prohibited. Methods to treat blank walls can include:   (a) Display windows at least 16 inches of depth to allow for changeable displays. Tack on display cases  shall not qualify as a blank wall treatment.   (b) Landscape planting bed at least five feet wide or a raised planter bed at least two feet high and three  feet wide in front of the wall with planting materials that are sufficient to obscure or screen at least 60  percent of the wall’s surface within three years.   (c) Installing a vertical trellis in front of the wall with climbing vines or plant materials.   (d) Special building detailing that adds visual interest at a pedestrian scale. Such detailing must use a  variety of surfaces; monotonous designs will not meet the intent of the standards. For large visible blank  walls, a variety of treatments may be required to meet the intent of the standards.   Figure: Blank Wall Treatment Examples.       Good and bad blank wall treatment examples. Image A illustrates that heavy landscaping can be very  effective in treating a large blank wall. Image B uses a combination of planted trellises and display ads  integrated with the building’s architecture along a facade facing a drive‐through. Image C simply doesn’t  use enough treatments and the result is a stark and unwelcome streetscape.    20.38.615 TRMT – Building walls and modulation.   All buildings which contain two stories or have a building footprint of more than 10,000 square feet or  which have facade length greater than 100 feet and which are visible from a public street or located  within 100 feet of a residential zone shall use the following elements and features in design and  construction of the building:  Page 168 of 260     19      (1) No wall plane visible from any public right‐of‐way shall be wider than two and one‐half times the  height of the wall plane (a wall plane is a flat vertical surface on a building facade, which may include  doors, windows, openings, or other incidental recessions that do not extend through to the roofline).  (2) Any wall or portion of a wall which is visible from a public street must contain 35 percent surface  transparency.   (3) All building walls shall provide horizontal modulation consistent with the following standards:  (a) The maximum allowable horizontal length of a building wall between modulations is 100 feet;  (b) The minimum depth of each modulation is three feet; and   (c) The minimum width of each modulation is 15 feet.   (d) As an alternative treatment, horizontal modulation may be provided by installation of one stand of  trees for each required modulation, located within 20 feet of that portion of the building wall requiring  modulation.     20.38.616 TRMT – Roofline modulation.   (1) Rooflines visible from a public street, open space, or customer parking area must be varied by  emphasizing dormers, gables, stepped roofs, prominent cornice or fascia, or a broken or articulated  roofline. The width of any continuous flat roofline should extend no more than 100 feet without  modulation. Modulation should consist of either:   (a) For flat roofs or facades with a horizontal eave, fascia, or parapet, the minimum vertical dimension of  roofline modulation is the greater of two feet or one‐tenth multiplied by the wall height (finish grade to  top of wall). The required change in elevation noted above may be reduced by approximately one‐half  provided the roofline change corresponds with a change in building materials.  (b) A sloped or gabled roofline segment of at least 20 feet in width and no less than three feet vertical in  12 feet horizontal.  (c) A combination of subsections (1)(a) and (b) of this section.  (2) All roof equipment shall be screened from public view. Mechanical equipment should be located  below the highest vertical element.     20.38.617 TRMT – Windows and awnings.   (1) Large, continuous expanses of glass shall provide detailing such as subdivisions by mullions, panes, or  decorative millwork.  (2) Horizontal repetition of single windows over long distances is to be avoided.  (3) The use of bay, bow and box windows is encouraged.  (4) Tinted glass may be used to reduce solar gain; however, deeply tinted glass which stops interior  views is to be avoided. Mirrored glass or highly reflective glass is prohibited. Electro‐chromatic windows  are permitted.  (5) Window frames may be constructed of materials including steel, anodized aluminum, wood, wood  and metal and vinyl‐covered wood; silver, gold and other bright‐colored frames should be avoided in  favor of natural colors.  (6) Window awnings along a row of contiguous buildings shall be restricted to the same form and color.  Awnings shall maintain an eight‐foot minimum vertical clearance. Plexiglas and glossy vinyl illuminated  awnings are prohibited. Canvas, treated canvas, matte finish vinyl, and fabric awnings are encouraged.     20.38.618 TRMT – Building design.   (1) Multiple‐tenant office buildings shall be clustered and designed with common materials, colors and  styles across their entire facades so as to create cohesive building designs. However, they can be  characterized by variation in the application of said materials and colors and also in fenestration details.  Page 169 of 260     20      For example, siding materials or colors may be alternated between building sections; provided, that no  single section be of a material or color that is not found on other portions or elements of the facade  design. Accent siding materials and prominent siding materials may also be reversed to create interest.  Tenant‐specific motifs are prohibited if they do not reflect the style, colors and materials that  characterize the overall facade design. For purposes of this section, a single building is defined as any  structure that is not completely separated from another structure by at least a 10‐foot distance.   (2) Common materials, colors and styles are encouraged for multiple buildings on a single site; however,  each building shall be unique in terms of its general massing design and fenestration design. Variety in  design may be achieved by variation in each building’s footprint, rooflines, facade modulation, and  window arrangement. Color and materials may also be varied.  (3) Buildings greater than 40,000 square feet in area shall use one or more of the following elements in  an effort to reduce the appearance of excess bulk in large buildings:  (a) Variety in surface planes of exterior walls in depth or direction;  (b) Variety of the height of the building so it appears to be divided into separate distinct sections;  (c) Articulation in different parts of the building’s facade by use of color, change in materials, and  arrangement of elements;  (d) Use of landscape and pavement materials at ground level to encourage the transition from building  to parking areas;  (e) Use of building trellises, wall articulation, change in materials, arcades, or other features.  (4) To enhance the pedestrian scale of any new development or redevelopment, buildings must:   (a) Provide project‐appropriate details including window patterns, structural bays, roof overhangs,  siding, awnings, moldings, fixtures, and other details.  (b) Include pedestrian connections between new and existing pedestrian areas (i.e., plazas, courtyards,  street sidewalks) and new and existing buildings.   (c) Create transitions in bulk and scale between large buildings and adjacent smaller buildings through  the use of appropriately scaled landscaping, fencing, art or other structures.   (d) Provide overhead weather protection and interior lot pedestrian oriented lighting.  (e) Public sidewalks shall be separated from the public roadway through use of landscape planting strips,  parking bulb‐outs and street furnishings where appropriate.  (f) Pedestrian walkways internal to the site shall be a minimum of six feet in width.   (g) At least one building entrance shall face each public street frontage on a corner lot but in any event,  no building shall be required to have more than two front entrances. A corner entrance shall count as  two entrances when it faces two public street frontages. Directly linking pedestrian access shall be  provided between the street right‐of‐way and each building entrance.     20.38.619 TRMT – Siding materials.   Acceptable siding materials include brick, stone, split‐face cement block, shingles, and horizontal lap  siding. Other materials may also be used if:   (1) They are used as accent materials in conjunction with acceptable siding materials; or   (2) Singular materials are characterized by details or variations in the finish that create a regular pattern  of shapes, indentations, or spaces that are accented or highlighted with contrasting shades of color.     20.38.620 TRMT – Landscape standards.   The general landscape standards set forth in Subtitle VI shall apply unless a more restrictive provision is  set forth in the TRMT specific landscape standards set forth in Chapter 20.128.230 POMC through  20.138.239.     Page 170 of 260     21      20.38.627 TRMT – Utilities.   Underground utilities shall be installed for all new development.     20.38.628 TRMT – Parking and circulation standards.   The general parking standards set forth in Subtitle VI shall apply unless a more restrictive provision is set  forth in the TRMT specific parking standards set forth in POMC **.     20.38.633 TRMT – Signs.   All permanent freestanding signs within the Tremont Street corridor overlay district shall be of  monument type. Pole signs are prohibited. All other applicable conditions of Chapter ** POMC shall  govern the placement of signs within the TRMT.       Chapter 20.100  DEVELOPMENT STANDARDS—DESIGN GUIDELINES    20.100.010 Purpose.  (1) The purpose of this section is to ensure that developments are compact, pedestrian‐friendly, provide  necessary infrastructure and services, and contribute to the character of the town and surrounding  neighborhoods,  by providing building and site design standards that:  (a) Reduce the visual impact of large residential buildings from adjacent streets and properties;  (b) Enhance the aesthetic character of large residential buildings;  (c) Contain sufficient flexibility of standards to encourage creative and innovative site and  building design;  (d) Meet the on‐site recreation needs of project residents;  (e) Enhance aesthetics and environmental protection through site design; and  (f) Allow for continued or adaptive re‐use of historic resources while preserving their historic  and architectural integrity.  (2) These guidelines do not alter the land uses or densities allowed in the underlying zoning districts  defined in this code. Projects shall comply with all relevant criteria set forth in this chapter.     20.100.020 Block and lot layouts.  (1) Blocks should have sufficient width to provide for a maximum of two tiers of lots of appropriate  depths. Exceptions should be permitted in blocks adjacent to major streets, railroads, waterways, or  involving unique site conditions that make this requirement impractical.  (2) Lots to be created within a proposed site plan or subdivision should comply with the following  requirements:   (a) Every lot should have a minimum frontage of 25 feet on a public or privately dedicated right‐of‐way.  A repair and maintenance access should be provided to all lots by site plan or plat easement and  property deed. Required easements shall be shown on the face of the site plan or plat.  (b) Lot lines should be at right angles to street lines or radial to curvilinear streets unless a variation will  result in a better street or lot plan.  (c) Dimensions of corner lots should be large enough to allow for front yard setbacks off both streets.  (d) Corner lots should be graded to provide sufficient sight clearance at intersections.     20.100.030 Roadway elements.  (1) Right‐of‐Way Dedications.   Formatted: Space After: 0 pt, Line spacing: single Page 171 of 260     22      (a) All site plans and subdivisions should provide direct access to at least one existing improved and  publicly dedicated street.  (b) When a proposed site plan or subdivision is abutting an existing street or streets with a right‐of‐way  of lesser width than specified by city code, the applicant may be required as a condition of approval to  deed additional right‐of‐way width and to improve said right‐of‐way to the design specifications of the  city engineer. The city may require dedication of right‐of‐way in excess of standards in the following  cases:  (i) Where additional width is necessary to maintain continuity with the adjoining rights‐of‐way; and   (ii) Where additional width is necessary to maintain alignment with adjoining streets and sidewalks  improvements or to allow for provision of sidewalks or bicycle facilities.  (iii) Dead‐end streets shall be used on access streets only and shall terminate in a cul‐de‐sac. Streets  which dead‐end and which would normally be continued if the adjacent property were developed  should be shown as temporary turnarounds. The land beyond the normal right‐of‐way for such streets  shall revert to the abutting property owners when the street is continued.  (c) Half‐streets shall not be allowed.  (2) Street Layouts.  (a) The street within and adjacent to a site plan or subdivision should be classified and designed to  comply with the road standards as adopted by city resolution or ordinance, comprehensive plan and  major street map of the city. Major streets should refer to designated arterial and collector streets and  minor streets should refer to access streets and cul‐de‐sacs.  (b) Proposed streets should extend to the boundary lines of the proposed site plan or subdivision in  order to provide for the future development of adjacent tracts unless prevented by natural or manmade  conditions or unless such extension is determined to be unnecessary or undesirable by the planning  commission or city council.  (c) The street pattern for commercial site plans and subdivisions should be designed to expedite traffic  movement, reduce conflicts between various types of land uses including pedestrian and bicycle access,  and coordinate the location of proposed buildings with vehicular loading and parking facilities. To the  extent practical and feasible, commercial site plans should provide common driveways and integral  access through or between the property and adjacent properties and surrounding residential  neighborhoods.  (d) The street pattern for industrial site plans and subdivisions should be designed to expedite traffic  movement, reduce conflicts between various types of land uses including pedestrian access, and  coordinate the location of proposed buildings with airport, railroad, waterfront, and vehicular loading  and parking facilities.  (3) Street Signage. Public street names shall conform to the city of Port Orchard system. Street signs  shall be installed as designated by the city engineer before final site plan or plat approval.     20.100.040 Site plan elements.  (1) Grading and Storm Drainage.   (a) Structures, roadways, and other site improvements should be designed to blend with the natural  topography with the minimum amount of site disturbance and grade changes. Large cuts and fills  requiring tall or long retaining walls or rockeries may be allowed at the City’s discretion.  (b) Major drainage corridors and detention facilities should be graded and landscaped to blend with the  natural landscape in accordance with the provisions of Chapter 15.32 POMC. Where possible,  stormwater facilities should be incorporated into the site’s design as aesthetic amenities, enhanced  portions of walkway or trail corridors, and/or special visual accents.   Formatted: Space Before: 0 pt, After: 0 pt Page 172 of 260     23      (c) Where retention/detention ponds are highly visible or used as a design feature, water levels within  the pond should be maintained during the dry season for visual accent purposes.  (2) Landforms and View Sheds.  (a) Buildings should be fit into the existing topography to appear to be an integral part of the natural  landform. On sloping sites, buildings should be stepped into the slope to reflect the sloping grade.  (b) Buildings should be placed to preserve and frame views of natural features including the waterfront  and mountain ranges, and significant townscapes including the downtown and significant architectural  landmarks from other properties within the surrounding view shed.  (3) Parking Lots and Areas.  (a) Parking areas or lots should be located along the side, rear or in courtyard configurations to retain a  building frontage along road corridors and control the scale of the streetscape.  (b) Parking lot aisles should be aligned perpendicular to commercial, retail, and office building entries to  provide protected walking spaces and visual focus on building entrances.   (c) Where feasible, parking lots should be varied in grade, bermed, and/or differentiated with planting  materials to reduce the visible extent of paved surfaces and to manage stormwater.   (d) Parking structures should be integrated into surrounding buildings or streetscapes using facades,  artworks, landscaping, or other means that visually filter the view of parked cars from pedestrian  walkways and trails, adjacent building occupants, and the commercial roadway.  (e) Downtown streets will be reserved for short‐term, customer oriented parking spaces, particularly  during off‐peak traffic hours and prime retail hours and events. Where possible and practical, loading  activities should be accomplished from a side street or back property location to reserve through access  streets for customer parking use.     20.100.050 Streetscape elements.  (1) Walkways and Trails.   (a) Buildings should front onto walkways or trails to be developed within each district in accordance with  the nonmotorized transportation element of the comprehensive plan.   (b) The walkways or trails should be incorporated into the site development as the principal, publicly  accessible pedestrian space and design focus of the development and between the development and  adjacent properties and surrounding residential neighborhoods.  (c) The walkways or trails should integrally connect each development, particularly retail and  commercial projects, with adjacent properties and residential neighborhoods.  (d) The walkways or trails should extend through parking lots and parking areas in separated medians or  other placements that protect pedestrians from vehicular traffic.  (2) Walkway and Trail Corridor Zones. A minimum width of five feet of any walkway or trail corridor will  be clear of any temporary furnishings in order to accommodate pedestrians. The periphery sections of  the corridors, which may be combined on one side, may be used to display advertising signage, flower  pots or other moveable plantings, and/or outdoor seating areas on a temporary, special event basis.   (3) Building Entry and Access.  (a) Building entry and access shall be provided within the private property beyond the public walkway or  trail corridor.   (b) Vestibules and other recessed areaways should be used to define and provide pedestrian access  apart from the public walkway space. Vestibules and recessed areaways should visually alert pedestrians  within the public walkway or trail corridor and be sufficiently attractive to invite visual interest.  (4) Outdoor Activities.  Formatted: None, Space Before: 0 pt, After: 0 pt Formatted: Space Before: 0 pt, After: 0 pt Page 173 of 260     24      (a) As an amenity, ground floor outdoor spaces such as plazas, squares, eating, seating areas, and/or  retail alcoves and inner courtyard spaces or greens should be provided as integral parts of the  development.   (b) The ground floor outdoor spaces should adjoin and be accessible from, and may occasionally be  permitted to spill over into, the public walkway or trail corridor space – but may not include permanent  improvements or uses of the public walkway or trail corridor space.  (5) Streetscape Furnishings.   (a) Improvements to the public walkway or trail corridor spaces may utilize the public streetscape  furnishings palette selected for the corridor.   (b) Improvements to the adjoining private spaces should incorporate or continue the materials, colors,  and/or styles of the public furnishings palette in order to provide design continuity.  (c) Where appropriate, project developments should provide pedestrian scaled lighting fixtures to  illuminate walkways, trails, parking areas, and other people spaces. Lighting shields should direct  illumination onto pedestrian spaces and away from adjacent properties or uses. Freestanding fixtures  should not exceed 14 feet in height.   (6) Public Artworks.  (a) Building and property developments should incorporate outdoor artwork.   (b) Artwork may be permanently incorporated into functional areas that are accessible to the public  including parking lots, accessory buildings and structures, as well as building entries.   (c) Where the building or site is of historical or cultural interest, interpretive signage and other exhibits  or monuments should be incorporated into building or site improvements that are physically and  visually accessible to the public.     20.100.060 Commercial and Mixed‐Use Design Guidelines.  (1) Building Frontages.  (a) Buildings that face onto commercial parking streets and/or public walkway and trail corridors should  be built to front onto the pedestrian space or activity area to create continuous frontages of interest to  the corridor.   (b) Buildings may abut or share common sidewalls subject to International Building Code (IBC), fire code  and emergency access requirements.  (2) Building Heights. Building elevations facing public areas should incorporate offsets, modulations, and  additional setbacks above the second story to reduce massing at the pedestrian scale. The purpose of  this is to prevent imposing or tunnel‐like effects and to visually break up long, continuous facades. It also  encourages more aesthetically pleasing architecture.   (3) Modulation and Articulation.  (a) Building elevations should be horizontally modulated in no larger than 40‐ to 60‐foot increments to  create architectural relief and interest.   (b) Vestibules, entries, and other architectural adaptations should provide further visual definition and  reduce the mass of larger commercial and industrial structures.    (4) Building Entries.  (a) Building entrances should be visually defined from access walkways, fronting streets, and parking  areas. Building designs may use columns, arches, porches, recesses, or other concepts to create  architectural focus and interest.   (b) The principal building entrance should be accessed from major walkways or trail corridors or other  pedestrian ways, or otherwise address the street, opposed to the building’s parking lots and access  roads.  (5) Ground Floor Activities – Mixed Use Developments.   Formatted: Space Before: 0 pt, After: 0 pt Page 174 of 260     25      (a) First or ground floors should be devoted to retail, commercial or a similar public use with pedestrian  appeal where the building fronts onto a commercial street or the public pedestrian walkway or trail  corridor. Activities that serve the elderly or handicapped may be located or accessed from the ground  floor or street level of proposed developments.  (b) Upper floors may be commercial or office where the building has a double frontage, but should be  residential where the building is not publicly accessible.   (c) The first or ground floor should be at least 12 feet and preferably 14 feet in height where the ground  floor use is retail or commercial, and the building fronts onto a commercial street or the public  pedestrian walkway or trail corridors.   (d) Upper floors may be 10, 12 or 14 feet in height depending on occupant uses and exterior  appearances.   (6) Upper Floor Balconies, Alcoves, Decks. Upper floors should incorporate balconies, alcoves, decks or  other outdoor spaces to provide an amenity and increase visual definition to the building – particularly  of the building frontages that face onto commercial streets and the public pedestrian walkway or trail  corridors.   (7) Awnings and Canopies.  (a) As an amenity, commercial or retail developments may provide permanent or retractable awnings,  overhangs, arcades or skylights sheltering pedestrians and shoppers from the elements where the public  walkway or trail corridor traverses through the site.   (b) The design of awnings and canopies should provide natural lighting and openness and continuous  protection from the elements but not overly obscure or shadow the walkway or trail corridor.   (c) Awnings or canopies should be hung above the display window space at least 10 to 14 feet above the  public walkway with a minimum eight‐foot vertical clearance.   (d) Structural supports for awnings or canopies will be provided from the building or adjacent private  property. Such awnings or canopies may be supported by posts or columns within the public walkway or  trail corridor with variance approval.   (8) Display Windows.  (a) Ground floor retail and commercial spaces along the public walkway or trail corridors should provide  display window space to showcase commercial, retail or other public uses and wares in a storefront  style typical of main street or marketplace architecture. Window space coverings should be translucent  materials to provide pedestrians views into ground floor spaces and activities.  (b) The corners of buildings that are located at the intersections on commercial streets and principal  public walkway or trail corridors should provide some form of visual interest such as window displays,  artwork or signage.  (9) Accessory Buildings. Independent parking structures, storage buildings or other accessory enclosures  should be designed to complement the principal, adjacent buildings in form, detail, color, and material.  Generally, accessory buildings and structures should be designed with similar or complementary roof  slopes and building materials as the primary structure.  (10) Rooftop Equipment. Roof‐mounted mechanical equipment and other accessories that are not to be  accessed or viewed from adjacent properties or public corridors should be screened and integrated into  the building structure and shell.  (11) Solar Orientations. Building designs, particularly within new developments, should be located to  maximize the use of passive solar potentials. Where possible, major window areas and outdoor activities  should be oriented along the south‐facing facades and yards.         Page 175 of 260     26      CHAPTER 20.124  PARKING    20.124.010  Development Standards—Parking—Purpose.  (1) Purpose. The purpose of this chapter is to set standards that provide adequate parking for all uses  allowed in this section; to reduce demand for parking by encouraging alternative means of  transportation including public transit, rideshare, and bicycles; and to increase pedestrian mobility in  urban areas by:  (a) Setting minimum off‐street parking standards for different land uses that assure safe,  convenient, and adequately sized parking facilities within activity centers.  (b) Providing incentives to rideshare through preferred parking arrangements.  (c) Providing for parking and storage of bicycles.  (d) Providing safe direct pedestrian access from public rights‐of‐way to structures and between  developments.  (e) Requiring uses which attract large numbers of employees or customers to utilize transit and  provide transit stops.     20.124.020 Development Standards—Parking—Authority and application.  (1) Before an occupancy permit may be granted for any new or enlarged building or to a change to a  different use in any existing building that involves additional parking, the use shall be required to meet  the provisions of this chapter.  (2) Parking studies by individuals with expertise in traffic and parking analysis may be required by the  planning director. If this chapter does not specify a parking requirement for a land use, the planning  director shall establish the minimum requirement based on a study of anticipated parking demand. In  the study, the applicant shall provide sufficient information to demonstrate that the parking demand for  a specific land use will be satisfied.   (3) If the required amount of off‐street parking has been proposed to be provided off‐site, the applicant  shall provide written contracts with affected landowners showing that required off‐street parking shall  be provided in a manner consistent with the provisions of this chapter. The contracts shall be reviewed  by the planning director for compliance with this chapter, and if approved, the contracts shall be  recorded with the Kitsap County auditor as a deed restriction on the title to all applicable properties.  These deed restrictions may not be revoked or modified without authorization by the planning director  or planning commission.  (4) Development along both sides of Bay Street from the crosswalk at Harrison Avenue to Orchard  Avenue is exempt from the parking requirements of this chapter.  (5) In lieu of on‐site parking, bed and breakfast facilities may obtain an on‐street parking permit to  satisfy the facility’s minimum parking requirements as follows:  (a) Applicant for any on‐street parking permit complies with the provisions of Chapter 10.14  POMC.  (b) No more than three on‐street parking permits are issued per facility.  (c) For each on‐street parking permit requested, applicant establishes to the satisfaction of the  city planning director that on‐site parking is not feasible.  (d) Applicant satisfies all other requirements for bed and breakfast facilities as required by city  code or ordinance.     20.124.030 Development Standards—Parking—Off‐street parking spaces requirement.  Page 176 of 260     27      (1) Off‐street parking areas shall contain at a minimum the number of parking spaces set forth in Table  20.124.250. Off‐street parking ratios expressed as number of spaces per square feet means the gross  square footage of floor area. If the formula for determining the number of off‐street parking spaces  results in a fraction, the number of off‐street parking spaces shall be rounded to the nearest whole  number with fractions of 0.50 or greater rounding up and fractions below 0.50 rounding down.  (2) An applicant may request a modification of the minimum required number of parking spaces by  substantiating that parking demand can be met with a reduced parking requirement. In such cases, the  planning director may approve a reduction of up to 50 percent of the minimum required number of  spaces.  (3) When the city has received a shell‐and‐core building permit application, off‐street parking  requirements shall be based on the possible tenant improvements or uses authorized by the zone  designation and compatible with the limitations of the shell‐and‐core permit. When the range of  possible uses result in different parking requirements, the planning director will establish the amount of  parking based on a likely range of uses.  (4) Bicycle parking may be required in accordance with the following provisions:   (a) Off‐street parking areas shall contain at least one bicycle parking space except as follows:  (i) The director may reduce or eliminate bike rack parking facilities for patrons when it is  demonstrated that bicycle activity will not occur at that location or is not safely accessible.  (ii) The director may require additional spaces when it is determined that the use or its  location will generate a high volume of bicycle activity. Such a determination will include but not  be limited to the following uses:  (A) Park and playfield;  (B) Marina;  (C) Library, museum, or arboretum;  (D) Elementary or secondary school;  (E) Sports club; or  (F) Retail business, when located along a developed bicycle trail or designated  bicycle route.  (b) Bicycle facilities for patrons shall be located on site and shall be designed to allow either a  bicycle frame or wheels to be locked.  (c) All bicycle parking and storage shall be located in safe, visible areas that do not impede  pedestrian or vehicle traffic flow, and shall be well lighted for nighttime use.     20.124.040 Development Standards—Parking—Shared parking requirements.  The amount of required off‐street parking may be reduced by an amount determined by the director  when shared parking facilities for two or more uses are proposed, provided:  (1) The total parking area exceeds 5,000 square feet.  (2) The parking facilities are designed and developed as a single on‐site common parking facility, or as a  system of on‐site and off‐site facilities, if all facilities are connected with improved pedestrian paths.   (3) No building or use involved is more than 1,000 feet from the most remote shared facility.   (4) The amount of the reduction shall not exceed 10 percent for each use, unless:  (a) The normal hours of operation for each use are separated by at least one hour; or  (b) A parking demand study is prepared by a qualified individual and submitted by the applicant  documenting that the hours of actual parking demand for the proposed uses will not conflict and that  uses will be served by adequate parking if shared parking reductions are authorized.   (5) The total number of parking spaces in the common parking facility is not less than the minimum  required spaces for either use.  Page 177 of 260     28      (6) A covenant or other contract for shared parking between the cooperating property owners shall be  approved by the planning director. This covenant or contract must be recorded with the Kitsap County  auditor as a deed restriction on both properties and cannot be modified or revoked without the consent  of the planning director.  (7) If any requirements for shared parking are violated, the affected property owners shall provide a  remedy satisfactory to the planning director or provide the full amount of required off‐street parking for  each use, in accordance with the requirements of this chapter.    20.124.050 Development Standards—Parking—Exceptions for community residential facilities (CRF).  (1) The requirement for off‐street parking space per bedroom may be reduced to no less than 50  percent of the requirement per bedroom, as determined by the planning director based on one or more  of the following considerations:  (a) Availability of private, convenient transportation services to meet the needs of the CRF  residents.  (b) Accessibility to and frequency of public transportation.  (c) Pedestrian access to health, medical, and shopping facilities.  (2) If a CRF facility is no longer used for such purposes, additional off‐street parking spaces shall be  required in compliance with this chapter prior to the issuance of a new certificate of occupancy.   20.124.060 Development Standards—Parking—Handicapped parking requirements.  Off‐street parking and access for physically handicapped persons shall be provided in accordance with  the current Revised Code of Washington standards.     20.124.070 Development Standards—Parking—Stacking spaces for drive‐through facilities.  (1) A stacking space shall be an area measuring eight feet by 20 feet with direct forward access to a  service window of a drive‐through facility. A stacking space shall be located to prevent any vehicle from  extending onto the public right‐of‐way or interfering with any pedestrian circulation, traffic  maneuvering, or other parking space areas. Stacking spaces for drive‐through or drive‐in uses may not  be counted as required parking spaces, except as defined in POMC 20.124.030.  (2) Uses providing drive‐up or drive‐through services shall provide vehicle stacking spaces in the  following serial or combined sequence per lane of drive‐up window; such required spaces shall include  the drive‐up window space itself:  (a) For each service window of a drive‐through restaurant, a minimum of five stacking spaces  shall be provided.  (b) For all other uses, each drive‐up window requires a minimum of three stacking spaces.     20.124.080 Development Standards—Parking—Transit and rideshare provisions.  To support the use of ridesharing as an alternative mode of transportation that will aid the city in its  efforts to reduce air pollution, traffic congestion, and fossil fuel consumption, the following shall apply:  (1) All land uses with 25 employees working at any given work site during a single work shift listed under  the government/business services and manufacturing tables shall be required to reserve parking spaces  for registered rideshare vehicle parking as follows:  (a) There shall be a minimum of one open parking space reserved for an employee rideshare  vehicle, and all registered rideshare vehicles shall have a reserved parking space.  (b) A vehicle parked in a rideshare vehicle only parking space must be registered in Kitsap  Transit’s countywide public rideshare vehicle registration program, qualify as a rideshare vehicle as  defined by Kitsap Transit, and display a valid car/vanpool pass.  Page 178 of 260     29      (c) Each rideshare vehicle parking space shall be clearly labeled with a Kitsap Transit carpool or  vanpool parking sign.  (d) Except for disabled parking spaces, rideshare vehicle parking spaces shall be located closer to  the primary employee entrance than any other employee parking spaces.  (2) When one or more scheduled transit routes provide service within 660 feet of the employment site  and there is designated pedestrian access, the planning director may reduce the number of required off‐ street parking spaces.  (3) All uses which are located on an existing transit route and are required under the computation for  required off‐street parking to provide more than 200 parking spaces may be required to provide transit  shelters, bus turnout lanes or other transit improvements as a condition of permit approval. Uses that  reduce required parking pursuant to subsection (2) of this section may provide transit shelters if transit  routes adjoin the site.     20.124.090 Development Standards—Parking—Pedestrian circulation and access.  The following general pedestrian design standards shall apply to all developments throughout the city in  addition to those outlined elsewhere within the special design districts:   (1) All uses, except single‐family detached buildings, shall provide pedestrian access onto the site.  Pedestrian access shall be located as follows:  (a) Access points at property edges and to adjacent lots shall be coordinated with the existing  development to provide circulation patterns between development sites. Pedestrian access to adjacent  lots shall not be required if the topography is greater than three percent between the lots.  (b) Residential developments shall provide links between cul‐de‐sacs or groups of buildings to  allow pedestrian access from within the development and from adjacent developments to activity  centers, parks, common tracts, open spaces, schools or other public facilities, transit stops, and public  streets.  (2) Pedestrian walkways shall minimize the conflict between pedestrians and traffic at all points of  pedestrian access to on‐site parking and building entrances as follows:   (a) All developments which contain more than one building shall provide walkways between the  principal entrances of the buildings.  (b) Pedestrian walkways across parking areas shall be located as either one of the following:  (i) Walkways running parallel to the parking rows shall be provided at a minimum of  every two parking lot aisles.   (ii) Walkways running perpendicular to the parking rows shall be no further apart than  25 parking spaces.   (3) Pedestrian access and walkways shall meet the following minimum design standards:  (a) Access and walkways shall be physically separated from driveways and parking spaces by  landscaping, berms, barriers, grade separation or other means to protect pedestrians from vehicular  traffic. Lighting may be required.  (b) Access and walkways shall be a minimum of 60 inches of unobstructed width and meet the  surfacing standards of the Port Orchard road standards for walkways or sidewalks.  (c) Access shall be usable by mobility‐impaired persons and shall be designed and constructed to  be easily located by the sight‐impaired pedestrian by grade change, texture or other equivalent means.  (d) A crosswalk shall be required when a walkway crosses a driveway or a paved area accessible  to vehicles.  (e) Wherever walkways are provided, raised crosswalks or speed bumps may be located at all  points where a walkway crosses the lane of vehicle travel.     Page 179 of 260     30      20.124.100 Development Standards—Parking—Off‐street parking design standards.  (1) The most distant parking space shall not be located more than 500 feet away from the nearest  building entrance it is required to serve. Where the off‐street parking areas do not abut the buildings  they serve, the required maximum distance shall be measured from the nearest building entrance that  the parking area serves:  (a) For all nonresidential uses permitted in residential zones, the parking spaces shall be located  on the same lot they are required to serve and at least a portion of parking areas shall be located within  150 feet from the nearest building entrance they are required to serve.  (b) For all uses permitted within downtown mixed use district (Mxd), the parking spaces may be  located on consolidated off‐site parking lots distributed at accessible locations about the downtown  district.  (2) Minimum parking space and aisle dimensions shall be determined by the planning director.  Regardless of the parking angle, one‐way aisles shall be at least 10 feet wide, and two‐way aisles shall be  at least 20 feet wide. Parking plans for angle parking shall use space widths no less than eight feet, six  inches for a standard parking space design and eight feet for a compact car parking space design.  (3) Any parking spaces abutting a landscaped area on the driver or passenger side of the vehicle shall  provide an additional 18 inches above the minimum space width requirement to provide a place to step  other than in the landscaped area. The additional width shall be separated from the adjacent parking  space by a parking space division stripe. The parking space depth may be reduced when vehicles  overhang a walkway under the following conditions:  (a) Wheelstops or curbs are installed.  (b) The remaining walkway provides a minimum of 60 inches of unimpeded passageway for  pedestrians.  (4) The amount of space depth reduction is limited to a maximum of 18 inches.  (5) Ingress and egress between off‐street parking areas and abutting streets shall be designed, located,  and constructed in accordance with Port Orchard street standards.   (6) Lighting of off‐street parking areas shall be provided for safety of traffic and pedestrian circulation on  the site, as specified in the International Building Code. Lighting shall be designed to minimize direct  illumination of abutting properties and adjacent streets. The planning director shall have the authority  to waive the requirement to provide lighting.  (7) Tandem or end‐to‐end parking is allowed in single‐family detached residential developments.  Driveways crossing required setback areas may be used for parking when serving single‐family detached  dwellings but shall not be considered for purposes of calculating required parking. Attached single‐ family and multifamily developments may have tandem parking areas for each dwelling unit but shall  not combine parking for separate dwelling units in tandem parking areas.  (8) All required vehicle parking must be on a paved surface.     20.124.120 Development Standards—Parking—Compact car allowance requirements.  Subject to planning director review and approval, up to 40 percent of the total number of spaces to be  provided in any development may be sized to accommodate compact cars. Aisle widths shall conform to  the standards set for standard size cars.    20.124.130 Development Standards—Parking—Internal circulation road standards.  Internal access roads to off‐street parking areas shall conform with or exceed the surfacing and design  requirements for private roads set in the Port Orchard road standards.     20.124.150 Development Standards—Parking—DOD parking standards.  Page 180 of 260     31      Except as otherwise provided in this section, development within the central DOD shall provide parking  in accordance with the off‐street parking requirements set forth in this chapter. If the formula for  determining the number of parking spaces results in a fraction, the number of parking spaces shall be  rounded to the nearest whole number with fractions of 0.50 or greater rounding up and fractions below  0.50 rounding down.  (1) For multifamily residential uses, the off‐street parking standard shall be a minimum of 1.5 parking  spaces for each dwelling unit, regardless of the number of bedrooms.  (2) For nonresidential uses, the off‐street parking standard shall be a minimum of one parking space per  300 gross square feet of floor area, except as otherwise provided in Table 20.124.250, as now or  hereafter amended.   (3) No new street level parking lot or parking garage that fronts directly on Bay Street shall be allowed  between Bank Street and Seattle Avenue.  (4) In the event that a building is located on a waterfront lot, parking shall be located to the side of the  building and not between the building and the water.  (5) Exemptions. The following uses within the central DOD shall be exempt from the parking standards  set forth in these regulations and the land use and development regulatory code.  (a) Existing uses along both sides of Bay Street from the crosswalk at Bank Street to Seattle  Avenue shall be exempt from the parking requirements set forth in these regulations and the land use  and development regulatory code.  (b) New ground floor uses shall be exempt from the parking requirements set forth in these  regulations.  (c) New development above the ground floor shall be exempt from the parking requirements set  forth in these regulations only if (i) the floor area of the new or remodeled building is equal to or less  than the floor area of the building that is present when these regulations become effective, and (ii) the  use(s) remains the same.  (6) In Lieu Payment.  (a) In lieu of furnishing the parking spaces required in subsections (1) and (2) of this section, the  requirements thereof may be satisfied by paying the city treasurer, prior to the issuance of a building  permit, a sum of money for each parking space required. The amount of the fee to be paid in lieu shall  be set by the city council in its sole discretion and shall incorporate current values for the purchase of  land, construction, and ongoing maintenance of off‐street parking spaces, or on a rental fee for each  required space.   (b) Sums so paid shall be deposited by the city treasurer in a special fund to be designated “city  of Port Orchard off‐street parking cumulative fund.” The city council may from time to time direct that  other moneys be transferred into the fund to be used for the purposes of the fund. The fund shall be  used exclusively for acquiring, planning, designing, developing, financing, and maintaining off‐street  parking facilities by purchase or lease for use by the central DOD area, all consistent with the  transportation improvement plan adopted or thereafter amended by the city council.  (7) Screening of Parking. The street‐facing, ground level facades of parking lots or garages shall be  designed to obstruct the view of parked cars from public rights‐of‐way. Where commercial or residential  space is not available to accomplish this, features such as planters, decorative grilles, or works of art  shall be used.    20.124.200 Development Standards—Parking—TRMT (Tremont Street corridor overlay district)) parking  and circulation standards.  Required parking will be as determined by the underlying zoning designation and must be contained on  site except where shared parking/consolidation is sought as described in POMC 20.124.210.   Page 181 of 260     32      20.124.210 Development Standards—Parking—TRMT parking reduction bonus.  (1) A shared parking/consolidated parking bonus may be achieved by any development which  incorporates either a shared parking or a consolidated parking agreement with an adjacent property.  The bonus may allow an overall reduction of required parking spaces by up to 20 percent. Where  reciprocal parking and/or access is proposed, agreements between the property owners together with  the proposed design must be provided with the site plan at application.  (2) A pedestrian amenities parking bonus may be achieved by the incorporation of a significant  pedestrian amenity in the form of plazas, courtyards, seating areas, fountains, and water features. The  bonus will vary with the amount and size of the amenities provided. The maximum incentive for the  reduction shall be one required parking space for each 100 square feet of plaza area or courtyard  provided, or through some combination of pedestrian amenities. For the purpose of qualifying for the  pedestrian amenities parking bonus, a plaza or courtyard must be designed as an integral part of the  development; have a minimum dimension of at least 20 feet; be open to the sky except for shade  trellises, arcades; and must incorporate seating areas, shade trees and trellises, and enhanced paving  materials. The incorporation of fountains or other water features is highly encouraged.    20.124.220 Development Standards—Parking—TRMT shared parking/consolidated parking bonus  conditions.  A shared parking/consolidated parking bonus for two or more uses may be achieved when the following  conditions are met, as determined by the planning director:  (1) The total parking area exceeds 5,000 square feet.  (2) The parking facilities are designed and developed as a single on‐site common parking facility, or as a  system of on‐site and off‐site facilities, if all facilities are connected with improved pedestrian paths.   (3) No building or use involved is more than 1,000 feet from the most remote shared facility.   (4) The amount of the reduction shall not exceed 10 percent for each use, unless:  (a) The normal hours of operation for each use are separated by at least one hour; or  (b) A parking demand study is prepared by a traffic engineer and submitted by the applicant  documenting that the hours of actual parking demand for the proposed uses will not conflict and that  uses will be served by adequate parking if shared parking reductions are authorized.   (5) The total number of parking spaces in the common parking facility is not less than the minimum  required spaces for either use.  (6) A covenant or other contract for shared parking between the cooperating property owners shall be  approved by the planning director. This covenant or contract must be recorded with the Kitsap County  auditor as a deed restriction on both properties and cannot be modified or revoked without the consent  of the planning director.  (7) If any requirements for shared parking are violated, the affected property owners shall provide a  remedy satisfactory to the planning director or provide the full amount of required off‐street parking for  each use, in accordance with the requirements of this chapter.     20.124.230 Development Standards—Parking—TRMT additional parking standards.  (1) Parking areas shall be separated from buildings by either a raised concrete walkway or a landscaped  strip with a six‐inch curb. Vehicles should not be allowed to directly abut the building.  (2) All parking spaces shall be clearly and permanently marked. Compact parking shall be grouped and  clearly identified.  (3) Parking lot design shall provide for connection to adjacent parcels where uses are compatible and  said connection is practical.  Page 182 of 260     33      (4) Parking lots shall be located to the rear and sides of buildings whenever feasible. Parking areas  directly adjacent to Tremont Street are discouraged.  (5) Parking facilities shall be located and designed in such a manner that vehicles exiting a site will do so  in a forward manner.  (6) Parking facilities shall be designed so that a car within a facility will not have to enter a street to  move from one location to another within the same parking lot.  (7) Large parking areas shall be divided into a series of connected smaller lots or separated with  landscaping and/or offsetting portions of the lot.  (8) Projects are encouraged to incorporate reciprocal access easements/agreements to improve internal  vehicular movements. Where parking areas are connected, interior circulation shall be designed to allow  for a similar direction of travel and parking bays, in all areas to reduce conflict points of connection.  (9) Individual projects and parking areas with on‐site driveways shall be linked and shall be clearly  identified as internal vehicle connectors.  (10) Access roads and/or driveways for commercial/office developments shall be located a minimum of  200 feet apart unless an alternate distance is recommended by the planning director.  (11) Access drives and/or driveways shall be located a minimum of 10 feet from property lines.  (12) Parking lot lighting standards shall be a maximum of 18 feet and shall be shielded to the parking  and building areas, avoiding light‐bleed into adjacent residential uses.     20.124.240 Development Standards—Parking—TRMT parking circulation.   (1) Design parking areas so that pedestrians can walk parallel to moving cars. Design parking lots so that  the majority of drive aisles are perpendicular to the majority of buildings or major tenant.   (2) Consolidation of parking entrances and exits with adjoining developments is encouraged to preserve  the functionality of Tremont Street as a major arterial.   (3) The parking area shall link the building to the street sidewalk system as an extension of the  pedestrian environment. This is accomplished through the use of enhanced walkways incorporating  different pavement materials, trellis structures, arcades, and landscape treatments.  (4) Driveway entry throats should be at least 25 feet wide, and preferably 30 to 35 feet wide, so that no  interference between exiting and entering vehicles occurs, or as recommended by the city engineer.  (5) Bicycle parking racks shall be provided for bicycles near each public entrance to each building.     20.124.16250 Development Standards—Parking—Minimum parking standards.  Table 20.124.16250  Minimum Parking Standards       Unit of  Measurement  Minimum Off‐ Street Parking  Requirement  Supplemental Parking  Requirement  Agriculture     Determined during application  Forestry     Determined during application  Fish and wildlife management     Determined during application  Mineral     Determined during application  Resource accessory uses     Determined during application  Recreational/Cultural Land Uses  Page 183 of 260     34      Park and recreation     Determined during application  Amusement/entertainment:        7832 Theater 3 fixed seats 1.0      7833 Theater, drive‐in     Determined during application   792 Plays, theatrical production 3 fixed seats 1.0 Determined during application   793 Bowling alley Lane 6.0    Sports club 300 sq. ft. 1.0    Golf facility Hole 3.0 + 1/300 sf clubhouse facilities   7999 Golf driving range Tee 1.0    Shooting range – guns and firearms Target 1.0 Determined during application  Archery range Target 1.0 + 1/300 sf indoor facilities  Amusement arcades 300 sq. ft. 1.0    Cultural:        823 Library 300 sq. ft. 1.0      841 Museum 300 sq. ft. 1.0      842 Arboretum     Determined during application  Conference center 3 fixed seats 1.0 + 1/50 sf assembly are without  fixed seats  Residential Land Uses  Dwelling units:        Single‐family detached Dwelling unit 2.0      Single‐family attached  Dwelling unit 2.0    Multifamily:        Studio units Dwelling unit 1.3      1 bedroom units Dwelling unit 1.5      2 bedroom units Dwelling unit 1.8      3 bedroom units or larger Dwelling unit 2.0    Mobile home park Dwelling unit 2.0    Houseboats Dwelling unit 2.0    Group residences:   Senior citizen assisted Dwelling unit 0.5      *Community residential facility –  CRF  Bedroom 0.5      *CRF – prisoner release Bedroom 0.5      *Dormitory Bedroom 0.5    Page 184 of 260     35      Accessory uses:   Dwelling unit Dwelling unit    Determined during application   Home (cottage) industry     Determined during application   Home occupation     Determined during application   Home profession     Determined during application  Temporary lodging:   7011 Hotel/motel Bedroom 1.0      Bed and breakfast Bedroom 1.0 In addition to any residential  dwelling parking requirements as  applicable   7041 Organization hotel/lodging  houses  Bedroom 1.0    General Services Land Uses  Personal services:   72 General personal services 300 sq. ft. office 1.0      Stand‐alone buildings     Determined during application   7216 Dry cleaning plants     Determined during application   7218 Industrial launderers     Determined during application   7261 Funeral home/crematory     Determined during application   Cemetery, columbarium or  mausoleum     Determined during application    Daycare Facility    Determined during application   Veterinary clinic 300 sq. ft. 1.0 Includes office, lab and exam area   753 Automotive repair Service bay 2.0 + 3/facility   754 Automotive service Service bay 2.0 + 3/facility   762‐3 Miscellaneous repair –  electrical/electronic     Determined during application    764‐9 Miscellaneous repair –  furniture/welding     Determined during application    83 Social services 300 sq. ft. 1.0      Stable     Determined during application   Kennel or cattery     Determined during application   866 Churches, synagogue, temple 3 fixed seats 1.0 + 1/50 sf assembly without fixed  seats  Health services:        801‐04 Office/patient clinic 250 sq. ft. 1.0    Page 185 of 260     36        805 Nursing and personal care  facilities  4 beds 1.0      806 Hospital Bed    Determined during application   807 Medical/dental lab 300 sq. ft. 1.0      808‐09 Miscellaneous health 300 sq. ft. 1.0    Education services:        Elementary or middle/junior high  school  Classroom 1.0 + 1/50 students    Secondary or high school Classroom 1.0 + 1/7 students   Vocational school Classroom 1.0 + 1/5 students   Specialized instructional school Classroom 1.0 + 1/2 students   School district support offices 300 sq. ft. office 1.0 + 1/1,000 sf of storage/repair  area  Government/Business Services Land Uses  Government services:      Public agency office 300 sq. ft. office 1.0    Public agency yard 300 sq. ft. office 1.0 + 1/1,000 sf of storage/repair  area  Public agency archives 50 sq. ft. review  area  1.0 + 1/1,000 sf of storage/repair  area  921 Court 50 sf seating area 1.0 + 3/courtroom  9221 Police facility     Determined during application  9224 Fire facility     Determined during application  Subregional utility     Determined during application  Minor communications facility 300 sq. ft. office 1.0    All business services unless  specified  300 sq. ft. office 1.0    15‐17 Construction and trade 300 sq. ft. office 1.0 + 1/1,000 sf of storage area  Warehousing and wholesale trade 300 sq. ft. office 1.0 + 1/1,000 sf of storage area  Self‐service storage 3,500 sf storage 1.0 + 2/resident manager’s unit  7312 Outdoor advertising service 300 sq. ft. office 1.0 + 1/1,000 sf of storage area  735 Miscellaneous equipment  rental  300 sq. ft. office 1.0 + 1/1,000 sf of indoor repair areas  751 Automotive rental and leasing 300 sq. ft. office 1.0 + 1/1,000 sf of indoor repair areas  Heavy equipment and truck repair 300 sq. ft. office 1.0 + 1/1,000 sf of indoor repair areas  Helipad     Determined during application  Page 186 of 260     37      Retail Land Uses  All retail uses unless specified 300 sq. ft. 1.0    5271 Mobile home dealers 300 sf indoor  sales  1.0    Forest products sales 300 ft. indoor  sales  1.0    54 Food stores less than 15,000 sf 300 sq. ft. 1.0 + 3/facility  Agricultural crop sales 300 sf indoor  sales  1.0    Motor vehicle and boat dealers 300 sf indoor  sales  1.0    554 Gasoline service station  without grocery  Service bay 2.0 + 3/facility  554 Gasoline service station with  grocery  300 sf store 1.0 + 3/facility + 2/service bay  58 Eating and drinking places – sit  down  100 sf dining/  lounge area  1.0    58 Eating – take out with drive‐ through windows  100 sf dining/  lounge area  1.0 + stacking requirement  58 Eating and drinking places –  banquet  100 sf dining/  lounge area  1.0 + 1/5 fixed seats of banquet  rooms  598 Fuel dealers     Determined during application  Auction houses     Determined during application  Petroleum:        2911 Petroleum refining      Manufacturing Land Uses  All manufacturing uses unless  specified  1,000 sq. ft. 0.9    2082‐8 Winery/brewery 1,000 sq. ft. 0.9 + 1/50 sq. ft. of tasting area  Regional Land Uses  All regional uses unless specified     Determined during application    20.124.260 Development Standards—Parking—Minimum parking stall dimensions.  Table 20.124.170260    Minimum Parking Stall Dimensions  Minimum Parking Stall  Dimensions  Stall  Width  Stall  Depth  Page 187 of 260     38      Compact stall 8.0 16.0  Standard stall (required for  single‐family and duplex  parking)  9.0 20.0  Minimum Loading Requirements       Unit of  Measurement  Minimum  Loading  Spaces  Nonresidential Buildings with Retail, Wholesale,  Manufacturing, Storage Uses (1)  10,000 – 16,000 square feet 1.0  16,001 – 40,000 square feet 2.0  40,001 – 64,000 square feet 3.0  64,001 – 96,000 square feet 4.0  96,001 – 128,000 square feet 5.0  128,001 –  160,000 square feet 6.0  160,001 –  196,000 square feet  7.0  Each additional  36,000 square feet 2.0  Retail, Hotel, Office, Restaurant, Hospital,  Auditorium, Convention Hall, Exhibition Hall,  Sports Arena/Stadium or Similar  40,000 – 60,000 square feet 1.0  60,001 – 160,000 square feet 2.0  160,001 –  264,000 square feet 3.0  264,001 –  388,000 square feet 4.0  388,001 –  520,000 square feet 5.0  520,001 –  652,000 square feet 6.0  652,001 –  784,000 square feet 7.0  784,001 –  920,000 square feet 8.0  Page 188 of 260     39      Each additional  140,000 square feet 1.0  (1) Excluding self‐service storage facilities.    20.124.180270 Development Standards—Parking—Off‐street parking design standards.  (1) The most distant parking space shall not be located more than 500 feet away from the nearest  building entrance it is required to serve. Where the off‐street parking areas do not abut the buildings  they serve, the required maximum distance shall be measured from the nearest building entrance that  the parking area serves:  (a) For all nonresidential uses permitted in residential zones, the parking spaces shall be located  on the same lot they are required to serve and at least a portion of parking areas shall be located within  150 feet from the nearest building entrance they are required to serve.  (b) For all uses permitted within downtown mixed use district (Mxd), the parking spaces may be  located on consolidated off‐site parking lots distributed at accessible locations about the downtown  district.  (2) Minimum parking space and aisle dimensions shall be determined by the planning director.  Regardless of the parking angle, one‐way aisles shall be at least 10 feet wide, and two‐way aisles shall be  at least 20 feet wide. Parking plans for angle parking shall use space widths no less than eight feet, six  inches for a standard parking space design and eight feet for a compact car parking space design.  (3) Any parking spaces abutting a landscaped area on the driver or passenger side of the vehicle shall  provide an additional 18 inches above the minimum space width requirement to provide a place to step  other than in the landscaped area. The additional width shall be separated from the adjacent parking  space by a parking space division stripe. The parking space depth may be reduced when vehicles  overhang a walkway under the following conditions:  (a) Wheelstops or curbs are installed.  (b) The remaining walkway provides a minimum of 60 inches of unimpeded passageway for  pedestrians.  (4) The amount of space depth reduction is limited to a maximum of 18 inches.  (5) Ingress and egress between off‐street parking areas and abutting streets shall be designed, located,  and constructed in accordance with Port Orchard street standards.   (6) Lighting of off‐street parking areas shall be provided for safety of traffic and pedestrian circulation on  the site, as specified in the International Building Code. Lighting shall be designed to minimize direct  illumination of abutting properties and adjacent streets. The planning director shall have the authority  to waive the requirement to provide lighting.  (7) Tandem or end‐to‐end parking is allowed in single‐family detached residential developments.  Driveways crossing required setback areas may be used for parking when serving single‐family detached  dwellings but shall not be considered for purposes of calculating required parking. Attached single‐ family and multifamily developments may have tandem parking areas for each dwelling unit but shall  not combine parking for separate dwelling units in tandem parking areas.  (8) All required vehicle parking must be on a paved surface.  (9) LID best management practices (BMPs) shall be used for all parking lot design and construction,  unless site and soil conditions make LID infeasible as determined by the City. LID BMPs for parking lot  design and construction include, but are not limited to:   (a) Pervious surfacing;   (b) Integrating stormwater management facilities, such as bioretention swales, with required  parking lot landscaping; and  Page 189 of 260     40      (c) Using native species in the landscape design.   (d) LID BMPs shall be designed and constructed in accordance with the LID Technical Guidance  Manual for Puget Sound (current edition).      Chapter 20.128  DEVELOPMENT STANDARDS—LANDSCAPING  20.128.010 Development Standards—Landscaping—Purpose.(1) The purpose of this chapter is to  preserve the aesthetic character of the community, improve the aesthetic quality of the built  environment, promote retention and protection of existing native vegetation, reduce the impacts of  development on storm drainage systems and natural habitats, and increase privacy for residential zones.  (2) These goals are established through standards that:  (a) Provide visual relief from large expanses of parking areas and reduce perceived building  scale;   (b) Provide physical separation between residential and nonresidential areas;  (c) Provide visual screens and barriers as a transition between differing land uses;   (d) Retain existing vegetation and significant trees by incorporating them into the site design;   (e) Promote the use of native and drought‐tolerant plant materials; and   (f) Provide areas of permeable surface to allow for infiltration of surface water into groundwater  resources, reduce the quantity of stormwater discharge, and improve the quality of stormwater  discharge.     20.128.020 Development Standards—Landscaping—Applicability.  (1) All development shall be subject to the landscaping provisions and requirements of this chapter;  provided, that specific landscaping and tree retention provisions for uses established through a  subdivision, short subdivisions, binding site plan, or conditional use permit application shall be  determined during the application review process.    (2) Landscaping standards referenced in POMC 20.128.230 through 20.128. 239 shall be applicable  within the Tremont Street corridor overlay district (TRMT).   (23) Landscaping standards referenced in POMC 20.128.240 shall be applicable within the Downtown  overlay district (DOD).     20.128.030 Development Standards—Landscaping—Exempt areas. Development along both sides of Bay  Street from the crosswalk at Harrison Avenue to Orchard Avenue is exempt from the landscaping  requirements of this chapter.     20.128.032 Development Standards—Landscaping—Landscape materials.  Recommended species/variations of suitable landscape plants are shown in Table 20.128.297,  Suggested Landscape Materials. An applicant may select from the suggested list or propose other  alternative planting materials based on the objectives for the landscape zones outlined in this chapter.  All proposed landscape plantings within these zones shall be reviewed and approved by the Director or  his or her designee.    20.128.035 Development Standards—Landscaping—Integration with LID stormwater management  facilities.  Page 190 of 260     41      The required landscape design requirements in this chapter may be integrated with LID stormwater  management facilities and BMPs unless site and soil conditions make LID infeasible, subject to the  approval of the Director and Public Works Department.  LID facilities shall not compromise the purpose  or intent of required landscaping and landscaping shall not result in the disruption of the LID facilities’  functions.  LID facilities shall be designed and constructed in accordance and the LID Technical Guidance  Manual for Puget Sound (current edition).    20.128.040 Development Standards—Landscaping—General landscape requirements.  Landscape designs shall conform to the following provisions:  (1) New landscaping materials shall include native or ornamental species that have adapted to the  climatic conditions of the coastal region of the Pacific Northwest. Required minimums are indicated in  Table 20.128.296, Landscape Design Requirements.  (2) New landscape materials shall include drought‐tolerant species, except where site conditions within  the required landscape areas assure adequate moisture for growth.  (3) Existing vegetation may be used to augment new plantings to meet the standards of this chapter.  (4) Trees shall have a caliper of the dimensions shown in Table 20.128.296, Landscape Design  Requirements, measured four feet above ground level at the time of planting. The caliper may be  averaged, but no individual tree shall have a caliper of less than 75 percent of the requirement.   (5) When the width of any landscape strip is 20 feet or greater, the required trees shall be staggered in  two or more rows.  (6) Shrubs shall be at least one gallon in size and of the minimum inches in height at the time of planting  shown in Table 20.128.296, Landscape Design Requirements.   (7) Ground covers shall be planted and spaced to result in total coverage of the required landscape area  within the number of years indicated in Table 20.128.296, by using four‐inch pots at 18 inches on center,  or one gallon or greater sized containers at 30 inches on center.  (8) Grass may be used as a ground cover only in urban buffer parking lots or filtered areas; provided,  that the grass area constitutes no more than 30 percent of such landscape areas.  (9) Grass and ground cover areas shall contain at least two inches of composted organic material at  finish grade. Existing soils shall be augmented with a two‐inch layer of fully composted organic material  rototilled a minimum of six inches in depth.  (10) Berms should not exceed a slope of two horizontal feet to one vertical foot (2:1), unless there are  extenuating circumstances.  (11) Landscape areas shall be covered with two to three inches of mulch. Mulch shall consist of  materials such as yard waste, sawdust, and/or manure that is fully composted.   (12) Required street landscaping may be placed within Port Orchard street rights‐of‐way subject to the  Port Orchard road design standards set forth in this Title and with the permission of the city engineer.     20.128.050 Development Standards—Landscaping—Alternative landscape options.  The following alternative landscape options may be permitted only if they accomplish equal or better  levels of screening and are subject to the review and approval of the planning director:  (1) Total required landscape and tree retention area will not exceed 15 percent of site area.  (2) The width of the perimeter buffer landscape strip may be reduced up to 25 percent along any  portion where berms at least three feet in height or architectural barriers at least six feet in height are  incorporated into the landscape design, or the landscape materials are incorporated elsewhere on‐site.  (3) Perimeter landscaping may be reduced up to 25 percent when a development retains an additional  10 percent of the existing significant trees or 10 significant trees per acre on‐site (above the  requirements for tree retention defined within this chapter), whichever is greater.  Page 191 of 260     42      (4) The landscaping requirement may be modified when existing conditions on or adjacent to the site,  such as significant topographic differences, vegetation, structures or utilities would render application of  this chapter ineffective or result in scenic view obstruction.  (5) Within the mixed use district (Mxd) areas subject to a requirement for an urban  streetscape/pedestrian boardwalk design, roadway corridor buffering is waived provided the applicant  complies with the requirements for street trees, pedestrian pavings, furnishings, and other amenities.  (6) When an existing structure precludes installation of the total amount of required site perimeter  landscaping, such landscaping material shall be incorporated on another portion of the site.  (7) Creative designs using groupings of trees may be utilized.     20.128.060 Development Standards—Landscaping—Irrigation.  (1) Except for areas of undisturbed existing vegetation or low areas with existing high soil moisture  conditions, landscape areas shall have temporary irrigation systems. Such systems may be removed  after 24 months or two growing seasons, whichever occurs first; provided, that the plantings are  established.  (2) Areas of undisturbed existing vegetation, or areas where existing site conditions assure adequate soil  moisture for growth within the required landscape area, shall have temporary irrigation systems only as  required to sustain new plantings and shall be determined on a case‐by‐case basis by the planning  director.  (3) Areas of undisturbed existing vegetation, low areas with existing high soil moisture conditions, or  landscape areas consisting of drought‐tolerant vegetation may not require permanent irrigation  systems. Permanent irrigation systems may be permitted within all other required landscape areas,  provided such systems shall be designed with:  (a) Moisture or precipitation sensors;  (b) Automatic timers set for operation during periods of minimum evaporation and that assure  adequate moisture levels;  (c) Head‐to‐head spacing, if sprinkler heads are proposed;  (d) Backflow prevention devices; and  (e) Separate irrigation zones for turf and planting beds, and other nondrought‐tolerant species.     20.128.070 Development Standards—Landscaping—Landscape installation – Timing.  Landscaping shall be installed no later than five months after issuance of a temporary certificate of  occupancy for the project or project phase. The time limit for compliance may be extended to allow  landscape installation during the next appropriate planting season.   20.128.080 Development Standards—Landscaping—Urban streetscape/pedestrian boardwalk corridors.  (1) Urban streetscape and pedestrian boardwalk corridors are the public right‐of‐way spaces to be  improved for pedestrian walking, shopping, eating, and similar activities in front of retail stores and  mixed use structures. The urban streetscape/pedestrian boardwalk corridors shall be as defined in the  design overlay districts in this code.  (2) Urban streetscape/pedestrian boardwalk areas shall be landscaped to provide and maintain a design  theme that may emphasize a selection of street trees, lighting standards, directional signage,  furnishings, pavings, landscape materials, or other major components to be specified within the design  overlay districts.     20.128.090 Development Standards—Landscaping—Roadway corridors and street frontages.  Roadway corridors and street frontages shall be landscaped based on the different pedestrian and/or  vehicle emphasis to be provided in accordance with the following categories of design and functional  Page 192 of 260     43      treatment. These zones and corridors shall be planted with street trees suitable for a mixed motor  vehicle, bicycle, and pedestrian environment.  (1) Commercial Street Corridors. These corridors are the public rights‐of‐way and the setbacks required  within and around roadways and parking lots in the commercial (Co), mixed use (Mxd), employment  (Eo), and community facilities (Cf) zones. The setback from the street right‐of‐way shall be landscaped to  provide “see‐through vegetation” that functions as a partial visual separator to soften the appearance of  parking areas and building elevations.   (2) Residential Street Corridors. These corridors are the public rights‐of‐way and the setbacks required  within and around collector and arterial roadways and parking lots in all residential zones (R4.5 through  R20). These zones shall be landscaped to provide a “filtered screen vegetation” that functions as a visual  separator between the street, parking areas, and residential activities.   (3) Parkway Road Corridors. These corridors are the public rights‐of‐way and the setbacks required  along major roadway entries into the community as defined on comprehensive plan maps. These  parkway road corridors shall be landscaped to provide a “filtered to view blocking vegetation” using  natural materials that provide continuity with adjacent greenway landscapes.   (4) Sight Distance. All physical obstructions, except utility poles and traffic control signs, shall be  maintained in a manner that provides for adequate sight distances at street intersections as described  below:  (a) A sight distance triangle area as described in subsection (4)(b) of this section shall not contain  fencing, berms, vegetation, on‐site vehicle parking areas, signs and other physical obstructions between  36 inches and eight feet above the existing street grade.  (b) The sight distance triangle at:  (i) A street intersection shall be determined by measuring 15 feet along both the right‐of‐way property  lines beginning at their point of intersection. The third side of the triangle shall be a line connecting the  endpoints of the first two sides of the triangle; or  (ii) A site access point shall be determined by measuring 15 feet along the street lines and 15 feet along  the edges of the driveway beginning at the respective points of intersection. The third side of each  triangle shall be a line connecting the endpoints of the first two sides of each triangle; and  (iii) Any intersection where the posted speed limit exceeds 25 miles per hour, the site distance triangle  shall be determined by the table below or the city engineer.    Posted Speed  Limit  Design  Speed  Minimum Distance  for Sight from  Center of  Intersection  25 30 200 feet  30 35 250 feet  35 40 325 feet  40 45 400 feet  45 50 475 feet  50 55 550 feet  55 60 650 feet  Page 193 of 260     44      The city engineer may require further  restrictions.    (c) If a property owner receives written notice from the city that there is a violation of the above  requirements and does not comply to the written notice within the specified time, then such property  owner shall be guilty of a civil penalty. In addition to this, the city engineer or his/her designee may  prune the trees or take other appropriate action, charge the owner for the cost of the work, record the  charges as a lien against the property and collect this amount in a civil action against the property  owner. The city shall be entitled to recover its costs and attorney’s fees in such action.     20.128.100 Development Standards—Landscaping—Buffers and urban buffers.  (1) Perimeter landscaping along interior lot lines and between zones shall be as provided within Table  20.128.296, Landscape Design Requirements. Perimeter landscaping may be modified where  appropriate by the planning director to account for aboveground subregional utility developments and  distribution or transmission corridors or other utilities and infrastructure.   (2) Urban buffers shall be landscaped based on the extent to which the activity is to be screened from  adjacent uses in accordance with the categories identified below. However, common standards applied  to all buffer areas include:  (a) Within the landscape buffer areas about the property, particularly along secondary access roads and  around parking lots that do not abut the public pedestrian walkway or trail corridors, site plantings  should be grouped to simulate natural stands and should not be planted symmetrically or of even  spacing.   (b) Landscape designs should reflect natural planting materials and settings that are representative of  the local and regional landscape.   (c) Where practical and feasible, buffer areas should retain existing larger trees and vegetation to  maintain continuity with adjacent greenways and natural areas.  (d) Within higher density residential developments, buffers or open spaces may be grouped into  common open space areas that define building placements, provide visual accents, preserve landscape  or landform features, or house common activity areas.   (3) Urban Buffers with Filtered Screening. Urban buffers to be filter screened are the perimeter  landscape areas provided between nonresidential land uses within the commercial (Co), mixed use  (Mxd), employment (Eo), and community facilities (Cf) zones. These buffers shall function as a visual  separator between uses within these zones. The plant materials and design may mix evergreen and  deciduous trees and shrubs to create a filtered screen effect.  (4) Urban Buffers with Full Screening. Urban buffers to be fully screened are the perimeter landscape  areas provided between residential and nonresidential zones. These buffers shall function as a visual  barrier to obscure views of incompatible activities and improvements. The plant materials and design  may include a mix of primarily evergreen trees and shrubs to form an effective full screen effect.     20.128.110 Development Standards—Landscaping—Walkway and trail corridors.  Landscaping along the public walkway or trail corridor may utilize the street trees and plant materials  palette selected for the public walkway or trail corridor. Improvements within the adjoining private  spaces, such as outdoor eating areas, plazas, and the like, should incorporate or continue the same  plantings in order to enhance the definition of the corridor.    20.128.120 Development Standards—Landscaping—Greenways.  Page 194 of 260     45      Greenways shall be maintained, enhanced, and replanted, where appropriate, based on the type of  habitat to be conserved in accordance with the following categories:  (1) Greenways of Upland Habitat.   (a) Upland greenways are the sensitive environmental areas located on steep, eroding, or geologically  hazardous slopes as defined within this code and within the comprehensive plan.   (b) The landscape within this zone shall be maintained or enhanced with native materials that provide  habitat and cover for upland wildlife species.   (2) Greenways of Wetland and Stream Habitat.   (a) Wetland greenways are the sensitive environmental areas located on impermeable or slowly draining  soils, wetlands and other freshwater bodies, and the required buffer areas adjacent to wetlands and  streams as defined within this code and within the comprehensive plan.   (b) The landscape within this zone shall be maintained or enhanced with native materials that provide  habitat and cover for wetland wildlife species.   (3) Shorelines.  (a) Shorelines are the sensitive environmental areas and buffer zones located along the fresh and  saltwater shores and banks as defined within this code and within the comprehensive plan.  (b) The landscape within this zone shall be maintained or enhanced with native materials that provide  habitat for marine and estuarine wildlife species.     20.128.130 Development Standards—Landscaping—Street trees.  (1) Street trees shall be planted along roadways and street frontages as indicated within the  accompanying Table 20.128.296 on landscape design requirements. Tree spacing shall consider the  mature height and spread of the tree species.  (2) Street tree species, where not designated in accordance with a design overlay district’s  requirements, may be selected from the suggested landscape materials list, Table 20.128.297, and shall  be subject to the review and approval of the planning director.   (3) The trees may be located within the street right‐of‐way subject to the review and approval of the city  engineer and accounting for any possible future street widening or improvements.  (4) Street trees within the public right‐of‐way shall be maintained according to the standards established  by the planning director.  (5) Street trees may be spaced at irregular intervals where necessary to accommodate sight distance  requirements for driveways, intersections, street lights, and signage.     20.128.140 Development Standards—Landscaping—Buildings and yards.  (1) The landscape design should highlight and focus views of the building frontages and entries,  particularly retail window displays, pedestrian areas, and amenities. The design should create a special  or individual character of the private portions of each property and building.   (2) Vines may be planted on buildings, fences, walls and other blank surfaces, particularly structures  faced with brick and masonry or that are enhanced with trellis overhangs.   (3) Moveable planters with seasonal plantings should be placed at building entries, particularly within  alcoves and inner courtyards.   (4) All plantings, particularly ornamentals, should be provided irrigation or other watering methods to  ensure plant survival.     20.128.150 Development Standards—Landscaping—Screening.  Landscape, fence or other improvements should be erected to visually screen refuse, storage, loading  docks, and other areas that are not to be accessible or viewed from public walkways, corridors, and  Page 195 of 260     46      roadways. Latches and other devices should be used to secure refuse and storage areas from animals  and children.     20.128.160 Development Standards—Landscaping—Parking lots.  (1) Landscaping within parking lots that are shared or used in common by residential developments, and  within all nonresidential parking areas and lots, shall be as provided within the accompanying Table  20.128.296, Landscape Design Requirements.  (2) The maximum distance between any parking stall and required parking area landscaping shall be no  more than every 13 stalls.  (3) Permanent curbs or structural barriers shall be provided to protect the plantings from vehicle  overhang.  (4) Urban parking areas shall be landscaped to provide shade and visual relief while maintaining clear  sight lines within parking and access areas. Shrubs will not exceed a height of three feet around parking  lot entries, access aisles, and other vehicle maneuvering areas in order not to visually block views among  vehicles and pedestrians.  (5) The plant materials and landscape design may mix evergreen and deciduous trees to create a  continuous canopy.  (6) Plantings may be contained in planting islands or strips having an area of at least 75 square feet with  a narrow dimension of not less than four feet that is unobstructed by vehicle overhang.  (7) Shade trees and ground covers should be installed in parking medians and/or landscape set‐asides in  parking areas and lots to soften the visual impact, reduce glare, and provide visual interest.     20.128.180 Development Standards—Landscaping—Significant tree retention.  Significant trees should be retained in all zones as follows:  (1) Removal of any significant tree with a DBH (diameter at breast height) of 36 inches or greater shall  require city council approval upon the following standards:  (a) The proposed use cannot reasonably accommodate the retention of the significant tree.  (b) The significant tree shall be replaced in accordance with POMC 20.128.220.  (c) All significant trees located within any required buffer area or required landscape planting area  should be retained to the extent practical and feasible.  (d) Tree retention adjacent to critical areas is desirable.  (e) Utility developments including roadways may be exempt from the significant tree retention  requirements of this chapter.  (f) If significant trees were previously located in a closed, forested situation, an adequate buffer of  smaller trees shall be retained or replaced on the fringe of such significant trees.  (g) A grouping of three or more existing healthy trees with canopies that touch or overlap may be  substituted for each required significant tree, provided each tree has a diameter of at least three inches  when measured four feet above grade.  (2) Except as provided in subsection (3) of this section, significant trees to be retained shall not include  significant trees that are identified by a licensed arborist as damaged or diseased or a safety hazard due  to potential root, trunk or primary limb failure, or exposure of mature trees which have grown in a  closed, forested situation.  (3) At the discretion of the planning director, damaged or diseased or standing dead trees may be  retained and counted toward the significant tree requirement if demonstrated that such a tree will  provide important wildlife habitat and is not classified as a danger tree.     20.128.190 Development Standards—Landscaping—Significant tree retention plan.   Page 196 of 260     47      The applicant shall submit a tree retention plan concurrent with a grading permit, building permit or  preliminary subdivision application, whichever is reviewed and approved first. The tree retention plan  shall consist of:  (1) Tree survey that identifies the location, size, and species of individual significant trees or the  perimeter of stands of trees on a site. For forested sites, the tree survey may use a standard timber  cruising method to reflect general locations, numbers, and groupings of significant trees. For detailed  site plans and grading applications, the tree survey may be conducted by a method that locates  individual significant trees near edges of tree protection areas.   (2) The tree retention plan identifying the significant trees that are proposed to be retained should show  the locations of tree protection fence that protects the critical root zones of the trees.     20.128.200 Development Standards—Landscaping—Incentives for retaining significant trees.  Each significant tree that is located outside of the area for perimeter buffer landscaping and is retained  may be credited in a ratio up to two trees for complying with the retention requirements of this chapter.     20.128.210 Development Standards—Landscaping—Protecting significant trees.  To provide the best protection for significant trees:  (1) No clearing shall be allowed on a site until approval of tree retention and landscape plans.  (2) The root protection zone is equal to one foot radius for every one inch of tree DBH unless individual  tree evaluation by a certified arborist recommends modification to the guidelines. It shall be identified  prior to construction with a temporary five‐foot‐high chain‐link or orange mesh fence.  (3) No impervious surfaces, fill, excavation, or storage of construction materials shall be permitted  within the root protection zone.  (4) Alternative protection methods may be used if determined by the planning director to provide equal  or greater tree protection.    20.128.220 Development Standards—Landscaping—Replacement of significant trees.  When the required number of significant trees cannot be retained, significant trees that are removed  shall be replaced with:  (1) New trees measuring 2.5‐inch caliper and six feet in height, at a replacement rate of three trees for  each significant tree removed.   (2) If the site does not allow for planting all replacement trees, trees can be planted on another site  approved by the planning director.    20.128.230 Development Standards—Landscaping—Tremont Street corridor overlay district landscape  standards (TRMT).  The general landscape standards set forth in this chapter shall apply unless a more restrictive provision  is set forth in the TRMT specific landscape standards set forth in POMC 20.128.231 through 20.128.239.     20.128.231 Development Standards—Landscaping—TRMT landscape standards – Generally.  The following guidelines are to be addressed in all landscape plans in the Tremont overlay:  (1) Significant trees shall be preserved where possible (some may be moved and transplanted). Removal  of any significant tree requires pre‐approval from the planning director.   (2) Emphasize use of varieties which require low maintenance and drought‐tolerant species in public  and commercial areas and in large landscape areas.  (3) A minimum of 25 percent of the site shall be landscaped. Required landscaping within parking areas  may not be counted as contributing to this requirement. However, landscaping for and within setback  Page 197 of 260     48      areas may be counted toward meeting the 25 percent requirement. A minimum five‐foot landscaped  area shall be installed around all parking lots.     20.128.232 Development Standards—Landscaping—TRMT landscape as buffering.  Buffering between noncompatible land uses is considered critical in maintaining the existing character  of Tremont Street. The following standards are to be used in designing a landscape buffer:  (1) Landscape buffers, in conjunction with decorative fencing, is the preferred method to screen  adjacent land uses.  (2) Evergreen trees having minimum size of 15 gallons shall be planted and staked at least 20 feet on  center, depending upon the species, or clustered in equal amounts to screen parking or architecture.  (3) A six‐foot‐high wall may be placed on or just inside the property line. A ten‐foot landscape strip area  will be provided on the inside of the wall. The wall should be lowered to three feet within the front  setback area.     20.128.234 Development Standards—Landscaping—TRMT landscape area ratio.  A minimum of one 15‐gallon size tree (25 feet or higher at maturity) for every 625 square feet of  landscaping, and one shrub or vine for every 50 square feet of landscaping are required; at least 25  percent of shrubs shall be of a flowering variety.     20.128.236 Development Standards—Landscaping—TRMT landscape irrigation.  Automatic sprinkler or drip irrigation systems for all commercial or multifamily projects shall be  provided.     20.128.237 Development Standards—Landscaping—TRMT landscape maintenance.  All plantings shall be kept healthy and growing with all planting areas free of weeds and debris. Each  project will have a bond recorded insuring planting materials will be well maintained; such bond shall  remain in place for one year after project completion.     20.128.238 Development Standards—Landscaping—TRMT landscape sizes.  (1) Trees shall be a minimum of one gallon size and be at least eight feet at time of planting. Shrubs shall  be a minimum of one gallon size at time of planting. All deciduous trees shall be double staked and  properly fertilized upon planting. Give consideration for rapidly growing trees.  (2) The ground cover shall be healthy, densely foliated, and consist of one‐gallon container plants.  Herbaceous and flat ground covers shall be planted no more than 12 inches on center. Woody shrub  ground cover shall be planted no more than four feet on center (e.g., evergreens, junipers).     20.128.239 Development Standards—Landscaping—TRMT landscape spacing.  Spacing of trees and shrubs shall be appropriate for each individual species and growing characteristics.  Plant materials shall conform to the following spacing standards:  (1) A minimum of 25 feet from the property corner at a street intersection to the center of the first tree  or large shrubs. Shrubs less than three feet in height are allowed within this clear sight triangle.  (2) A minimum of 15 feet between center of trees or large shrubs and fire hydrants.  (3) A minimum of 10 feet between center of trees or large shrubs and edge of driveway.     20.128.240 Development Standards—Landscaping—Downtown overlay district landscape standards  (DOD).  Page 198 of 260     49      The general landscape standards set forth in this chapter shall apply to all development in the DOD  unless a more restrictive provision is set forth in this section, and then this section shall control.  (1) New development and existing uses along both sides of Bay Street between Bank Street and Seattle  Avenue shall be exempt from the landscaping requirements of the land use and development regulatory  code and these regulations.  (2) New development that is adjacent to the water shall provide landscaping on the waterside facade as  well as on the street frontage.  (3) New development on waterfront lots that abut the north side of Bay Street between Bank Street and  Seattle Avenue shall provide landscaping on the waterside facade only.  (4) For buildings which include residential uses on the upper floors, up to 25 percent of the landscaping  requirements may be fulfilled by providing rooftop gardens and upper floor terraces and decks. Rooftop  gardens, terraces, and decks shall not count against the 75 percent gross floor area limitation described  in POMC 16.20.219.     20.128.290 Development Standards—Landscaping—Maintenance.  (1) All landscape materials and significant trees, in all zones and/or overlay districts, except within  critical areas or buffers, shall be maintained in a healthy growing condition.  (2) With the exception of dead, diseased or damaged trees specifically retained to provide wildlife  habitat; other dead, diseased, damaged or stolen plantings shall be replaced on a one‐for‐one basis  within five months or during the next planting season if the loss does not occur in a planting season.  (3) Landscape areas shall be kept free of trash.     20.128.295 Development Standards—Landscaping—Bonds and security.  Performance bonds or other appropriate security (including letters of credit and set aside letters) equal  to 125 percent of the estimated value of the plants and installation costs shall be required for a period  of two years after the planting or transplanting of vegetation to insure proper installation,  establishment, and maintenance.     20.128.296 Development Standards—Landscaping—Landscape design requirements.  See Table 20.128.297 for alternatives.  Page 199 of 260   50   Table 20.128.296  Landscape Design Requirements   Urban Streetscapes/ Pedestrian Boardwalks Roadway Corridors –  Commercial Development Roadway Corridors –  Residential Development Roadway Corridors –  Parkways Urban Buffers –  Urban Parking Lots Urban Buffers –  Filtered Screening Urban Buffers –  Full Screening Greenways – Uplands Greenways – Wetlands Shorelines Planting materials Large deciduous trees  X   X   X X X Medium deciduous trees X X X  X   X X X Small deciduous trees X  X   X  X X X Conifers/broadleaf trees   X X X X X X X X Deciduous shrubs X X X  X X  X X X Evergreen shrubs X X X X X X X X X X Ground covers X X X X X X X X X X Planting mix – Approximate Percent in deciduous trees 100% 100% 50% 30% 70% 50% 30% 30% 70% 70% Percent in evergreen trees 0% 0% 50% 70% 30% 50% 70% 70% 30% 30% Plant spacing – Feet on center Trees 25 40 40 30 30 30 15 30 30 40 Shrubs     5 5 4 4 4 4 Plant scale at time of planting Page 200 of 260   51   Trees – minimum height in feet 10 10 8 8 10 8 8 8 8 8 Trees – minimum caliper in inches 3.0 3.0 2.5 2.5 3.0 2.5 2.5 2.5 2.5 2.5 Shrubs – minimum height in inches  18 18 18 18 18 18 18 18 18 18 Ground cover – years to full coverage 2 2 3 3 2 3 3 3 3 3 Buffer – Depth in feet (subordinate to building setbacks)  Street frontage  10 10 20     25 25 25 Interior lot line     5 5 10 25 25 25 Parking lot – sf landscape area/stall Residential shared parking     20      Commercial/employment zone lots:              0 – 30 stalls     20      30+ stalls     25      Parking lot – Stalls/tree spacing Residential shared parking     8      Commercial/employment zone lots     4      Species suggestions – Percent of mix Page 201 of 260   52   Native ground cover and shrubs 75% 75% 75% 75% 75% 75% 75% 100% 100% 100% Native trees 50% 50% 50% 50% 50% 50% 50% 100% 100% 100% Drought‐tolerant 60% 60% 60% 60% 60% 60% 60% 100% 100% 100%    20.128.297 Development Standards—Landscaping—Suggested landscape materials. Table 20.128.297  Suggested Landscape Materials    Urban Streetscapes/ Pedestrian Boardwalks Roadway Corridors/ Street Frontage Parking Lot Trees Urban Buffer Areas Greenways – Uplands Greenways – Wetlands/ Streams Shorelines Native Materials Drought‐Tolerant Large deciduous trees Acer macrophyllum Bigleaf Maple     X X  X  Acer rubrum species Red Maple variety X X X X   X   Acer saccharum Sugar Maple   X X      Acer truncatum X platanoide Pacific Sunset Maple X X            Acer platanoides species Norway Maple variety X X X X   X   Alnus rebra Red Alder     X X  X X Page 202 of 260   53   Carpinus betulus ‘Fastigiata’ Columnar European Hornbeam X X            Fagus sylvatica European Beech    X   X  X Fraxinus latifolia Oregon Ash     X X  X  Fraxinus oxycarpa ‘Raywood’ Raywood Ash X X            Gingko bilboa ‘Sentry’ Columnar Maidenhair    X     X Liquidambar styraciflua American Sweetgum X X X X   X  X Liriodendron tulipifera Tulip tree    X      Magnolia grandiflora ‘St. Mary’ Evergreen Magnolia X X            Platanus x acerifolia London Plane    X      Quercus species Oak variety X X X X     X Quercus robur ‘Fastigiata’ Upright English Oak   X X   X  X Quercus rubra Northern Red Oak X X X X     X Salix species Willow variety      X X X  Page 203 of 260   54   Tillia americana ‘Redmond’ Redmond Linden X X            Tillia cordata Littleleaf Linden X X X X   X   Tillia cordata ‘Greenspire’ Greenspire Linden X X            Medium deciduous trees Acer campestre Hedge Maple   X         X Betula species Birch variety    X      Carpinus betulus European Hornbeam X X X X   X  X Cercidiphyllum japonicum Katsura Tree    X      Cornus nuttallii Pacific Dogwood     X   X X Cratawgus laevigata English Hawthorn X X            Crateagus lavallei Lavalle Hawthorn X X            Fraxinus pennsylvanica Marshall’s Seedless Ash X X X X     X Populus tremuloides Quaking Aspen      X  X  Prunus species Flowering Cherry variety X X X X   X   Page 204 of 260   55   Prunus sargentii Sargent Flowering Cherry X X            Prunus sargentii ‘Columnaris’ Columnar Sargent Flowering Cherry X X            Prunus serrulata ‘Kwanzan’ Kwanzan Flowering Cherry X X            Pyrus calleryana species Flowering Pear variety X X X X     X Zelkova serrata ‘Village Green’ Sawleaf Zelkova X X X X      Small deciduous trees Acer circinatum Vine Maple    X X X  X  Acer davidii David Maple    X      Acer ginnala Amur Maple   X X   X   Acer palmatum Japanese Maple    X      Amelanchier species Serviceberry variety    X X X  X  Carpinus species Hornbeam variety X X X X   X  X Cornus florida Flowering Dogwood    X      Page 205 of 260   56   Cornus kousa Kousa Dogwood   X X      Corylus cornuta californica Western Hazelnut    X X   X X Crataegus species Hawthorn variety    X X  X X X Magnolia species Magnolia variety X X X X   X   Malus species Flowering Crabapple    X      Prunus species Flowering Cherry/Plum X X  X   X  X Styrax japonica Japanese Snowball    X      Conifers/broadleaf evergreen trees Abies grandis Grand Fir    X X   X  Abrutus unedo Strawberry Tree    X   X  X Cedrus deodara Deodar Cedar    X   X  X Chamaecyparis lawsoniana Port Orford Cedar    X X  X X X Chamaecyparis nootkatensis Alaska Cedar    X X  X X X Colodecrus decurrens Incense Cedar    X      Photinia serrulata Chinses Photinia    X   X  X Page 206 of 260   57   Picea sitchensis Sitka Spruce    X  X X X  Pinus contorta Shore Pine   X X X  X X X Pinus contorta latifolia Lodgepole Pine    X   X  X Pinus densiflora Japanese Red Pine    X     X Pinus monticola Western White Pine    X X   X X Pinus nigra Austrian Black Pine   X X   X  X Pinus ponderosa Ponderosa Pine    X     X Pinus sylvestris Scotch Pine   X X   X  X Pinus thunbergii Japanese Black Pine    X   X  X Pseudotsuga menziesii Douglas Fir    X X  X X X Sequoidendron sempervirens Coastal Sequoia    X   X   Taxus brevifolia Western Yew    X  X X X  Thuja plicata Western Red Cedar    X  X  X  Tsuga heterophylla Western Hemlock    X  X  X X Tsuga mertensiana Mountain Hemlock    X      Page 207 of 260   58   Umbellularia californica California Bay Laurel   X X   X  X Deciduous shrubs Amelanchier alnifolia Western Serviceberry    X X X X X  Berberis species Barberry variety    X     X Callicarpa japonica Japanese Beautyberry    X      Cornus stolonifera Red‐Osier Dogwood    X X X X X  Enkianthus campanulatus Red‐Veined Enkianthus    X      Elaegnus species Elaegnus variety    X   X X X Euonymus alata ‘Compacta’ Winged Eunymus    X   X   Hamamelis mollis Chinese Witch Hazel    X      Holodiscus discolor Ocean Spray     X X X X X Hydrangea lacecap varieties Lacecap Hydrangea    X      Potentilla fruticosa Potentilla    X   X  X Physocarpus capitatus Pacific Ninebark      X  X  Page 208 of 260   59   Rhamnus purshiana Cascara Sagrada     X X  X  Rhus typhina Staghorn Sumac    X X   X X Ribes sanguineum Red‐Flowering Currant     X X  X  Rosa nutkana Nootka Rose     X X X X  Rosa rugosa Rugosa Rose    X   X  X Rubus parviflorus Thimbelberry    X X X  X  Rubus spectabilis Salmonberry    X X X X X  Salix species Willow variety      X X X  Sambucus racemosa Red Elderberry     X X X X  Spiraea species Spiraea variety      X X X X Symphoricarpos albus Snowberry     X   X X Syringa vulgaris cultivars Lilacs    X   X   Vaccinium parvifolium Red Huckelberry      X  X  Viburnum x burkwoodii Burkwood Viburnum    X   X   Evergreen shrubs Page 209 of 260   60   Arbutus unedo compacta Compact Strawberry Tree    X   X  X Cornus alba ‘Sibirica’ Siberian Dogwood    X      Cotoneaster species Cotoneaster variety    X   X  X Ilex crenata Japanese Holly    X      Kalmia latifolia Mountain Laurel    X      Ligustrum japonicum Japanese Privet    X      Myrica californica Pacific Wax Myrtle    X X X X X X Osmarea x burkwoodii Burkwood Osmarea    X     X Osmanthus delavayi Delavay Osmanthus    X   X  X Photinia frazeri Japanese Photinia    X   X  X Pieris floribunda Mountain Pieris    X   X   Pieris japonica Japanese Pieris    X   X   Prunus lusitanica Portugese Laurel    X     X Pinus Mugo Mugho Pine    X   X  X Page 210 of 260   61   Rhododendron species Rhododendron and Azaleas    X X  X X  Vaccinium ovatum Evergreen Huckleberry    X X X X X  Ground covers Arctostaphylos uva‐ursi Kinnikinnick    X X  X X X Berberis nervosa Cascade Mahonia    X X   X X Calluna vulgaris Scotch Heather    X   X   Caenothus gloriosus Point Reyes Ceanothus    X   X  X Cotoneaster microphyllus Rockspray Cotoneaster    X   X  X Erica carnea Winter Heath    X   X   Erica x darleyensis Mediterranean Heather    X      Euonymus fortuei Winter Creeper Euonymus    X   X   Gaultheria shallon Salal    X X X X X X Hypericum calycinum St. Johnswort    X   X   Ilex crenata varieties and cultivars Japanese Holly    X      Page 211 of 260   62   Mahonia species Mahonia variety    X   X   Pachysandra terminalis Japanese Spurge    X     X Sarcococca hookerana Sarcococca    X      Vinca minor Periwinkle    X   X  X Note: Medium street trees are recommended for planted medians only without tree grates. Source: Hough, Beck & Baird as modified by Galen Wright, Washington Forestry Consultants, Inc.     Page 212 of 260 City of Port Orchard  216 Prospect Street, Port Orchard, WA 98366  (360) 876‐4407  FAX (360) 895‐9029        Agenda Staff Report  Agenda Item No.: Business Item 7B Meeting Date: February 27, 2018  Subject: Adoption of an Ordinance Amending Prepared by: Nicholas Bond, AICP   POMC Chapter 2.78 Design Review  DCD Director   Board     Atty Routing No.: 115‐17    Atty Review Date: 2/22/18    Summary:  An ordinance to adopt new multi‐family and non‐residential Design Review Standards (POMC  Chapter 20.137) has been presented to the City Council.  Because Chapter 20.127 establishes a new process  for reviewing project applications against the Design Review Standards, corresponding amendments to  Chapter 2.78 (Design Review Board) are necessary to ensure consistency between the two chapters regarding  the role of the City’s Design Review Board.      Relationship to Comprehensive Plan:  N/A    Recommendation:  Staff recommends that the City Council vote to approve an ordinance adopting the  amendments to POMC Chapter 2.78.     Motion for consideration: “I move to adopt an ordinance adopting the amendments to POMC Chapter 2.78  as presented.”    Fiscal Impact: This proposal is not expected to impact the City’s budget.    Alternatives:  Direct staff and consultants to further revise the amendments to POMC Chapter 2.78.  (If the  Design Standards are adopted, amendments to Chapter 2.78 are necessary for their implementation.)    Attachments:  Ordinance Amending Chapter 2.78 and Redline  Page 213 of 260 This Page Intentionally Left Blank Page 214 of 260 ORDINANCE NO. __  ‐18              AN ORDINANCE OF THE CITY OF PORT ORCHARD, WASHINGTON, AMENDING  CHAPTER 2.78 (DESIGN REVIEW BOARD) OF THE PORT ORCHARD MUNICIPAL  CODE; PROVIDING FOR SEVERABILITY AND CORRECTIONS; AND ESTABLISHING  AN EFFECTIVE DATE.    WHEREAS, on June 13, 2017, the Port Orchard City Council adopted Ordinance 019‐ 17 establishing a new unified development code (Title 20 POMC); and    WHEREAS, on June 27, 2017, the Port Orchard City Council adopted Ordinance 022‐ 17 which created new Chapter 20.139 (Single‐Family Residential, Duplex and Residential  Fence Design Standards); and    WHEREAS, the City Council wishes to establish additional design standard  requirements that will apply to commercial, multifamily residential and mixed‐use  development; and    WHEREAS, City staff, in conjunction with consultants and a citizens design standards  committee, have developed design standards for commercial, multifamily residential and  mixed‐use development, to be codified as Chapter 20.127 (Design Standards); and    WHEREAS, an ordinance adopting a new chapter 20.127, repealing ordinance 1479,  and amending chapters 20.12, 20.38, and 20.100 in being considered separately from this  ordinance to amend chapter 2.78; and    WHEREAS, the design review process for project applications proposed to be  established in Chapter 20.127 requires corresponding amendments to Chapter 2.78 (Design  Review Board), to ensure consistency between these chapters regarding the role of the City’s  Design Review Board; now, therefore,     THE CITY COUNCIL OF THE CITY OF PORT ORCHARD, WASHINGTON, DO ORDAIN AS  FOLLOWS:    SECTION 1.  The City Council adopts all of the “Whereas” sections of this ordinance as  findings in support of this ordinance.    SECTION 2.  POMC Chapter 2.78 Revised.  Chapter 2.78 of the Port Orchard Municipal  Code is hereby revised to read as follows:    Page 215 of 260 Ordinance No. __‐18    Page 2 of 5  Chapter 2.78  DESIGN REVIEW BOARD    Sections:  2.78.010    Purpose of board.  2.78.020    Definitions.  2.78.030    Board established – Membership.  2.78.040    Terms of membership.  2.78.050    Meetings.  2.78.060    Powers and duties.  2.78.070    Conflict of interest.  2.78.080    Administrative support.    2.78.010 Purpose of board.    The purpose of the design review board (DRB) is:  (1) To provide recommendations regarding an applications’ consistency with the City’s  adopted design standards.  (2) To review completed projects and evaluate design outcomes for the purposes of  determining whether amendments to the design standards in POMC 20.127 should be  recommended, and to make recommendations to the Planning Commission and City Council for  amendments to the City’s Design Standards as found in POMC 20.127.    2.78.020 Definitions.  (1) “Board” or “DRB” means the design review board.  (2) “Director” means the Department of Community Development Director or designee.  (3) “Design standards” means the design and building standards adopted in sections  20.127.     2.78.030 Board established – Membership.  (1) Appointment. There is created a design review board consisting of not less than five  and not more than seven members who shall be appointed by the mayor subject to  confirmation by the city council. Vacancies occurring otherwise than upon the expiration of  terms may be filled for the unexpired terms by the mayor subject to confirmation by the city  council.  (2) Membership. A five‐member board shall consist of three lay members who reside  within city limits or reside within the Port Orchard urban growth area and have an interest in  architecture, building, or design, and two professional members who reside within city limits or  reside within the Port Orchard urban growth area or own a business within the city of Port  Page 216 of 260 Ordinance No. __‐18    Page 3 of 5  Orchard, and who are desired to have expertise in any one of the following fields: architecture,  landscape architecture, urban design/planning, structural engineering, graphic, industrial, and  interior design, building or carpentry, or similar disciplines. A seven‐member board shall consist  of four lay members and three professional members who meet the qualifications set forth  above.  (3) Compensation. Board members shall serve without compensation.     2.78.040 Terms of membership.  (1) Terms. The initial terms of the appointed positions by position number shall expire  on December 31st of the year set opposite said position number as follows:  Lay Position No. 1 – 2009;  Lay Position No. 2 – 2010;  Lay Position No. 3 – 2011;  Lay Position No. 4 – 2011;  Professional Position No. 5 – 2009;  Professional Position No. 6 – 2010;  Professional Position No. 7 – 2011.  Thereafter the terms of membership for members shall be three years.   (2) Removal. When a member misses three consecutive meetings without excuse by the  board, the position may be declared vacant by a majority vote of the other members of the  board.     2.78.050 Meetings.  (1) Meetings. The board shall meet at such times deemed necessary for conducting  business.  (2) Quorum. No business shall be conducted without a quorum at the meeting. A  quorum shall exist when the meeting is attended by a majority of the members of the board,  which may include the chairperson.  (3) Chairperson. The board shall elect one of its members to serve as chairperson for a  term of one year. The chairperson may be elected to serve one consecutive additional term, but  not for more than two successive terms.  (4) Voting. All actions of the board shall be represented by a vote of the membership.  Unless otherwise provided in this chapter, a simple majority of the members present at the  meeting in which action is taken shall approve any action taken. The chairperson may vote at  the meetings.  (5) Rules and Procedures. The board may adopt rules and procedures it deems  necessary for the conducting of business.     2.78.060 Powers and duties.  Page 217 of 260 Ordinance No. __‐18    Page 4 of 5  The board is not delegated any executive or legislative power, authority or responsibility  and is not acting on behalf of the city council or the mayor but rather serves in an advisory  capacity and makes recommendations. The powers and duties of the board shall consist of the  following:  (1) Application Review. Review applications for compliance with design standards as  prescribed elsewhere in this code and make recommendations regarding the consistency of  projects with adopted design standards.   (2) Annual Review and Recommendations.  The Board shall meet at least once annually  to review completed projects and evaluate design outcomes for the purposes of determining  whether amendments to the design standards (POMC 20.127) are required.  The design review  board shall make its recommendation, even if it recommends that no changes are required,  prior to December 31 every year.  (3) Such other design‐related matters as shall be referred to the board for review and  recommendation by the mayor or city council.     2.78.080 Administrative support.  The Department of Community Development shall provide administrative support for  the board.       SECTION 3.  Severability.  If any section, sentence, clause or phrase of this ordinance  should be held to be invalid or unconstitutional by a court of competent jurisdiction, such  invalidity or unconstitutionality shall not affect the validity of constitutionality of any other  section, sentence, clause or phrase of this ordinance.    SECTION 4.  Corrections.  Upon the approval of the city attorney, the city clerk and/or  code publisher is authorized to make any necessary technical corrections to this ordinance,  including but not limited to the correction of scrivener’s/clerical errors, references, ordinance  numbering, section/subsection numbers, and any reference thereto.    SECTION 5.  Effective Date.  This ordinance shall be published in the official newspaper of  the city and shall take full force and effect five on April 1, 2018.  A summary of this ordinance in  the form of the ordinance title may be published in lieu of publishing the ordinance in its entirety.                 Page 218 of 260 Ordinance No. __‐18    Page 5 of 5    PASSED by the City Council of the City of Port Orchard, APPROVED by the Mayor and attested  by the City Clerk in authentication of such passage this 27th day of February 2018.                               Robert Putaansuu, Mayor    ATTEST:            SPONSOR:                              Brandy Rinearson, MMC, City Clerk     Bek Ashby, Councilmember    APPROVED AS TO FORM:                       Sharon Cates, City Attorney           PUBLISHED:    EFFECTIVE DATE:    Page 219 of 260 1    DESIGN STANDARDS –    REVISIONS TO EXISTING CODE  CHAPTER 2.78   DESIGN REVIEW BOARD        Chapter 2.78  DESIGN REVIEW BOARD  Sections:  2.78.0102.78.010    Purpose of board.  2.78.0202.78.020    Definitions.  2.78.0302.78.030    Board established – Membership.  2.78.0402.78.040    Terms of membership.  2.78.0502.78.050    Meetings.  2.78.0602.78.060    Powers and duties.  2.78.0702.78.070    Conflict of interest.  2.78.0802.78.080    Administrative support.    2.78.010 Purpose of board.  The purpose of the design review board (DRB) is:  (1)  Tto review development applications associated with development in the downtown overlay district  area. The DRB will review applications and makeprovide  recommendations to the director of planning  regarding the an applications’ consistency with the City’s adopted design guidelinesstandards.   (2) To review completed projects and evaluate design outcomes for the purposes of determining  whether amendments to the design standards (POMC 20.127) should be recommended, and to make  recommendations to the Planning Commission and City Council for amendments to the City’s Design  Standards as found in POMC 20.127.     2.78.020 Definitions.  (1) “Board” or “DRB” means the design review board.  (2) “Director” means the director of planningDepartment of Community Development Director or  designee.  (3) “Design guidelinesstandards” means the design and building standards for the downtown overlay  district as now or hereafter adopted by city council resolution or ordinance.adopted in sections 20.127.  (Ord. 006‐08 § 1; Ord. 035‐07 § 1).    2.78.030 Board established – Membership.  (1) Appointment. There is created a design review board consisting of not less than five and not more  than seven members who shall be appointed by the mayor subject to confirmation by the city council.  Vacancies occurring otherwise than upon the expiration of terms may be filled for the unexpired terms  by the mayor subject to confirmation by the city council.  (2) Membership. A five‐member board shall consist of three lay members who reside within city limits or  reside within the Port Orchard urban growth area and have an interest in architecture, building, or  design, and two professional members who reside within city limits or reside within the Port Orchard  urban growth area or own a business within the city of Port Orchard, and who are desired to have  expertise in any one of the following fields: architecture, landscape architecture, urban design/planning,  structural engineering, graphic, industrial, and interior design, building or carpentry, or similar  Page 220 of 260 2    disciplines. A seven‐member board shall consist of four lay members and three professional members  who meet the qualifications set forth above.  (3) Compensation. Board members shall serve without compensation.     2.78.040 Terms of membership.  (1) Terms. The initial terms of the appointed positions by position number shall expire on December  31st of the year set opposite said position number as follows:  Lay Position No. 1 – 2009;  Lay Position No. 2 – 2010;  Lay Position No. 3 – 2011;  Lay Position No. 4 – 2011;  Professional Position No. 5 – 2009;  Professional Position No. 6 – 2010;  Professional Position No. 7 – 2011.  Thereafter the terms of membership for members shall be three years. No person shall serve more than  two full consecutive terms. An appointment to fill a portion of an unexpired term less than one year in  length shall not be considered a full term.  (2) Removal. When a member misses three consecutive meetings without excuse by the board, the  position may be declared vacant by a majority vote of the other members of the board.     2.78.050 Meetings.  (1) Meetings. The board shall meet at such times deemed necessary for conducting business.  (2) Quorum. No business shall be conducted without a quorum at the meeting. A quorum shall exist  when the meeting is attended by a majority of the members of the board, which may include the  chairperson.  (3) Chairperson. The board shall elect one of its members to serve as chairperson for a term of one year.  The chairperson may be elected to serve one consecutive additional term, but not for more than two  successive terms.  (4) Voting. All actions of the board shall be represented by a vote of the membership. Unless otherwise  provided in this chapter and Chapter 18.94 POMC, a simple majority of the members present at the  meeting in which action is taken shall approve any action taken. The chairperson may vote at the  meetings.  (5) Rules and Procedures. The board may adopt rules and procedures it deems necessary for the  conducting of business.     2.78.060 Powers and duties.  The board is not delegated any executive or legislative power, authority or responsibility and is not  acting on behalf of the city council or the mayor but rather serves in an advisory capacity and makes  recommendations to the director. The powers and duties of the board shall consist of the following:  (1) Preapplication Meeting. One member of the board shall, whenever possible, attend the pre‐ application meeting with staff and the proponent of a project that is subject to design guidelines. The  chairperson shall be responsible for ensuring that this duty is rotated among the board’s members.  (21) Application Review. Review all applications for building permits in areas having adopted design  guidelines compliance with design standards as prescribed elsewhere in this code and make  recommendations regarding the consistency of projects with adopted design standards. The board shall  review the application for consistency with the applicable design guidelines and make a  recommendation to the director.  Page 221 of 260 3    (3) Biannual Review. Not later than September 30, 2009, and every two years thereafter, provide the  mayor and city council with a written report setting forth the board’s assessment of the design  guidelines, in light of the applications reviewed in the prior two years, and recommending changes to  the design guidelines that are intended to reinforce the purpose of the design guidelines and to provide  greater clarity to applicants.  (42) Annual Review and Recommendations.  The Board shall meet at least once annually to review  completed projects and evaluate design outcomes for the purposes of determining whether  amendments to the design standards (POMC 20.127) are required.  The design review board shall make  its recommendation, even if it recommends that no changes are required, prior to December 31 every  year.  (3) Such other design‐related matters as shall be referred to the board for review and recommendation  by the mayor or city council.     2.78.070 Conflict of interest.  A member of the board shall not participate in review of a project for which the member has a conflict  of interest.   2.78.080 Administrative support.  The planning Department of Community Developmentdepartment shall provide administrative support  for the board.     Page 222 of 260 City of Port Orchard  216 Prospect Street, Port Orchard, WA 98366  (360) 876‐4407  FAX (360) 895‐9029          Agenda Staff Report    Agenda Item No.: Business Item 7C Meeting Date: February 27, 2018  Subject: Adoption of a Resolution Approving the Prepared by: Noah Crocker   Conversion from GAAP to CASH  Finance Director         Atty Routing No.: NA    Atty Review Date: NA    Summary:  GAAP accounting is a more complex and time‐consuming method of reporting with little added  value to the City.  GAAP accounting takes significant resources to implement and are increasing each year  with additional staff training, auditing costs, additional requirements, etc.    The state auditor has prescribed and authorized reporting requirements through the Budgeting, Accounting,  and Reporting System (BARS) manual for both GAAP basis and Cash basis methods of accounting.      Cash basis reporting will simplify the annual reporting process, thereby significantly reducing the staff time  required for preparation of the annual financial report and creating additional efficiencies.    Recommendation:  The Finance Department recommends converting to Cash basis of accounting to increase  efficiency of the City’s accounting system and the annual audit process.    Relationship to Comprehensive Plan: N/A    Motion for consideration:  I move to adopt a resolution authorizing the Finance Department to convert to  Cash basis of accounting for fiscal year 2018.      Fiscal Impact: N/A    Alternatives: Don’t authorize and provide staff with direction.    Attachments: Resolution  Page 223 of 260 This Page Intentionally Left Blank Page 224 of 260 RESOLUTION NO.  ________________    A RESOLUTION OF THE CITY OF PORT ORCHARD, WASHINGTON,  APPROVING THE CONVERSION FROM GAAP TO CASH     WHEREAS, RCW 43.09.200 requires the state auditor to formulate, prescribe, and install a  system of accounting and reporting for all local governments; and     WHEREAS, the state auditor has prescribed and authorized reporting requirements  through the Budgeting, Accounting, and Reporting System (BARS) manual for both GAAP basis and  Cash basis methods of accounting; and     WHEREAS, the Finance Director for the City of Port Orchard has recommended converting  to the Cash basis of accounting to increase efficiency of the City’s accounting system and the  annual audit process; now, therefore,      THE CITY COUNCIL OF THE CITY OF PORT ORCHARD, WASHINGTON, HEREBY RESOLVES  AS FOLLOWS:    THAT: the Finance Director is authorized to convert the City of Port Orchard to  the Cash basis of accounting as prescribed by the Washington State Auditor’s  Office Cash Basis BARS manual effective retroactive to January 1, 2018, the  beginning of the 2018 fiscal year.    PASSED by the City Council of the City of Port Orchard, SIGNED by the Mayor and attested  by the City Clerk in authentication of such passage this 27th day of February 2018.                   Robert Putaansuu, Mayor    ATTEST:            Brandy Rinearson, MMC, City Clerk         Page 225 of 260 This Page Intentionally Left Blank Page 226 of 260 City of Port Orchard  Council Meeting Minutes  Regular Meeting of February 13, 2018                  1. CALL TO ORDER AND ROLL CALL    Mayor Putaansuu called the meeting to order at 6:32 p.m.     Roll call was taken by the City Clerk as follows:     Councilmember Ashby Present   Councilmember Chang Present   Councilmember Clauson Absent  Councilmember Cucciardi Present  Mayor Pro‐Tem Diener Present  Councilmember Lucarelli Present  Councilmember Rosapepe Present    Mayor Putaansuu  Present     Staff present: Public Works Director Dorsey, Finance Director Crocker, Community Development  Director Bond, City Attorney Cates, City Clerk Rinearson, and Office Assistant II Whisenant were also  present.    A. PLEDGE OF ALLEGIANCE    Mayor Putaansuu led the audience and Council in the Pledge of Allegiance.    2. COUNCIL PHOTO   3. APPROVAL OF AGENDA    MOTION: By Councilmember Cucciardi, seconded by Councilmember Diener, to add the excusal of  Councilmember Clauson due to business obligations.     The motion carried.     MOTION: By Councilmember Ashby, seconded by Councilmember Lucarelli, to approve the agenda  as amended.    The motion carried.          Page 227 of 260 Minutes of February 13, 2018   Page 2 of 6   4. CITIZENS COMMENTS     Matt Murphy, with Port Orchard Chamber of Commerce, discussed the vacant buildings in the region,  and spoke in favor to the 640 Bay Street Development Proposal Presentation.     5. CONSENT AGENDA  A. Approval of Check Nos. 73648 through 73787 totaling $470,278.66; January Electronic  Payment Dates 1/1/2018 through 1/31/2018 totaling $19.476.08; and Bi‐Weekly Payroll  including Check Nos. 147854 through 147864 totaling $470.484.10.  B. Approval of January 16, 2018, Council Work Study Session Minutes  C. Approval of an Interlocal Agreement with Kitsap County for the Anderson Hill Road SW/SW  Old Clifton Road Roundabout Right‐of‐Way Acquisition Services (Contract No. 018‐18)  D. New Item: Excusal of Councilmember Clauson for Due to Business Obligations    MOTION: By Councilmember Cucciardi, seconded by Councilmember Diener, to approve the consent  agenda as presented.    The motion carried.     6. PRESENTATION    A. Proposal to Purchase and Develop 640 Bay Street    Mayor Putaansuu introduced the presenters regarding the proposal to Purchase and Develop 640  Bay Street.     Steve Sego, with Waterman Investment Partners, explained how they arrived at the proposal being  presented to the City and provided a presentation on the proposed development.    Steve Rice, with RiceFergusMiller Architects, reviewed the site and how they gathered the details to  create their proposed plan having an urban streetscape, 44 residential units, with 2 potential retail  tenants of a restaurant occupant and Kitsap Regional Library’s Port Orchard Branch.     Steve Sego introduced his colleagues, Robert Baglio with BJC Group and Wes Larson with SWG  Development, who collaborated on the project. Mr. Sego spoke to the potential retail tenants, the  off‐site parking, and invited the Council to asked questions.     Discussion was had on if the proposal includes vacating Frederick Street.    Wes Larsen spoke to the development in the Kitsap County Area; redeveloping Bainbridge Island,  Bremerton’s Spyglass Hill Apartments, approving upon and enhancing the character of downtown  Port Orchard.     Page 228 of 260 Minutes of February 13, 2018   Page 3 of 6   Discussion was also had on parking expectations, outreach to property owners, and the  Condominium Act in Olympia’s current legislation review.    7. PUBLIC HEARING    No public hearings were held.     8. BUSINESS ITEMS     A. Adoption of an Ordinance Revising the Shoreline Master Program    MOTION: By Councilmember Ashby, seconded by Councilmember Lucarelli, to adopt an ordinance  adopting the revisions to the Shoreline Master Program as presented.    The motion carried.  (Ordinance No. 006‐18)    B. Adoption of a Resolution Declaring a Winning Response to the 640 Bay Street Request for  Proposals    MOTION: By Councilmember Cucciardi, seconded by Councilmember Lucarelli, to adopt a resolution  declaring the proposal submitted by Waterman Partners LLC in response to the 640 Bay Street RFP as  the winning proposal and to authorize the mayor to negotiate for the sale and redevelopment of 640  Bay Street.     Discussion was had on how the Council would prefer to move forward on evaluating the property value  to determine fair market value, either through a broker’s price opinion or an appraisal.     Direction was given to move forward with a broker’s price opinion and bring back to council for review.     Clarification was made on; next steps, process of negotiations, review committee members, and  request for proposal advertisements.       The motion carried.   (Resolution No. 006‐18)    C. Adoption of a Resolution Approving a Contract with Reid Middleton, Inc. for the Annapolis  Creek Culvert Replacement 30% Design and Permit Coordination Project    MOTION: By Councilmember Lucarelli, seconded by Councilmember Chang to adopt a resolution  approving a contract with Reid Middleton Inc. for the Annapolis Creek Culvert Replacement 30%  Design and Permitting Coordination in the amount not to exceed $355,763.00 and documenting the  Professional Services procurement procedures.   Page 229 of 260 Minutes of February 13, 2018   Page 4 of 6   Public Works Director Dorsey discussed future culvert replacements, the requirements, and the  environmental impacts.     The motion carried.   (Resolution No. 004‐18 and Contract No. 016‐18)    D. Approval of a Lease Agreement with Kitsap Transit to Lease a Portion of 87 Sidney Avenue  Facility     MOTION: By Councilmember Diener, seconded by Councilmember Rosapepe, to approve a lease  agreement with Kitsap Transit for a portion of the facility located at 87 Sidney Avenue, as described  in the lease agreement presented.     Mayor spoke to the importance of the site’s use for Kitsap Transit.     The motion carried.  (Contract No. 019‐18)    E. Approval of the January 23, 2018, Council Meeting Minutes      MOTION: By Councilmember Ashby, seconded by Councilmember Chang, to approve council  meeting minutes as presented.     The motion carried. Councilmembers Cucciardi and Diener abstained.     At 7:43 p.m., Mayor Putaansuu recessed the meeting for a brief discussion on collective bargaining  and a 10‐minute executive session in accordance with RCW 42.30.110(2)(i) regarding potential  litigation. City Attorney Cates and Community Development Director Bond were invited to attend  and Mayor Putaansuu noted that action would be taken after the executive session.    After the Collective Bargaining Discussion Councilmember Diener recused himself on the executive  session regarding potential litigation and returned to the dais.     At 7:53 p.m., Mayor Putaansuu reconvened Council back into regular session.    F. New Item: Approval of Settlement Agreement with Kitsap County regarding Comprehensive  Plan    MOTION: By Councilmember Cucciardi, seconded by Councilmember Ashby, to approve Settlement  Agreement on CPSGMHB Case No. 16‐3‐0012.    The settlement agreement was brought forward from the City’s appeal of Kitsap County’s  Comprehensive Plan, on transportation issues that were in the capital facilities plan and  Page 230 of 260 Minutes of February 13, 2018   Page 5 of 6   development regulations related to concurrency. This settlement agreement allows road  improvements to be equalized throughout the county.     The motion carried.     Councilmember Deiner returned to the dais.     9. REPORTS OF COUNCIL COMMITTEES    Mayor Putaansuu reported the next Finance Committee meeting is scheduled on February 23rd.    Councilmember Ashby reported on the Economic Development and Tourism Committee, and the  next meeting is at 9:30am on March 12th.    Councilmember Lucarelli reported the next Utilities Committee meeting is scheduled on March 19th.  The Sewer Advisory Committee meeting is scheduled to meet April 18th at South Kitsap Water  Reclamation Facility. The Chimes and Lights Committee is scheduled to meet February 27th.    Councilmember Diener reported on the Land Use Committee.    10. REPORT OF MAYOR  Mayor Putaansuu reported on the following:   Spoke on potential dates for a Council Retreat;   Next steps on awarded funding for the Rockwell Pocket Park;   Motion needed to elect representative for the Kitsap Transit Board Composition Review  Committee;   Facebook Stats on Police “Fallen” Movie, Chimes and Lights, and Tremont Street Closure;   Port Orchard Community Day of Service scheduled for April 7th;   Townhall meetings Caldier at 9am and Young 12pm 2/17;   City Townhall tentative date 5/29 at 6:30pm, for single use plastic bags; and   Title change for Police Commander to Deputy Chief.      MOTION: By Councilmember Diener, seconded by Councilmember Ashby, approval to elect Mayor  Putaansuu as representative for the Kitsap Transit Board Composition Review Committee.     The motion carried.    Council directed the Mayor to send a letter to the WA Department of Commerce stating the City  Council will pledge to provide any additional funding needed to complete the Rockwell Street Pocket  Park project.    11. REPORT OF DEPARTMENT HEADS   Page 231 of 260 Minutes of February 13, 2018   Page 6 of 6   Public Works Director Dorsey reported updated on Tremont Street Project and Emergency Operation  Center.     Community Development Director Bond followed up on Vision 2050, as previously discussed by  Councilmember Diener.     City Clerk Rinearson reported on requested audio recording of Council Retreat and that AWC‐RMSA  accounted for all properties listed.     12. CITIZENS COMMENTS    Sandra Butler, Theresa Donnelly, Leah Spaulding, Margi Moore, and Kelly Syhre asked for the  Council to bring forward an ordinance prohibiting the sale of cats and dogs in retail stores. Stated  the request would be a preventative measure, as there currently are no stores in the City that sell  cats or dogs.     Councilmembers and Mayor Putaansuu spoke to the ordinance request and stated that it will go  before Land Use at the next committee meeting.     13. EXECUTIVE SESSION  Held earlier in the meeting.     14.   ADJOURNMENT    The meeting adjourned at 8:38 p.m. No other action was taken. Audio/Visual was successful.                  Brandy Rinearson, MMC, City Clerk  Robert Putaansuu, Mayor   Page 232 of 260 City of Port Orchard  216 Prospect Street, Port Orchard, WA 98366  (360) 876‐4407  FAX (360) 895‐9029          Agenda Staff Report    Agenda Item No.: Business Item 7E Meeting Date: February 27, 2018  Subject: A Motion Directing the Mayor to Pursue Prepared by: Nicholas Bond, AICP   the Opportunity Zone Program  DCD Director         Atty Routing No.: NA    Atty Review Date: NA    Summary:  The City has learned of a federal program administered by the WA Department of Commerce  related to economic development.  An Opportunity Zone program was created under the Tax Cuts and Jobs  Act of 2017.  The Opportunity Zone program was included in that Act, which is designed to provide tax  incentives to investors who fund businesses in low‐income communities.  Investors are able to defer paying  taxes on capital gains that are invested in Qualified Opportunity Funds that in turn are invested in distressed  communities designated as Opportunity Zones by the governor of each state. Up to 25 percent of the low‐ income census tracts in each state can be designated as Opportunity Zones.    There are two census tracts in Port Orchard that are eligible under this program, one of which includes most  of downtown Port Orchard.  If Council would like staff to pursue this program, the City will need to submit  documentation to the Department of Commerce making its case as to why we should be included in the  program.  Commerce is only able to select 25% of eligible census tracts for participation.  Considering our  recent adoption of the Mixed‐Use Pilot Program, staff believes that applying to include the census tract that  includes downtown in the program would make a strong case for inclusion.  With Council’s consent, the  mayor will work with staff to submit a letter to the Department of Commerce requesting that the downtown  area be included in this program.    More information on the program is available here:  http://www.commerce.wa.gov/growing‐the‐ economy/opportunity‐zones/    Recommendation:  Staff recommends that Council approve a motion to direct the Mayor to pursue the City’s  participation in the Opportunity Zone program, and prioritize the inclusion of the census tract that includes  downtown Port Orchard.    Relationship to Comprehensive Plan:  Participation in this program would help to implement numerous goals  related to downtown revitalization.      Motion for consideration: “I move to direct the Mayor to petition the Department of Commerce to  prioritize the inclusion of the census tract covering downtown Port Orchard in the Opportunity Zone  Program and to participate in the program.”    Page 233 of 260 Business Item 7E  Page 2 of 2  Fiscal Impact:  No direct impact to the City.    Alternatives: Do not participate in the program.    Attachments: Map showing eligible census tract areas in Port Orchard.  Page 234 of 260  Page 235 of 260 This Page Intentionally Left Blank Page 236 of 260 City of Port Orchard  216 Prospect Street, Port Orchard, WA 98366  (360) 876‐4407  FAX (360) 895‐9029          Agenda Staff Report    Agenda Item No.: Business Item 7F Meeting Date: February 27, 2018  Subject: Discussion of Vision 2040 Scoping Notice  Prepared by: Nicholas Bond, AICP   and Comment Period  DCD Director         Atty Routing No.: NA    Atty Review Date: NA    Summary: This is a continuation of the February 20, 2018 work study discussion item.  On February 20, 2018,  Council asked to continue the discussion to the February 27th meeting.    The City has been asked by PSRC to provide comments on the update to Vision 2040, with the new regional  plan to be called Vision 2050.  A copy of the scoping notice published by PSRC is attached.  Comments on this  scoping notice are due on March 19, 2018.  It is very important that the City think about how the region,  county, and city should grow between now and 2050.  The population forecasts that were just released by  PSRC calls for 1.8 million additional people in the 4‐county region by 2050!  A large part of Vision 2050 will  focus on deciding where these people will live and work and how they will move throughout the region.   There are several alternatives for how this growth can be accommodated as a region and we’ll want to  discuss the pros and cons of each.     A draft outline has been created and attached which the Council may or may not wish to use as the basis of a  comment letter from the City to PSRC.  Council may want to discuss its contents or may wish to take the  discussion in a different direction.    As you may recall from our comprehensive plan periodic update that was completed in 2016, Vision 2040 was  the first step in an 8‐year planning cycle.  Vision 2040 led to countywide planning policies that ultimately  required the City to plan for 8,235 more residents and 3,132 more jobs by 2036.  The contents of Vision 2050  will greatly influence our next comprehensive plan update in 2024 and will very likely result in new  population and employment targets, in addition to those previously allocated, which we will have to plan for  through zoning and infrastructure policies.     Vision 2040 can be viewed at: https://www.psrc.org/vision‐2040‐documents    Recommendation:  Discuss the City’s position and provide guidance to staff regarding drafting a scoping  comment letter.    Relationship to Comprehensive Plan:  The City’s 2024 Comprehensive Plan will be required to implement  Vision 2050.    Page 237 of 260 Business Item 7E  Page 2 of 2  Motion for consideration:  N/A    Fiscal Impact: The regional growth strategy has a direct relationship to future transportation grant funding  through PSRC.  Projects that support the regional growth strategy are eligible for competitive grant funding.    Alternatives: The purpose of the scoping notice is to begin identifying alternatives to be considered as part of  the SEPA review process that will lead to Vision 2050.  The alternatives will be evaluated to inform the policy  makers at PSRC.  One of the alternatives could be selected, or elements of each alternative could be  combined into a preferred alternative.  At this time, there are an endless number of alternatives that could  be considered, and the scoping notice will help to narrow down the number of alternatives to a few.  The  default option would be the no action alternative whereby we continue on the Vision 2040 path.      Attachments: Vision 2050 scoping notice, draft comment letter outline  Page 238 of 260 VISION 2050 Plan AND SEPA Scoping Notice February 2018 Page 239 of 260 PSRC is extending the region’s growth plan to 2050. VISION 2050 will build on the region’s existing plan, VISION 2040, to keep the central Puget Sound region healthy and vibrant as it grows. As the region prepares to add more people and jobs in the coming decades — about 1.8 million more people by 2050 — VISION 2050 will identify the challenges we should tackle together as a region and renew the vision for the next 30 years. Page 240 of 260 VISION 2050 Plan and SEPA Scoping Notice 1 Ways to Get Involved • Submit comments or questions about VISION 2050 scoping to VISION2050@psrc.org • Attend listening sessions to be held in each county (dates and locations on page 11) • Learn more about VISION 2050 and sign up for updates from PSRC at www.psrc.org/vision 6,000,000 5,000,000 4,500,000 4,000,000 3,500,000 3,000,000 2,500,000 2,000,000 1,500,000 1,000,000 2000 2010 2020 2030 2040 2050 3.4 million jobs 5.8 million people FORECAST (Draft) Population and Employment Growth in the Central Puget Sound Region PSRC’s draft forecast shows 1.8 million more residents and 1.2 million more jobs in the region by 2050. Sources: U.S. Census, Office of Financial Management, Employment Security Department, PSRC VISION 2040 helps to coordinate the local growth and transportation plans developed by cities and counties to make sure they are consistent with the Growth Management Act and regional transportation plans. The Puget Sound Regional Council (PSRC) is the planning agency for the central Puget Sound region, which includes King, Pierce, Snohomish and Kitsap counties. PSRC has specific responsibilities under federal and state law for transportation planning and funding, economic development, and growth management. PSRC is updating VISION to consider new information and perspectives about a chang- ing region. PSRC is seeking community input to shape the plan. What important regional issues should we focus on during the update? How should the region’s growth strategy be up- dated to plan for 2050? As we consider different ways to grow as a region, what impacts and actions should be evaluated through environmental review? Over the next two years, PSRC will work with cit- ies, counties, tribes, other agencies and interest groups, and the public to develop VISION 2050. PSRC will engage the public through surveys, workshops held throughout the region, formal comment periods, and input to PSRC’s elected board members. Page 241 of 260 VISION 2050 Plan and SEPA Scoping Notice2 Planning as a REGION Since 2010, the region has experienced significant growth with about 375,000 new neighbors calling the central Puget Sound home. Meanwhile, major infrastructure investments — like completing the 520 bridge and extending light rail from Everett to Tacoma to Redmond — are moving forward. The region has had important successes implementing VISION 2040, which helps to fulfill the goals of the state Growth Management Act (GMA). The plan has helped coordinate state and regional initiatives and supported local decisions. Cities are thriving. Regionally, growth is shifting towards more compact, sustainable development occurring within urban areas and cities, with cost effective and efficient services, reduced impacts on the environment, and positive health outcomes. At the same time, the region continues to face significant challenges, including the climb- ing cost of housing. Congestion from rapid growth is reducing access to jobs, services, and housing. While recent economic growth has been strong, prosperity hasn’t benefited every- one or all parts of the region. Finally, pressing environmental issues, such as climate change and preserving open space, require more collaborative, long-term action. VISION 2050 is an opportunity for cities and counties to work together to address the key challenges that extend beyond the boundaries of any single community. Page 242 of 260 VISION 2050 Plan and SEPA Scoping Notice 3 What is in VISION 2040? VISION 2040 is the region’s current plan for managing growth forecasted through the year 2040. The plan includes overarching goals, an environmental framework, a strategy to sustainably guide growth in the region, and multicounty planning policies. The plan also includes actions at the regional, county, and local level to make the plan a reality. VISION has six chapters ad- dressing the environment, development patterns, housing, the economy, transportation, and public services. The plan includes goals and policies to: • Protect and restore the natural environment and reduce greenhouse gas emissions. • Plan for growth in cities and urban centers, while reducing sprawl. • Improve the balance of jobs and housing across the counties. • Create more vibrant and resilient urban centers. • Support health, well-being, and active living. • Provide affordable housing choices to meet the needs of all residents. • Improve mobility for people and goods. • Maintain and operate the transportation system safely and efficiently. • Encourage a strong, diverse economy. • Provide services like solid waste, energy, and water systems to support the region’s growth. VISION 2040’s Regional Growth Strategy defines a role for different types of places in ac- commodating the region’s residential and employment growth. The strategy is organized around guiding most employment and housing growth to the region’s largest cities and urban centers. Other cities and unincorporated urban areas are expected to play a more modest role as locations for new growth. Outside the urban area, rural communities, farms and for- ests will continue to be a permanent and vital part of the region. Environmental review for VISION 2040 showed that, compared with a broad range of alter- natives, the desired growth pattern would have significant benefits for mobility, air quality, environmental stewardship, and healthy communities. Page 243 of 260 VISION 2050 Plan and SEPA Scoping Notice4 VISION 2040 Regional Growth Strategy VISION 2040 guides most new growth to cities and urban areas. Source: VISION 2040 Page 244 of 260 VISION 2050 Plan and SEPA Scoping Notice 5 Where Growth is Happening Growth has been focused in the urban area. In 2015, for example, 96% of new permitted housing was in cities and urban areas. Source: PSRC Building Permit Data 290,000 jobs have been added to the region since 2000, with strong growth in employment centers along the I-5 corridor. Source: PSRC Covered Employment Data Page 245 of 260 VISION 2050 Plan and SEPA Scoping Notice6 SCOPING and Environmental Impact Statement Process Determination of Significance and Request for Comments on Scope of Environmental Impact Statement PSRC has proposed to update and revise the long-range growth, economic, and transpor- tation strategy for King, Pierce, Snohomish and Kitsap counties. PSRC, as lead agency for environmental review, has determined that the proposal to update VISION 2040 is likely to have significant adverse impacts on the environment, and is therefore issuing a Determina- tion of Significance (DS). This notice announces PSRC’s intent to prepare a supplemental environmental impact statement (SEIS) on the proposed update to VISION 2040, pursuant to RCW 43.21C.030(2)(c). The SEIS will contain new information and analysis, and may also build on data and analysis contained in existing environmental documents, any of which may be adopted or incorporated by reference as appropriate, according to State Environmental Policy Act (SEPA) rules. The process will integrate SEPA and GMA to allow for consideration of environmental information as well as public input, and to assist decision makers in meeting the goals of GMA while identifying and mitigating probable significant adverse environmental impacts under SEPA. Under the SEPA process (WAC 197-11-408), PSRC is com- pleting a scoping period to inform the environmental review process for the VISION 2040 update. Pursuant to SEPA, PSRC is notifying the public of the intent to prepare an SEIS so that residents, jurisdictions, agencies, and tribes have an opportunity to comment on the scope of the impacts to be analyzed. Affected members of the public, jurisdictions, agencies, and tribes are invited, by this notice, to comment on alternatives, mitigation measures, prob- able significant adverse impacts, and licenses or other approvals that may be required. The method and opportunities for comment are provided on page 11. The official comment period on the scope of the SEIS will run through Monday, March 19, 2018. Page 246 of 260 VISION 2050 Plan and SEPA Scoping Notice 7 Input on Environmental Review PSRC is seeking input on environmental issues for analysis. Natural and built environment. PSRC has identified the following environmental areas for potential discussion in the SEIS: • Land use and population; employment; housing; transportation; air quality; ecosystems; water quality; public services and utilities; parks and recreation; environmental health; energy; visual quality and aesthetic resources. • The scoping process may be used to expand or narrow the environmental areas that need updated analysis. Additional issues that may be addressed. In addition to the areas listed above, PSRC contemplates that environmental analysis may address the following subjects, which may be modified in response to public comments and further analysis: • Housing affordability; economic inequality; social equity and access to opportunity; healthy communities; climate change adaptation and mitigation; demographic shifts or changing needs; and funding for infrastructure and other improvements. • Some issues may be addressed by existing information in the VISION 2040 Environmental Impact Statement (EIS). Other issues may require new information or analysis. Scoping Question: What issues should be considered for environmental review? $450,000 $400,000 $350,000 $300,000 $250,000 $200,000 $150,000 $100,000 $50,000 $0 Increasing Median Housing Costs Nationally, the region is at or near the top among peer regions in annual housing cost increases. $1,800 $1,600 $1,400 $1,200 $1,000 $800 $600 $400 $200 $0 2010 2011 2012 2013 2014 2015 2016 2017 Rents Home Prices Sources: Dupre+Scott, Zillow Page 247 of 260 VISION 2050 Plan and SEPA Scoping Notice8 Input on Assumptions, Themes, and Issues PSRC is seeking input on key assumptions to inform the plan update. This SEIS will build on the VISION 2040 EIS and include information analyzing the environmental impacts of updating VISION 2040. • Plan for 2050. A new regional forecast will show expected employment and population through 2050. PSRC is planning for 1.8 million more people and 1.2 million jobs by 2050. • Implement the Growth Management Act. VISION 2050 will continue to further the Growth Management Act’s objectives of preventing sprawl; conserving farmlands, forests, and open spaces; supporting more compact, people-oriented communities; focusing a significant amount of new employment and housing into vibrant urban centers; and coordi- nating between local governments. • Use VISION 2040 as starting point. PSRC will build on VISION 2040’s current framework — goals, policies, and Regional Growth Strategy — as the starting point for developing VISION 2050. • Focus on emerging and important issues. To efficiently use public resources and time, the plan update will focus on a limited set of issues that may benefit from additional regional discus- sion, coordination, and planning. Issues such as housing affordability, climate change, social equity, and shared economic prosperity have been discussed as key regional challenges. • Reflect the diversity of the region. The plan update will seek to reflect the demographic, cultural, geographic, and economic diversity of the region. • Review trends and actions. Key data trends will inform the update, as well as progress towards implementing the actions contained in VISION 2040. The update will identify actions and roles to realize the goals of VISION 2050 and outcome measures from which to measure progress. • Integrate recent initiatives. The update will consider recent initiatives of PSRC and part- ners, such as recent local comprehensive plan updates, the Growing Transit Communities Strategy, Puget Sound Clean Air Agency climate change targets, the Puget Sound Part- nership Action Agenda, and the Regional Centers Framework Update. • Acknowledge and leverage major regional investments. Since VISION 2040 was adopt- ed, voters have approved two Sound Transit ballot measures to expand high-capacity transit. Other regional transit agencies have expanded service, local governments have built key proj- ects, and the state adopted Connecting Washington to fund major transportation projects. The update will address the impact of these investments on regional policies and strategies. • Update the document. PSRC will review the existing plan for out-of-date information or statutory changes since the 2008 adoption of VISION 2040. PSRC will also look for opportu- nities to make VISION 2050 more accessible and usable. Scoping Questions: What regional issues should the plan address? What information should guide the update? Page 248 of 260 VISION 2050 Plan and SEPA Scoping Notice 9 Planned Regional Transit System (2040) Transit investments are planned throughout the region to provide more transportation options. Source: Regional Transportation Plan Page 249 of 260 VISION 2050 Plan and SEPA Scoping Notice10 Input on framework for considering modifications to growth strategy. One purpose of this scoping process is to gain information so that PSRC can craft a limited range of alternatives for analysis within the Draft SEIS. The existing Regional Growth Strategy will be considered in the context of recent and projected trends, adopted plans, infrastructure investments, and broad goals for the region. The wide range of alternatives studied for the VI- SION 2040 EIS provides a robust starting point for this process. Within the range of alternatives previously studied, several options may be available to modify the existing Regional Growth Strategy to more effectively achieve the region’s sustainability goals. The alternatives that will be developed will use the same assumptions and forecasts for growth through the year 2050. • No Action Alternative. A “no action” alternative must be evaluated in accordance with SEPA. In this proposal, the no-action alternative will be defined as continuing forward with the adopted growth patterns in VISION 2040, to essentially “stay the course.” The existing Regional Growth Strategy would be extended to reflect forecasts for 2050 without amend- ment or revision to growth shares or regional geographies. • 2050 Modified Regional Growth Strategy Alternative(s). A modified 2050 growth strategy(ies) may be defined and evaluated with modified regional geographies, adjusted growth allocations among counties and regional geographies, and/or actions to promote the desired pattern of future popu- lation and jobs. Scoping Question: How should the region’s growth strategy be updated to plan for 2050? Page 250 of 260 VISION 2050 Plan and SEPA Scoping Notice 11 Preview PROCESS Schedule and Anticipated Milestones in SEPA Process PSRC anticipates that a Draft SEIS will be completed in summer 2019 and a Final SEIS will be issued in spring 2020. Engagement Opportunities There will be many opportunities to provide input throughout the planning process, including PSRC meetings, workshops, surveys, online open houses, and opportunities to comment on the draft plan and environmental review document. PSRC is accepting comments on the VISION 2050 scoping from Friday, February 2, 2018, through Monday, March 19, 2018. We want to hear from you! What issues should be con- sidered for environmental review? What regional issues should the plan address? What information should guide the update? How should the region’s growth strategy be updated to plan for 2050? There Are Several Ways to Comment: SEPA Responsible Official: Erika Harris, AICP, Senior Planner E-mail: VISION2050@psrc.org U.S. Mail: ATTN: VISION 2050 Comment, 1011 Western Avenue, Suite 500, Seattle, WA 98104 In Person: March 1, 2018 / Growth Management Policy Board meeting / 10 am Fax: ATTN: VISION 2050 Comment, 206-587-4825 Visit the website: https://www.psrc.org/vision Listening Sessions: King County / February 13 / 3-5 pm .......................Union Station, Ruth Fisher Board Room 401 South Jackson Street, Seattle 98104 Pierce County / February 20 / 3-5 pm ....................Fife Community Center 2111 5 4 th Avenue East, Fife 98242 Snohomish County / February 22 / 3-5 pm .............Lynnwood City Hall 19100 4 4th Avenue West, Lynnwood 98036 Kitsap County / February 27 / 3-5 pm ....................Norm Dicks Government Center 345 6th Street, Bremerton 98337 Page 251 of 260 VISION 2050 Plan and SEPA Scoping Notice12 What is PSRC? The Puget Sound Regional Council (PSRC) is the regional transportation, economic develop- ment, and growth planning agency for the central Puget Sound — King, Pierce, Snohomish and Kitsap counties. It serves as a forum for cities, counties, ports, transit agencies, tribes, and the state to work together on important regional issues. Key responsibilities include: • Long range growth, economic, and transportation planning • Transportation funding • Economic development coordination • Regional data • Technical assistance The elected leaders of King, Pierce, Snohomish and Kitsap counties, the region’s cities and towns, port districts, transit agencies, and tribes direct PSRC’s work. Once a year, these elect- ed officials meet as a General Assembly to vote on major decisions and elect new leadership. Each month, an Executive Board makes decisions on behalf of the General Assembly with the input of several advisory boards made up of local elected officials and representatives of busi- ness, labor, environmental and community interests, as well as input from the public at large. Page 252 of 260 Funding for this document provided in part by member jurisdictions, grants from U.S. Department of Transportation, Federal Transit Administration, Federal Highway Administration and Washington State Department of Transportation. PSRC fully complies with Title VI of the Civil Rights Act of 1964 and related statutes and regulations in all programs and activities. For more information, or to obtain a Title VI Complaint Form, see https://www.psrc.org/title-vi or call 206-587-4819. Americans with Disabilities Act (ADA) Information: Individuals requiring reasonable accommodations may request written materials in alternate formats, sign language interpreters, physical accessibility accommodations, or other reasonable accommodations by contacting the ADA Coordinator, Thu Le, at 206-464-6175, with two weeks’ advance notice. Persons who are deaf or hard of hearing may contact the ADA Coordinator, Thu Le, through TTY Relay 711. Additional copies of this document may be obtained by contacting: Puget Sound Regional Council Information Center 1011 Western Avenue, Suite 500 Seattle, Washington 98104-1035 206-464-7532 • info@psrc.org • psrc.org psrc.org back cover image courtesy of: Bryan Reinbold, Local 302 Union OperatorPage 253 of 260 Puget Sound Regional Council Page 254 of 260 1 Outline of Vision 2050 Comments (Draft) Vision 2040 Part One – Towards a Sustainable Environment  The City is very supportive of the existing focus on environmentally sustainable growth, however, the existing plan is short on other important components of sustainability: o Quadruple bottom line. Part One should be expanded to include balanced discussion of all 4 legs of the sustainability “stool.” By emphasizing environmental policy above the other 3 legs of the stool, the plan does not balance all elements of a sustainable region.  Environmental – Sustainability (Seems to be the highest Priority) (Word “Enviro” occurs 62 times in Part One)  Social – Equity (Mentioned, but seems far less important than environment and economic concerns) (Word “Social” appears twice in Part One)  Economic – Prosperity (Mentioned, but seems secondary to environmental concerns) (Word “Econ” Appears 17 times in Part One)  Cultural – Vitality (Mentioned in intro, not discussed elsewhere in part one) (Word “Culture” appears once in Part One) o Fiscal Sustainability: The EIS should consider alternatives for ensuring fiscal sustainability of local government. Cities and counties within the region should grow in a more fiscally sustainable manner. Throughout the region there are unincorporated urban areas under county control that are fiscally unsustainable in terms of the costs of providing services and replacing infrastructure vs. the revenue that is generated to local governments. Because of this fiscal unsustainability, these areas have not been annexed. We should ensure that these areas (and all areas) grow to be assets rather than liabilities. Transportation funding from PSRC should support projects that won’t create long term liabilities that aren’t supported by the revenue streams from existing or planned development. Perhaps funds should be awarded only after verification that the project area is fiscally sustainable over the long term, and/or that legislative actions have been taken to make the area more fiscally sustainable. As part of an application process, cities and counties should be asked to identify barriers to growth in the vicinity of a candidate transportation project and take action to remove those barriers prior to seeking funding. o Under the Social – Equity category, Vision 2040 doesn’t discuss housing affordability. There are many alternatives for ensuring affordability, however a one-size fits all approach should be avoided. For instance, inclusionary zoning may be appropriate in Seattle or Bellevue, but would likely be a barrier to increasing housing supply in Port Orchard. o There is very little mention of Native American tribes in Part One. The one mention is not in a cultural context, but rather in regard to restoration work being performed by tribes. o The military and its regional significance is not mentioned in Part One. Part Two – Regional Growth Strategy  In terms of the missions of city and county governments, our plans, roles and growth strategies seem to say one thing but do another. Vision 2050 should clearly state that Page 255 of 260 2 cities are the preferred entities for urban growth and that a county’s role is to support expansion of cities, the annexation of urban areas, the incorporation of new cities. County governance is also preferred for rural, resource, and agricultural management and growth, and for coordination of multi-jurisdictional services such as health departments. As it is now, counties are competing with cities for urban growth and the one-time revenues that new growth provides. Counties should be doing more to encourage annexations, joint city/county planning, and incorporations of stand-alone urban growth areas. The local view of a county’s role varies greatly between counties and frequently what is spoken or written in a plan is not the same as what is practiced. Some counties more than others seem to be creating more fiscally sustainable urban development that is ripe for annexation or incorporation.  Regional Geographies – Metropolitan Cities, Core Cities, Larger Cities, Small Cities, Unincorporated UGA, Rural are the current Vision 2040 Geographies. Recent PSRC reports show that we are missing our regional growth targets in some geographies. Perhaps our 6 regional geographies don’t capture the diversity in cities and counties throughout the region. Additional geographies may allow us to direct growth in a more targeted way that maximizes the quadruple bottom line. One way to do this would be to create sub-geographies within the existing 6 types. o It could be beneficial to divide unincorporated UGAs into affiliated and unaffiliated (those that function as a city i.e. Silverdale). Silverdale (and areas like Silverdale) could be considered a large city within the regional framework since it is a standalone UGA that can’t be annexed by another city. o More growth could be directed to affiliated UGAs. This would possibly encourage annexation either because existing residents may seek to have more local control as provided within a city or because the counties would be forced to invest in infrastructure in support of growth which would ultimately make the areas more attractive to an adjacent city as a candidate for annexation. o LAMIRDs (or functional equivalent) could be split from or become or a sub category of the rural geography. Perhaps some growth in LAMIRDs be encouraged as urban lands become more constrained. o Perhaps we should create an island sub-geography. Bainbridge Island and Mercer Island are unique from their small and large city counterparts. There are unique infrastructure challenges facing islands. For instance, both have 2 ways in and out vs. many roads in and out of most other cities. Additionally, there are unique challenges related to providing water and sewer services on an island. o Small Satellite Cities (i.e. Eatonville, Wilkeson, Gold Bar, Buckley) could be treated differently than contiguous Small Cities (Edgewood, Milton, Normandy Park). Small Satellite Cities are typically connected to the region by state highways and by directing regional growth to these places, we could exacerbate regional transportation problems. Many of small satellite cities are also located outside of transit service areas. Directing more growth to contiguous small cities may be more sustainable in the context of the quadruple bottom line. o Small cities outside of transit service areas should be exempt from certain PSRC planning policy requirements. It is not reasonable to require slow growing towns of 400 people to complete technical planning documents with the same frequency as rapidly growing cities. Page 256 of 260 3 o Consideration should be given to the investment under ST3 in terms of those jurisdictions how are being served by light rail expansion. Perhaps cities that are being served by light rail should be a regional geography sub category under the 6 categories. These areas should be shouldering a larger share of the burden when it comes to accommodating 1.8 million more people compared to the cities that are not directly benefitting from that investment.  Consideration should be given to what happens after we as a region build out our existing cities and unincorporated UGAs. At some point it will be unreasonable to expect that reasonable measures to densify existing cities and UGAs will be sufficient for accommodating future growth. We need to evaluate how to grow once this occurs. Counties should begin evaluating long term (beyond 20 year) alternatives for growth. Policies should require an evaluation in advance of future updates to Vision to identify which lands would be most suitable for future growth based on utility capacity, transportation capacity, and quadruple bottom line considerations. This way, a predefined alternative will exist that can be evaluated in comparison to other alternative growth strategies. There are several alternative growth strategies that should be evaluated: o Keep generally fixed urban growth boundaries. This may be the most environmentally sustainable alternative but may not maximize social and cultural considerations. In terms of economic sustainability, it is not clear whether this alternative would be better or worse that expanding existing UGAs. o Expansion of existing UGAs into rural areas. Cities (other than those that are landlocked) like Port Orchard could expand UGA boundaries outward. This may address social and cultural concerns, but at the expense of the environment. In terms of economic sustainability, it is not clear whether this alternative would be better or worse keeping fixed urban growth boundaries as described above. o New compact high density (+/-100 Activity Units Per Acre planning requirement (64000-120000 dwellings units/jobs that are no larger than 1-2 square miles) sustainable satellite communities supported by high capacity transit. Building new compact well-designed transit-oriented development communities supporting a large population of people and jobs could maximize the quadruple bottom line approach in conjunction with preserving fixed urban growth boundaries. Counties could identify potential sites that are likely to be successful, such as sites in proximity of an amenity such as a tourism/recreational area or areas with access to existing rail corridors that are underutilized. Perhaps new technology or transportation solutions could play a role in the PSRC area becoming a global leader in that technology. Each county could be asked to identify 1-2 locations where a new sustainable city could be constructed. o Convert rural LAMIRDs to UGAs/cities. Convert a place like Southworth or Manchester to become a UGA/City. It is not clear whether this would be more or less sustainable under the quadruple bottom line considerations compared to a new city approach.  We need to decide whether cities ought to be reclassified as they grow (i.e. Port Orchard changing from Small to Large City). The alternative would be to have the regional geography classifications grow (i.e. a small city threshold going from <22,500 to Page 257 of 260 4 <35,000). There may be benefits to letting the geography grow with the region in terms of tracking progress towards meeting targets and implementing the growth strategy. Parts Three and Four – Planning Policies and Implementation  The region continues to grow more in rural areas than is envisioned in Vision 2040. We should more aggressively look to bend the trend. A major goal of Vision 2050 should be to protect and preserve the rural areas in between UGAs, LAMIRDs (or functional equivalents), and cities from development. The following graphs were provided by PSRC and show how the regional growth strategy are being implement in Kitsap County and the Region. Page 258 of 260 5  Regional transportation concurrency policies could be used as a tool to implement the regional growth strategy and bend the trend away from rural development and towards centers.  As we plan for the future, rural growth allocations could be split into Rural and LAMIRDs (or functional equivalent) or could remain as one regional geography and see growth spread evenly across rural areas.  Concurrency: Throughout the region, cities and counties use different transportation concurrency methods and standards. It may be beneficial to standardize these systems in some way. Concurrency policies are required in GMA, but inconsistent implementation can hugely interfere with achieving the regional growth strategy. If one jurisdiction has a lax concurrency standard, they could be encouraging more growth than has been allocated. Likewise, a city with too strict a standard could be preventing growth from occurring in accordance with the regional growth strategy. As a region, we could allow transit-oriented development areas to have a lesser concurrency LOS due to the presence of an alternative transportation strategy. In rural areas, we could require a higher level of service on road segments and at intersections to discourage growth that is likely to exacerbate congestion. Uniform standards would also simplify interjurisdictional mitigation of traffic impacts. Kitsap County - Specific Items for Consideration  High Capacity Transit in Kitsap County o Kitsap County needs to establish or explicitly state its policy not to establish long term countywide goals for providing high capacity transit connections aside from marine based transit and the existing bus network that utilizes existing roadways.  A Poulsbo to Bainbridge connection.  Connect the County to Gig Harbor, Tacoma, and Pierce County.  Transit to the Shipyard.  Connections between 4 KC cities. o Additional consideration should be given to expanding the passenger ferry network.  Silverdale to Seattle.  LAMIRDs to Seattle.  Intra-County marine connections. Page 259 of 260 This Page Intentionally Left Blank Page 260 of 260