2. Key topics to cover
The use of spatial databases
Underlying principles
Model data – infrastructure networks +network
options
The 4S model
Conclusions
3. Why does this matter?
We are no longer the custodians of data – we are more like
curators (collate and contextualise)
Need to be able to incorporate updates
Hierarchy of models – share across levels
Community of modellers – share between modellers and
platforms
Importance of auditing, licensing and change management
Less tedious more fun!
5. How Data is Stored – Traditional
Developed without reference to
recent developments in data
management
Stored in proprietary formats
File based data/consolidated data
bank
Data stored outside of the model
(e.g. GIS) – often deeply nested
folders of files on a network share
6. How Data is Stored - Improved
Well established approach – Relational Database
Management System (RDBMS)
Commercial and open source packages
Large data sets, spatial
Standardised access and analysis – SQL
Integrate with other systems (GIS, stats, custom)
Shared access, security and access control
7. Guiding principles
Robustness principle – Fuzzy not brittle
Be conservative in what you do, be liberal in what you accept from
others
Separate data and processing
BAD: Excel, GOOD: Database Queries
Data normalisation – never repeat data
[Every] non-key [attribute] must provide a fact about the key, the whole
key, and nothing but the key
Unified data – Everything goes in the database
Metadata – Data about data
Source, context, limitations
9. Data Sources
Govt street centreline data
Freely available but limited
Commercial products
Full routing information
License issues with derivative works
Crowd sourced (OpenStreetMap)
Road networks, points of interest, commercial centres,
schools, airports, parking and many other elements
Good quality – but some missing/inconsistent
Can fix errors/omissions
10. Network Geometry and Connectivity
Traditional approach:
Series of links and nodes
Anode, Bnode and fixed number of attributes
Semi-automatic/semi-manual process that creates a new
stand-alone artifact
Weaknesses:
Cannot distinguish defaults from overrides
Breaks links to original data sources
Hard to bring in update to external sources
Difficult to unify changes (node number conflicts)
11. The Goal
No manual processing in network creation
Repeatable, automatic process
Share process not all data
Fast enough to run every time
“Fuzzy" enough that it can still work even if there are
changes to the underlying spatial data
No node numbers!
12. Creating a network from GIS layers
Two ways of viewing a network
Geographically (polylines in GIS)
Topologically (links + nodes in transport model)
Conversion between these views
Network connectivity from spatial join
Cannot use exact coincident points
sensitive to minor changes
Not too fuzzy or else incorrect topology
14. Adding more detailed information
Need to add detail to source data (lanes,
capacities)
Common approaches – both break connection
Edit source data
Make model network and then edit
15. Our Approach – “Link Transitions”
A point with a
bearing (unit vector)
Specify start or end
of an attribute
change
16. Directional Points - Link Transitions
Bearing allows direction
Better identification when position data is ambiguous -
location + bearing eliminates most ambiguities
Remaining problems can be identified and solved through
more careful coding
Works with named roads – consistent with the way that we
think about roads
Robust when network changes – coordinates, added or
removed links
18. Option Coding
o Option Links
o Option
Connection
Points
o Option Link
Transitions
o Option Nodes
o All have
OptionCode
o Scenarios have
hierarchical sets
of OptionCodes
20. 4S
Structure
Stochastic:
● Monte Carlo methods to draw
values from probability
distributions
● Random variable parameters
● Number of slices can be
varied
SIMULTANEOUS
Segmented:
● Comprehensive
breakdown of travel
markets (20 private + 40
CV segments)
● Behavioural parameters
vary by market segment
EXPLICIT RANDOM UTILITY
Slice:
● Takes slices of the travel
market
○ across model area
○ through probability
distributions
● Very efficient – detailed
networks, large models
Simulation:
● Uses state-machine with
very flexible transition rules
● Simulates all aspects of
travel choice
● Complex public transport
● Multimodal freight
● Easily extended
21. Key features of 4S model
No matrices, no skims, no zones, no centroid connectors
All travel is from node to node
Models constructed with MUCH less manual effort
Include all roads, all paths, timetabled transit
Population and employment from multiple sources
Multimodal with all modes assigned
Continuous time and simultaneous choice
Easily include any demand based effects and capacity constraints (not
just roads and transit)
Much more detailed outputs (volumes by purpose)
22. Australia wide model
All roads except local streets
Some timetabled PT
Walk/cycle
Commercial vehicles
Runs in under 2 hrs (500k links, 400k nodes)
23. Detailed Australia model
All roads
Some timetabled PT
Walk/cycle
Commercial vehicles
Runs in under 8 hrs (2m links (2way), 1.5m nodes)
Commercial and open source packages - Oracle, Microsoft SQL server, IBM DB2, PostgreSQL and MySql/MariaDB
include just the additional information and tools necessary for downstream users to generate their own networks
extra information can be independently licensed, and downstream model users can obtain their own licence to the base data
Network Connection Points Algorithm
For each connection point
Find all lines within range (using manual tolerance)
For each line in range
Find the point of closest approach between the line and the connection point
Identify if the point is an endpoint or an intermediate point
If the intermediate point is close to the end of the line
Use the end point instead
Add the point to a set of adjustment points
If all adjustment points are end points
Extend each of the adjustment lines to the connection point
Else if only one adjustment point is an intermediate point
Extend all of the end point adjustment lines to the intermediate point
Else
Extend all end points to the connection point
Add a new mid point to all intermediate points to the connection point
However one problem remains - since we do not have a clearly gazetted road, how can we identify the start and end of each road. The only real candidate is to use the road name to determine road identity. This is somewhat problematic, since some roads are not named; there is not always consistency on when names change; and the same name could be used on multiple roads. In order to make the process work, we first construct a unique road name identifier. This is prepared by identifying contiguous sections of identically named roads; by requiring them to be contiguous we avoid problems of similarly named roads, and isolated sections of unnamed roads. Some flexibility in the contiguous test is desirable, though, since we have found that there are sometimes small sections of differently named roads and ramps and roundabouts that can sometimes break what should be a single road.
To simplify coding, and eliminate extraneous end points, we have adopted a range of different Link Transition types:
Merge Start - notes that the attribute changes at the closest intersection back from this point , and applies to all sections of this road until the end (unless an End Transition is found)
Split Start - splits the road at the transition point, and applies the attribute change
Merge End - notes the end of an attribute change at the next intersection forward from this point
Split End - splits the road at the transition point, and ends the previous attribute change
Single Link - applied an attribute change only to the specified link (however that has been defined)
Single Block - applies the attribute change from the previous intersection through to the next intersection
The link transitions are easily created in any GIS system
OptionLinks - this contains all the new links that are to be added in any scenario (includes link attributes)
OptionLinkConnectionPoints - shows where the new links should connect to the existing network
OptionNodes - identifies nodes that are added or changed in any scenario (includes node attributes)
OptionLinkTransitionPoints - shows the start and stop of any changes in link attributes (includes link attributes)
There are complexities in updating a timetable to incorporate congestion because any change in a stop-to-stop time will alter the whole timetable and is likely to have follow on effects on other services that use the same vehicle. We have explored methods to address this problem but they are beyond the scope of this paper.
Can build from OpenStreetMap and GTFS
We have focused on SEQ – combines 3 cities, also some rural areas