Combining queueing delay and geometric delay - Part 2 - TRL Software
01344 379777software@trl.co.uk
TwitterYouTubeLinkedin
  • TRL Main Site
  • Careers
  • Publications
Top Menu
Search
Cart0
  • No products in the cart.

Subtotal: £0

View Cart Checkout

TRL SoftwareTRL Software
TRL Software
World Class Traffic & Transportation Software Solutions
  • Products
    • Junction & Signal Design
      • Junctions
        • ARCADY
        • PICADY
        • OSCADY
      • PCMOVA
      • TRANSYT
    • Traffic Control
      • MOVA
      • SCOOT®
      • Urban Traffic Control (UTC)
      • MotorGraph
    • Road Safety
      • iMAAP
      • Street Auditing
    • Economic Appraisal
      • HDM-4
    • Digital Asset Management
      • iROADS™
  • Services
    • Junction Analysis
    • Microsimulation Services
    • Signal Control
    • Road Danger Reduction
    • Software Development
    • Strategic Modelling
  • About
    • TRL Software
    • Quality Standards
    • Careers
  • News
  • Support
    • Training
    • Knowledge Base
    • Webinars
    • Videos
    • Support Options
    • Maintenance Agreement
    • Licensing
    • Online Store Help
    • Ideas Portal
    • FAQ
  • Contact
Menu back  
TRL Software > Support & Training > Articles > Combining queueing delay and geometric delay – Part 2

Combining queueing delay and geometric delay – Part 2

Strictly speaking, it is not possible to do this since the definition of queuing delay has an element of geometric delay in it. The element of overlap is the delay associated with drivers checking that it is safe to enter a junction. It can be argued that this delay is both an element of queueing delay AND geometric delay and hence ARCADY is in fact correct to show it the way it does, included in both. Clearly this does not help those wishing to obtain a combined figure for total delay. However, It should be noted that, if the geometric delay was to be re-defined in ARCADY and PICADY to exclude this overlap it would then not be possible to measure the queueing delay as is currently possible! I would suggest that anyone facing a request for a total value of delay should provide both the queueing and geometric delay tables separately with an explanation of the fact that there is an overlap. Alternatively there is an approximate representation of driver checking time given in TRL Supplementary Report SR810, although at the time of writing this, I have not sourced the origins of this ‘estimate’ of driver checking time and so cannot comment further on its usefulness. Furthermore, the size of the overlap (the ‘checking delay’) will tend to relatively small in comparison with the queueing delay.

Categories
  • ARCADY Modelling
  • ARCADY/PICADY/OSCADY Technical
  • Other products
  • PICADY Modelling
  • TRANSYT Modelling
  • TRANSYT Network Diagrams
  • TRANSYT Technical
Recent Articles

  • TRANSYT 16 Simulation Model

  • Automatically calculating future traffic flows using growth factors

  • Graphs showing sensitivity of geometric parameters

  • How can I transfer traffic data between Junctions and Excel?

  • Pedestrian crossing and blocking on the same road

Stay up to date with news from TRL Software

Sign up
Products
  • Junction & Signal Design
  • Traffic Control
  • Road Safety
  • Economic Appraisal
  • Digital Asset Management
Services
  • Junction Analysis
  • Microsimulation Services
  • Signal Control
  • Road Danger Reduction
  • Software Development
  • Strategic Modelling
Contact Us

01344 379777
software@trl.co.uk

TRL Limited
Crowthorne House
Nine Mile Ride
Wokingham
Berkshire
RG40 3GA

TRL Software
TRL Registered Office: Crowthorne House, Nine Mile Ride, Wokingham, Berks, UK, RG40 3GA. Registered in England, No. 3142272, VAT Registration 664 625 321.
© Copyright 2021 TRL. All rights reserved.
  • Sitemap
  • Terms & Conditions
  • Privacy Notice
  • Accessibility
Footer Menu