1 / 9

Network Data Translation Tools

Network Data Translation Tools. Author Don Freeman, Sr. Transportation Engineer Presenter Tom Cooney, Travel Forecasting Manager Pima Association of Governments Tucson, AZ. Sucks !. Coding model input data is a time consuming exercise with many opportunities for error.

clovis
Download Presentation

Network Data Translation Tools

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Network Data Translation Tools Author Don Freeman, Sr. Transportation Engineer Presenter Tom Cooney, Travel Forecasting Manager Pima Association of Governments Tucson, AZ

  2. Sucks! Coding model input data is a time consuming exercise with many opportunities for error Highway Node & Link Data A B DIST ATYPE CAP LANES LNKCLS SPEED WAY2 PAG_CID PAG_CNT ST_NAME 6416 1112 0.92000 5 12750 1 3 43 2 2005219 3673 AJO HY 6416 1177 1.83000 5 12750 1 3 43 2 2005219 3908 AJO HY 6417 653 1.06000 9 99990 9 9 15 2 0 0 TAZ 653.01 6417 1112 0.43000 5 12750 1 3 43 2 2005213 3934 AJO HY 6417 6006 0.74000 5 12750 1 3 43 2 2005213 3841 AJO HY 6419 214 0.32000 9 99990 9 9 15 2 0 0 TAZ 214.04 6419 257 0.19000 9 99990 9 9 15 2 0 0 TAZ 257.03 6419 1114 0.12000 2 10690 2 4 31 2 0 0 RUTHRAUFF RD 6419 2308 0.32000 2 10690 2 4 31 2 2006088 10840 WETMORE RD 6420 1477 0.48000 4 11650 1 4 33 2 2006184 1689 LOS REALES RD 6420 1478 0.57000 4 11650 1 4 33 2 2006184 1879 LOS REALES RD Transit Line & Stop Data 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

  3. Traffic CountManager

  4. Most network data begins lifeas character-based information TIP RTP Bus Schedule And with locations specified by On-Street, From-Street & To-Street Names

  5. Sucks! Coding model input data is a time consuming exercise with many opportunities for error Highway Node & Link Data A B DIST ATYPE CAP LANES LNKCLS SPEED WAY2 PAG_CID PAG_CNT ST_NAME 6416 1112 0.92000 5 12750 1 3 43 2 2005219 3673 AJO HY 6416 1177 1.83000 5 12750 1 3 43 2 2005219 3908 AJO HY 6417 653 1.06000 9 99990 9 9 15 2 0 0 TAZ 653.01 6417 1112 0.43000 5 12750 1 3 43 2 2005213 3934 AJO HY Transit Line & Stop Data 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, 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?

  6. 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

  7. 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.

  8. 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

  9. 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

More Related