response in accessibility measure, both locally (for
individual network nodes) and globally.
However, the results lack generality. We are able
to test a single improvement by changing a travel
time, but we may suspect that other, untested
changes on the analysed edge yield different and
unexpected changes in accessibility. Though the
monotonic relation between travel time and
accessibility seems to be beyond discussion, the
exact magnitude and shape of this relation in
different parts of the network is unexplored. Also, in
the current practice, only positive changes have been
tested, but exactly the same procedure could be used
to simulate negative changes. What is needed is
general characteristics of a network edge over the
whole range of travel time variability. With fixed
edge length this translates to the range of travel
speeds. Due to complex formulation and graph
involvement, no analytic solution exists to simply
derive a range of accessibility values from a single,
base value. The only solution is numerical simulation.
In above circumstances, a strong, unifying
concept was necessary and it appeared as a
accessibility response profile (explained in
METHODOLOGY section). The other need is of
technical nature: existing OGAM software was not
designed to run multiple simulations in a systematic
way because the complete dataset must be modified
and model must be run again for each simulation.
3 METHODOLOGY
Figure 3 illustrates the concept of accessibility
response profile. X-axis runs along speed dimension,
from 0 value (no traffic) up to maximum allowed
speed (in case of Polish Traffic Code, 130 km/h). A
special point v
base
corresponds to actual, current
Figure 3: Generic accessibility response profile (exact
shape irrelevant).
value of speed on the link in the base model. Y-axis
runs along accessibility dimension. A special point
A
base
is actual, current value of accessibility
computed in the base model. A generic profile runs
from zero speed to maximum speed with ever
increasing A value and always crosses v
base
position.
Two parts of the profile may be distinguished
(see Figure 4): left part corresponds to negative
change usually related to congestion, accident
blocking, construction works or even complete
exclusion from traffic. This is the vulnerability area.
The bigger the area, the worse traffic disruption
occurs in case of negative event.
Figure 4: Profile functional structure.
The right part corresponds to improvements
resulting in increased speed due to construction (e.g.
surface or width improvement) or regulatory action
(higher speed limit, vehicle-type restrictions). This is
the amendability area. The bigger the are, the better
results may be achieved. A base point is neutral and
corresponds to current state of affairs. Please note,
that this “attachment” point for the profile is actually
not located in the middle, but on the right side for a
good road or left side for poor road. Thus, low speed
segments have small vulnerability area and cannot
do much harm to the network in case of failure. High
speed segments have small amendability area and
cannot give much improvement (in many cases they
have no amendability area at all).
Actual profiles given by series of simulations are
not smooth. They are approximated by nine speed
points, spread evenly across 0 – 130 km/h range.
Extra tenth value comes from the base model itself
and is computed once only. The test run results are
illustrated on Figure 5.
Observations on the shape, inclination and
attachment point give a complete information about
road segment’s importance and it’s influence on the
network. We may choose to observe the influence on
whole system or on particular node. This is why two
kinds of profiles will be computed: