30.66B.145 Concurrency determination-forecasting level-of-service.
(1) An inventory of developments that have been determined concurrent, also referred to as "developments in the pipeline," will be used to estimate future traffic volumes for forecasting future level-of-service conditions. This inventory will be established and maintained by the department of public works in accordance with the department’s administrative rules. Developments in the pipeline will also include developments given pre-application concurrency approval pursuant to SCC 30.66B.175.
(a) The department of public works shall use the inventory of developments in the pipeline when conducting analysis to determine whether an arterial unit is in arrears. Inventories or estimates shall be in accordance with the department of public works’ administrative rules.
(b) A developer may be required to provide a forecast of future level-of- service conditions to the department of public works for purposes of making a concurrency determination on a proposed development. When required to provide a forecast, the developer shall use the inventory of developments in the pipeline, as established and maintained by the department of public works, when providing a forecast of future level-of service conditions to the department. The inventory of developments in the pipeline used for making a concurrency determination on a proposed development shall not include any development that has been deemed concurrent subsequent to the proposed development.
(2) Estimates of future traffic volumes used for purposes of making level-of-service forecasts for concurrency determinations shall consist of the sum of the following: the current traffic volumes, the additional traffic volume that will be generated by the proposed development, and the additional traffic volume that will be generated by other developments in the pipeline.
(a) Estimates of current traffic volumes will be based on recent counts acceptable to the department of public works. The department of public works will provide them when available. When acceptable counts are not available, the applicant must provide them. The department of public works may specify by administrative rule the methodology for performing traffic counts of current traffic volumes.
(b) Additional traffic volume that will be generated by the proposed development will be based on the development’s forecast trip generation at full occupancy, in accordance with SCC 30.66B.130(3).
(c) The following shall apply to forecasting additional traffic volume that will be generated by the inventory of developments in the pipeline:
(i) the inventory of developments in the pipeline shall not include developments that have been deemed concurrent subsequent to the proposed development;
(ii) estimates of additional traffic volume that will be generated by the inventory of developments in the pipeline will include, at minimum, residential developments generating seven (7) or more peak-hour trips and commercial developments generating five (5) or more peak-hour trips that have been determined concurrent based on the department’s concurrency determination;
(iii) the department may, in its discretion, determine that certain developments in the pipeline should not be included in the inventory. The department may exclude a development, or part of a development, in the pipeline based on a factual demonstration by the applicant that one or more of the following is applicable:
(A) a development is not going to be constructed;
(B) a development is not going to be approved; or
(C) a development was already occupied at the time the current traffic volumes were counted; and
(iv) a threshold of three AM and/or PM peak-hour trips will be used for trip distributions.
(d) The department of public works will provide the applicant with the information in the department’s inventory of developments in the pipeline and the number of trips added to the individual traffic movements at the intersections on the identified arterial units.
(e) The department of public works will identify the arterial unit(s) for which an applicant must make estimates of future traffic volumes and specify the methodology for level-of-service forecasts used by the applicant in forecasting level of service from the estimates of future traffic volumes. Estimates of future traffic volumes may be required of the applicant for weekday a.m. and p.m. peak hour vehicle trips for any traffic movements on any intersection located on the identified arterial unit(s) including termini.
(f) Forecasts will analyze traffic impacts for arterial units in the development’s road system for the "forecast year" (i.e., the year of the proposed expiration date of the development’s concurrency determination). (Added by Amended Ord. 02-064, Dec. 9, 2002, Eff date Feb. 1, 2003; Amended by Amended Ord. 03-127 *see Code Reviser Note at beginning of Chapter, Nov. 5, 2003, Eff date Nov. 17, 2003).