Traffic Queue Length Sample Clauses

Traffic Queue Length. A major concern about a TSP system is whether a TSP treatment will cause excessive delay for other intersection movements. To address this concern, a key MOE is the size of the traffic queue for each conflicting phase and the delays associated with those queues. Before and after analysis of traffic queue lengths can help answer whether queues significantly lengthen for movements not receiving the benefits of TSP treatments. Also, it helps understand TSP impacts on streets crossing the TSP corridors. In this study we manually collected sample traffic queue length data from recorded video images at TSP-enabled intersections within the SS-RTSP project. Signal cycle failures refer to the specific delay condition in which vehicles must sit through at least one complete signal cycle to pass through an intersection. This condition leads to considerable public frustration, and an increased occurrence of such failures is likely to result in more substantial “public resistance” to TSP than will a minor increase in intersection delay. Thus, it is a key measure reported to public officials. Signal cycle failures were extracted manually from recorded video data.
AutoNDA by SimpleDocs
Traffic Queue Length. ‌ We manually counted the traffic queue length in vehicles from field recorded video data. Table 8-8 shows the traffic queue lengths on cross-streets. Because of time constraints, we analyzed and summarized data only from Mondays. Table 8-8 Traffic Queue Length on Cross Streets in Phase One Test Intersection Cross-Street Average Queue Length Per Cycle Standard Deviation Maximum Median TSP Off Alderwood Mall Parkway South approach 2.65471 2.41476 14 2 36th Ave West approach 3.20079 2.58121 16 3 TSP On Alderwood Mall Parkway South approach 2.64318 2.43128 12 2 Alderwood Mall Parkway North approach 1.63679 1.40252 7 1 36th Ave West approach 3.27135 2.76868 16 3 We also used a paired t-test to compare the average queue length before and after TSP implementation. The t ratio was -1.578, the absolute value of which was smaller than the critical t ratio of 2.920 at p=0.05. Therefore, the change of the average queue length on cross-streets after the SS-RTSP implementation was not significant. The average traffic queue length slightly increased for about 0.07 vehicles per signal cycle when the TSP system was turned on. However, on the southbound corridor of the Alderwood Mall Parkway intersection, traffic queue length decreased for about 0.01 vehicles per cycle. This result may be due to regular traffic variations between the two study days. Standard deviations of queue length also increased a little for all three cross- streets when TSP was on. The maximum queue length stayed at almost the same level after the TSP implementation. On the southbound corridor of the Alderwood Mall Parkway intersection, the maximum queue length even decreased for two vehicles per cycle when the TSP system was on. The median value of traffic queue length remained constant before and after the implementation of the TSP system.
Traffic Queue Length. We manually counted the traffic queue lengths from field recorded video tapes. Because of time constraints, this analysis was conducted on two representative intersections on the SR 99 corridor. Table 9-8 shows the statistics for traffic queue lengths on the cross-streets of the two intersections. 164th Street Eastbound 4.412 2.377 12 4 174th Street Westbound – through 1.353 1.433 5 1 174th Street Westbound – Left turn 0.647 0.597 2 1 174th Street Eastbound– through 0.800 1.476 8 0 174th Street Eastbound– Left turn 3.983 2.344 12 4 TSP On 164th Street Westbound 4.471 3.229 13 3 164th Street Eastbound 3.829 2.172 10 4 174th Street Westbound– through 1.909 1.258 6 2 174th Street Westbound– Left turn 0.338 0.553 2 0 174th Street Eastbound– through 1.722 1.944 9 1 174th Street Eastbound– Left turn 3.654 2.591 10 4 As we can see in Table 9-8, when TSP was turned on, queue length decreased in some cases and increased in other cases. This is reflected by the unpredictable changes in queue length statistics, including standard variation, maximum queue length, and median queue length, in Table 9-8. Again, a paired t-test was applied to compare the average queue lengths at the test intersections before and after TSP implementation. The t ratio was -1.663, the absolute value of which was smaller than the critical t ratio of 1.962 at p=0.05. Therefore, the change in average queue lengths on cross-streets after the SS- RTSP implementation was not significant.

Related to Traffic Queue Length

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Non-Arm’s Length Transactions To the knowledge of the Company, after due inquiry, except as disclosed in writing to the Underwriters or in the Registration Statement, the Time of Sale Information and the Prospectuses, neither the Company nor any subsidiary is a party to any contract, agreement or understanding with any officer, director, employee or any other person not dealing at arm’s length with the Company or any subsidiary which is required to be disclosed by applicable Canadian Securities Laws.

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • Arm’s Length Transactions During the term of this Agreement, all transactions and dealings between the Trust Depositor and its Affiliates will be conducted on an arm’s-length basis.

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that Xxxxx has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, traffic.

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Arm’s Length Transaction The Bank acknowledges and agrees that the Underwriters are acting solely in the capacity of an arm’s length contractual counterparty to the Bank with respect to the offering of Notes contemplated hereby (including in connection with determining the terms of the offering) and not as a financial advisor or a fiduciary to, or an agent of, the Bank or any other person. Additionally, neither the Representative nor any other Underwriter is advising the Bank or any other person as to any legal, tax, investment, accounting or regulatory matters in any jurisdiction. The Bank shall consult with its own advisors concerning such matters and shall be responsible for making their own independent investigation and appraisal of the transactions contemplated hereby, and the Underwriters shall have no responsibility or liability to the Bank with respect thereto. Any review by the Underwriters of the Bank, the transactions contemplated hereby or other matters relating to such transactions will be performed solely for the benefit of the Underwriters and shall not be on behalf of the Bank.

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall xxxx the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall xxxx the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall xxxx the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Links to Third Party Websites In your use of the Service and/or the Company’s website, you may encounter various types of links that enable you to visit websites operated or owned by third parties (“Third Party Site”). These links are provided to you as a convenience and are not under the control or ownership of the Company. The inclusion of any link to a Third Party Site is not (i) an endorsement by the Company of the Third Party Site, (ii) an acknowledgement of any affiliation with its operators or owners, or (iii) a warranty of any type regarding any information or offer on the Third Party Site. Your use of any Third Party Site is governed by the various legal agreements and policies posted at that website.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!