Using ONE HOUR (ODTAB) profiles - 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 > Using ONE HOUR (ODTAB) profiles

Using ONE HOUR (ODTAB) profiles

When using ONE HOUR (ODTAB) profiles, why does the total vehicles/hour in the final table of the ARCADY output file not match entered hourly counts?

Example: The hourly total count on an arm for, say, 08:00-09:00 is entered as 1000 PCU/hr, and a ONE HOUR (ODTAB) profile selected.

ARCADY will synthesise a peak demand profile that covers the central hour plus an extra 15-minute block either side of the central hour. The demand synthesised by ARCADY for each 15-minute time segment will therefore look something like this:

07:45-08:00 753 PCU/hr
08:00-08:15 899
08:15-08:30 1101
08:30-08:45 1101
08:45-09:00 899
09:00-09:15 753

The average over the central hour, i.e. 08:00-09:00, is (899+1101+1101+899) / 4 = 1000, which is the entered hourly count.

The average over the whole 90 minutes is slightly less: 918 PCU/hr. In other words, the average over the whole 90 minutes is slightly less than the entered hourly count because the synthesised profile includes a period either side of the central hour where the traffic demand is assumed to be lower than that measured during the central hour.

Using this profile type implies a number of assumptions, and of course the real demand profile at the junction may be completely different. For this reason, the ONE HOUR (ODTAB) profile should only be used if you know that the traffic profile at the junction follows a normal, typical peak period pattern.

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