Network Data Translation Tools

AuthorDon Freeman, Sr. Transportation EngineerPresenterTom Cooney, Travel Forecasting Manager

Pima Association of GovernmentsTucson, AZ

Coding model input data is a time consuming exercise with many opportunities for error

Transit Line & Stop DataLINE NAME="1_UNIEB", MODE=6, COLOR=1, FREQ[1]=30, FREQ[2]=30, ALLSTOPS=F, ONEWAY=T, OWNER=1, N=3349, DELAY_C=0.4, N=3346, 3304, -1071, 1072, 3343, 3444, 3249, 3293, 3248, 3292, 3295, 3429, 3432, 3319, 3320, 3404, 2091, 2092, 2908, 2617, 2618, 2616, 2067, 2615, 2411, 2409,1188, 2410, 2407, 2408, 2405, 2251, 3681, 2252, 2634, 2633, 2635, 2999, 2104, 2103, 2932, 2419, 2418, 2421, 2154, 2153, 2685, 2684, 2686, 2184, 2204, 2203, 2702, 2701, 2704, 5485, 2207, 2206, 3014, 2834, -1031, -2802, -2801, -2841, -2968, -5488, 2193, 2195, 2693

Highway Node & Link DataA B DIST ATYPE CAP LANES LNKCLS SPEED WAY2 PAG_CID PAG_CNT ST_NAME6416 1112 0.92000 5 12750 1 3 43 2 2005219 3673 AJO HY6416 1177 1.83000 5 12750 1 3 43 2 2005219 3908 AJO HY6417 653 1.06000 9 99990 9 9 15 2 0 0 TAZ 653.016417 1112 0.43000 5 12750 1 3 43 2 2005213 3934 AJO HY6417 6006 0.74000 5 12750 1 3 43 2 2005213 3841 AJO HY6419 214 0.32000 9 99990 9 9 15 2 0 0 TAZ 214.046419 257 0.19000 9 99990 9 9 15 2 0 0 TAZ 257.036419 1114 0.12000 2 10690 2 4 31 2 0 0 RUTHRAUFF RD6419 2308 0.32000 2 10690 2 4 31 2 2006088 10840 WETMORE RD6420 1477 0.48000 4 11650 1 4 33 2 2006184 1689 LOS REALES RD6420 1478 0.57000 4 11650 1 4 33 2 2006184 1879 LOS REALES RD

Sucks!

Traffic CountManager

Most network data begins lifeas character-based information

And with locations specified by On-Street, From-Street & To-Street Names

Coding model input data is a time consuming exercise with many opportunities for error

Transit Line & Stop DataLINE NAME="1_UNIEB", MODE=6, COLOR=1, FREQ[1]=30, FREQ[2]=30, ALLSTOPS=F, ONEWAY=T, OWNER=1, N=3349, DELAY_C=0.4, N=3346, 3304, -1071, 1072, 3343, 3444, 3249, 3293, 3248, 3292, 3295, 3429, 3432, 3319, 3320, 3404, 2091, 2092, 2908, 2617, 2618, 2616, 2067, 2615, 2411, 2409,1188, 2410, 2407, 2408, 2405, 2251, 3681, 2252, 2634, 2633, 2635, 2999, 2104, 2103, 2932, 2419,

Highway Node & Link DataA B DIST ATYPE CAP LANES LNKCLS SPEED WAY2 PAG_CID PAG_CNT ST_NAME6416 1112 0.92000 5 12750 1 3 43 2 2005219 3673 AJO HY6416 1177 1.83000 5 12750 1 3 43 2 2005219 3908 AJO HY6417 653 1.06000 9 99990 9 9 15 2 0 0 TAZ 653.016417 1112 0.43000 5 12750 1 3 43 2 2005213 3934 AJO HY

Sucks!

Wouldn’t it be great if we could update network attributes based on street names rather than node numbers?

Wouldn’t it be great if we could create transit line and stop data based on street names rather than node numbers?

Good News: GIS might help!

Route Systems Route = ordered groups of links A bus route, a named street

Linear Referencing Procedures for locating “events” along a route Bus stops, intersecting roadways, number of lanes,

traffic counts, or any other route attributes

Highway Data Translation Tool

A non-GIS tool that automatically translates: From data with location specified using street name syntax:

To the same data with location specified using one or more a-to-b node links from the input highway network

Standard DBMS software is used to join the “translated” link-level data to the network link data and to manipulate link attributes.

ON-STREET FROM-STREET TO-STREET COUNT

BROADWAY BL ALVERNON RD WILMOT RD 19327

ANODE BNODE ON-STREET FROM-STREET TO-STREET COUNT

1521 1522 BROADWAY BL ALVERNON RD WILMOT RD 19327

1522 1976 BROADWAY BL ALVERNON RD WILMOT RD 19327

1976 1980 BROADWAY BL ALVERNON RD WILMOT RD 19327

2365 2370 BROADWAY BL ALVERNON RD WILMOT RD 19327

2370 2772 BROADWAY BL ALVERNON RD WILMOT RD 19327

Transit Data Translation Tool

A non-GIS tool that automatically translates to and from:

Transit line data (route name, mode, headway, and delay) and stops specified using street names:

Transit line and stop data specified using node strings from an input highway network:

Allows users to quickly and accurately move transit lines and stops from one network to another having different node numbers.

LINE NAME="1_UNIEB", MODE=6, COLOR=1, FREQ[1]=30, FREQ[2]=30, ALLSTOPS=F, ONEWAY=T, OWNER=1, N=3349, DELAY_C=0.4, N=3346, 3304, -1071, 1072, 3343, 3444, 3249, 3293, 3248, 3292, 3295, 3429, 3432, 3319, 3320, 3404, 2091, 2092, 2908, 2617, 2618, 2616, 2067, 2615, 2411, 2409,1188, 2410, 2407, 2408, 2405, 2251, 3681, 2252, 2634, 2633, 2635, 2999, 2104, 2103, 2932, 2419, 2418, 2421, 2154, 2153, 2685, 2684, 2686, 2184, 2204, 2203, 2702, 2701, 2704, 5485, 2207, 2206, 3014, 2834, -1031, -2802, -2801, -2841, -2968, -5488, 2193, 2195, 2693

LINENAME MODE OWNER FREQ1 DELAY ON_STR FM_STR TO_STR SEQ

1_UNIEB 4 1 30 0.4 6TH AV CONGRESS ST UNIVERSITY BL 1

1_UNIEB 4 1 30 0.4 UNIVERSITY BL 6TH AV PARK AV 2

1_UNIEB 4 1 30 0.4 PARK AV UNIVERSITY BL GLENN ST 3

Conclusions

Street name based coding is feasible With or without GIS tools

Street name based coding is a good idea It is node-independent It reduces coding errors It documents attribute changes It encourages checking

Forum for modeling related shareware and open source software?

TCOONEY@PAGNET.ORG