| 2.2.2 | 13/01/2023 | Changed | - New Zealand: economic factors, values adjusted to November 2021
|
| 2.2.1 | 30/03/2021 | Changed | - New Zealand: economic factors, values adjusted to July 2020
|
| 2.2.0 | 05/06/2020 | Changed | |
| Added | - A note referencing the Australian Transport Assessment and Planning (ATAP) guidelines three tiered "Options generation and assessment" process is displayed when an Australian jurisdiction is selected
- The model now accepts separate “value of delay” parameters for both pedestrians and vehicles, instead of applying the same value to both modes, to facilitate Australian jurisdictions whereby assessments are performed on the basis of the split of private travel, business travel and heavy vehicles as is consistent with Table 12 of the ATAP PV2.
|
| 2.1.4 | 09/08/2019 | Fixed | - Zebra with median refuge/Zebra with kerb extensions and median refuge now allowed if Median refuge/Kerb extensions with median refuge allowed and Zebra is only excluded due to "formal median refuge" requirement
- Bug incorrectly showing Zebra with kerb extensions and median refuge as suitable in certain situations
- If the existing facility relies on a parent facility (i.e. Zebra with platform) enable parameters for parent facilities (i.e. Platform) to be entered
- If the existing facility is Zebra with median refuge/Zebra with kerb extensions and median refuge then the other should be allowed (unless parent Median refuge/Kerb extensions with median refuge facility is not allowed)
|
| 2.1.3 | 15/07/2019 | Fixed | - Bug in calculation for zebra crossings in one-lane one-way environments
|
| 2.1.2 | 05/04/2019 | Fixed | - Tool crashing on Internet Explorer
|
| 2.1.1 | 18/02/2019 | Changed | - Updtes to disclaimer
- New support email address: support@abley.com
|
| 2.1.0 | 29/11/2018 | Added | - New Zealand: Safe and Appropriate Speed as a "do minimum" speed for calculating delays/disbenefits for vehicle occupants
|
| Changed | - Improved help tips in Request help or report a problem form
- All inputs above each calculation step are now treated as required, to make highlighting more clear
- New Zealand: economic update factors
- Expected crash reduction factors for zebra, zebra with platform and zebra with platform and kerb extensions to align with recent research
- Clarified how to determine peak volume times in tool help tips and user guide
|
| Fixed | - Inputs with errors not being highlighted in some cases
- Crossing Sight Distance calculation returning NaN when there is no median
- Vehicle delays not being calculated correctly for zebra with platform and kerb extensions
|
| 2.0.3 | 03/09/2018 | Changed | - Updated Austroads URLs for User Guide and Report
|
| 2.0.2 | 28/08/2018 | Changed | - Update internal support system URL
|
| 2.0.1 | 23/04/2018 | Fixed | - Tool would not calculate when using Internet Explorer 11
|
| 2.0.0 | 12/04/2018 | Added | - Annual maintenance cost for each facility type can be specified in the feasible facilities table (defaults to $0), incorporated into BCR calculation
- Crossing upgrade scenarios can be tested: existing facility is selected from a dropdown menu, the upgrade is used in the financial assessment of savings and BCR
- Help tips and information box to highlight how Wombat crossings can be assessed in Australian jurisdictions
- Facilities determined as unfeasible (or feasible only under certain conditions) now have the reasons for this determination stated in the Feasible facilities table
- Quick-start and help tip text to state that the tool cannot be used to assess crossings in locations with more than two lanes in any direction.
- In situations where a raised/painted median exists and is used by pedestrians (even though it has no formal protection) the tool can assess "no facility" to account for this reduced delay and Crossing Sight Distance (CSD). In these situations:
- Kerb Extensions, Platform and Zebra are no longer determined to be suitable without a formal Median refuge
- CSD for Signals calculated to account for the existing median, as with no facility
- Inputs for Signals with Kerb extensions account for existing median, if present, affecting the CSD
- Printable site information collection form, developed as a checklist and template to assist in collecting tool data during site visits, hosted by the tool.
|
| Changed | - Updated visual style
- Improved cross-browser performance of help tips and page alert/confirmation dialogues
- Improved file save/load function to include tool version checking/warning, visibility status and "show in final output" information
- Support system moved to ticket-based system
- Incorporated disclaimer and quick start guide into tool landing screen
- Zebra crossing confirmation delay calculated on the basis of vehicle flow from Easwarapadcham, Topp, & Koorey (2013)
|
| 1.2.0 | 09/05/2017 | Added | - Confirmation on Jurisdiction change (to indicate that data may be lost)
- File download/upload capabilities
|
| Changed | - Economic values:
- Average vehicle occupancy
- Average cost of pedestrian crashes
- Vehicle operating costs
- Value of delay
- Economic update factors (NZ)
- Crash Reduction Factors
|
| 1.1.0 | 09/03/2015 | Added | - Dropdown selector for jurisdiction
- Incorporated Zebra crossing feasibility criteria for South Australia and Tasmania
|
| 1.0.3 | 02/02/2015 | Changed | - Default crash reduction factors for Zebra crossings updated following working group decision
|
| Removed | - Load example values button
|
| 1.0.2 | 16/01/2015 | Changed | - Integrated contact page into tool page
- Minor layout and style updates
|
| 1.0.1 | 07/01/2015 | Added | - Access help functions from top bar
- Contact page
|
| Changed | - Minor layout and style updates
|
| 1.0.0 | 22/08/2014 | Added | - Estimated pedestrian crossing time calculation
|
| 0.9.12 | 30/07/2014 | Added | - Overall site characteristics intermediate outputs: total crossing distance and peak hourly vehicle flow
- Highlight (red text) of negative NPV/BCR values and positioned negative symbol before dollar sign
- Sight distances output for all facilities
- Additional input value checking
|
| Changed | - Zebra "may require approval" condition now based off posted speed
- Page text and help tips
|
| Removed | - Crossing distance check for facility built parameters
- Tactile paving/visual aids inputs (and hence comfort element of PLOS)
- Sight distance as part of feasibility criteria
|
| Fixed | - Fixed delay calculation for median refuge on 1-way 2-lane roads
|
| 0.9.11 | 17/07/2014 | Changed | - Improved dialogue information if platform negotiation speed set too high
|
| Fixed | - Minor usability and error highlighting bugs
- Grade separation suitability (grade separation not appropriate at intersections)
|
| 0.9.10 | 16/07/2014 | Added | - Darkening rows of non-suitable facilities if shown in Assessment output
- Link to PDF document describing the facility feasibility process
- Zebra + Platform + Kerb extensions and Signals + Kerb Extensions added to possible facilities
- Detailed analysis of grade separation
- Help tips regarding crossing distances of built facilities
- Help tip descriptions for PLOS outputs
- Text stating AADT and Daily Pedestrians should be from counts/estimates/surveys
- noscript checking (if JavaScript is disabled will show a warning message to the user)
- Force IE to use latest rendering engine
|
| Changed | - Mathematically simplified some equations
- Default values for some inputs
- Initial speed in VOC/travel time calculation for platforms: average vehicle speed is now estimated from 85th percentile approach speed
- Minor changes/updates to landing page text
- Changed some labels (i.e. Walkability -> PLOS)
- New facility feasibility decision trees
- Renaming around sensitive/non-sensitive pedestrians
- Incorporated sight distances into feasibility assessment
|
| Removed | - Non-compliance rate for signalised crossings
|
| Fixed | - Highlighting of errors with component facilities
- Australian update factor date defaults
- Minor bugs
- Field width for update factor dates (too narrow on some browsers)
|
| 0.9.09 | 09/07/2014 | Changed | - General usability improvements and checks for invalid inputs
- Pedestrian and vehicle delay calculations at signals
- Zebra and Platform now allowed on 1-lane 1-way roads as well as 2-lane 2-way roads
- Australian vehicle occupancy defaults to 1.2
- Pedestrian non-compliance rate at signals affects crash rate
- Platform feasibility based only on 85th percentile approach speed, previously highest value of posted and approach
|
| 0.9.08 | 07/07/2014 | Changed | - Output tables now hidden if user changes inputs
- Error boxes around inputs now disappear when valid inputs are entered
- Layout diagram images show white paint between directions, instead of yellow
|
| 0.9.07 | 04/07/2014 | Fixed | - NPV of vehicle delay calculation for facilities that include raised platforms
|
| 0.9.06 | 03/07/2014 | Changed | |
| Fixed | - Bug with assessment outputs
|
| 0.9.05 | 03/07/2014 | Changed | - Appearance, usability and functionality improvements
|
| 0.9.04 | 01/07/2014 | Changed | - Functionality improvements
|
| 0.9.03 | 01/07/2014 | Fixed | |
| 0.9.02 | 01/07/2014 | Changed | - Browser compatibility enhancements
|
| 0.9.01 | 30/06/2014 | Added | - Further input error checking
|
| Changed | - Browser compatibility enhancements
|
