Cruise time discrepancy of parallel bus and general traffic link - 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 > Cruise time discrepancy of parallel bus and general traffic link

Cruise time discrepancy of parallel bus and general traffic link

I have two parallel links (with the same link length) – one is for general traffic and the other is an adjacent bus-only link. Having looked at the relative cruise times I have noticed that despite accounting for different crusie speeds and the bus stopped- time there is still a discrepancy in the cruise times shown in the output. Why is this?

On top of the user-specified standing time of the buses on that particular link, TRANSYT adds on additional time (to the cruise time) to account for the deceleration and subsequent acceleration back up to the cruise speed on links that have bus stops. This time depends on the link length and cruise speed specified. E.g. the time taken to accelerate and decelerate is deemed to take about 16 seconds as long as the link can fully accommodate this manoeuvre within its length. For short links this time will not be accommodated and hence the additional time lost due to acceleration/deceleration will be less as a result. With a specified cruise speed of 30 km/h on a link which is over 60 metres long, this extra time is close to 9 seconds.

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