a binational schema - its) canada fanucci_acgm... · a binational schema for cross-border data by...
TRANSCRIPT
A Binational SchemaFor cross-border data
by Melissa Fanucci
Senior Planner,
Whatcom Council of Governments
For ACGM 2013 - Toronto
Whatcom Council of Governments, Bellingham, WA ● 360-676-6974 ● [email protected]
What is an XML Schema?
Rules.
What is the Border Data Warehouse?
Wait times.
Traffic volume.
Service rate.
Two countries.
One database.
WSDOT data
Southbound
(to USA)
BCMOT data
Northbound
(to Canada)
Data are different.So find the common denominators
B.C. MINISTRY OF
TRANSPORTATION
WA STATE DEPT. OF
TRANSPORTATIONTRANSPORTATION
• Updates every minute
• Wait time by crossing
• Wait time by mode
• Volume
• Queue length (km)
TRANSPORTATION
• Updates every five minutes
• Wait time by crossing
• Wait time by mode
• Volume
• Queue length (mi)
Problems with the original schema
Repetitive information.
Timestamp issues.
Designed for time periods, not instances.
Not for all detector types.
Expanded Border Data Warehouse
Bluetooth wait times.
Three crossings.
Seven agencies.
U.S. border-wide archiveof common denominators
Cascade Gateway
PortalCascadeGatewayData.com
Niagara Region
PortalURL TBD
U.S.A. / Canada
PortalBorderDataWarehouse.com
Border Data Warehouse
(cloud server)
Wait times
Volume
Trucks, cars, NEXUS
Departure rate
WIM data
BTS data
Booth status data?
Wait times
Volume?
Booth status data?
New schema:
Inventory.
Everything must be made as simple
as possible. But not simpler.
- Albert Einstein
Inventory
Element Type Description
BorderCrossingData Root section
Organization_Id Unique identifier for the data feet )o/e/
WSDOT, BCMOT)
Describes details of system in one location
Inventory Top section for the inventory of detectors,
booths, lanes, and crossings
Detectors Type All the detector sections
Detector String (mandatory) Unique identifier for the detector
Detector.Name String (mandatory) Display name for the detector
Detector.Lanes Collection of lanes that are covered by the
detector
Detector.Latitude Enumeration (optional) Latitude of the detector.
New data elements
Detectors Type Description
Detector.Device.Type Enumeration
(mandatory)
Type of detector device (VDS, Bluetooth,
WIM, radar, other)
Element Type Definition
(open for comments)
Collection_Type String (mandatory) Period or instance
Collection_period_item Mandatory Section that defines the start/end of the
collection period
Collection_period_item.Date String (mandatory) Date in format yyyymmdd
Collection_period_item.StartHou
r
Numeric (mandatory) Start hour for the collection period 00-23
Collection_period_item.EndHour Numeric (mandatory) End hour for the collection period 00-23
Collection_period_item.StartM
inute
Numeric (mandatory) Start minute in 5 minute increments: 0, 5,
10, 15, 20, 25, 30, 35, 40, 45, 50, 55
Collection_Instance_Date Optional Date in format yyyymmddhhmmss
Architecture
U.S. CBP
CBSA
Peace Bridge
booth status data
WCOG
Cascade
Gateway Portal
WCOG
Border Data
Warehouse
WCOG
Niagara Region
Portal
MTO
Loop detectors
MTO
US-bound ATIS
system
WCOG
U.S. – Canada
Portal
U.S. CBP
Peace Bridge
booth status data
NYDOT
Corridor travel
times (toll tags)
BUFFALO BRIDGE
COMMISSION
Peace Bridge
vehicle counts
BUFFALO BRIDGE
COMMISSION
Border delay
websites/signs
NIAGARA FALLS
BRIDGE COMMISSION
Border delay
websites/signs
NIAGARA FALLS
BRIDGE COMMISSION
Bridge loop
detector data
NIAGARA FALLS
BRIDGE COMMISSION
Manual data
overrides
FREE AHEAD
Peace Bridge
Bluetooth system
FREE AHEAD
Rainbow Bridge
Bluetooth system
FREE AHEAD
Lewiston –
Queenston
Bluetooth Sys.
U.S. CBP
Border delay
website
CBSA
Border delay
website
Warehouse
Please contact me.
<?xml version="1.0" encoding="UTF-8"?>
<borderCrossingData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="borderCrossing.xsd">
<organization-id>BCMoT</organization-id>
<inventory>
<detectors>
<detector>
<id></id >
<name></name>
<device-id></device-id>
<device-type> </device-type>
<lanes>
<lane-number></lane-number>
Feedback?
Melissa FanucciSenior Planner
Whatcom COG
360-676-6974 <lane-number></lane-number>
<lane-number></lane-number>
<lane-number></lane-number>
</lanes>
<road-name></road-name>
<direction></direction>
<booth-id>4</booth-id>
</detector>
</detectors>
<booths>
<booth>
<id></id>
<type></type>
360-676-6974