INET &ROUTE M=4, L=41, ONEWAY=T, H=60, C=1, ID='RTE 41 SB ', -3779, -3831, -3887, -4001, -3999, -3995, 7117, -3977, -8389, -8409, -8383, -3975, -8415, -8417, -8403, -8397, -3903, -3447, 2183, -7837, -3853, -3825, -3823, -3821, -8473, -3819, -3847, -7833, -3455 /END

Palm Beach AM Peak Network

Palm Beach Line Attributes Route_ID Route_Name Track Time Distance Mode Line Company Reporting Headway Speed Label Comment Layover

Transit Network Issues Model Conversion - Line Databases Sources of speeds FSUTMS/Tranplan – Highway Network and “curves” TransCAD – Can assume a delay at each stop. Relationship between highway and transit speeds is whatever we specify. Conventions for coding stop? Should we use scheduled speeds?

Transit Network Issues Line attributes Node/Stop Attributes Time periods/Time of day Coding of auto connectors Coding of walk connectors Planning vs. Operational Analysis Other issues

TransCAD Transit Network Editing In general, if you are doing line edits on a network that a route system is based on, it's always a good idea to have the route system open at the same time, and to perform line edits in the following manner: 1. Perform a few line edits at a time. If you are also showing the route system, you'll see if the edits will affect your route system. 2. Switch over to the route system. TransCAD should detect that changes have been made to the line layer, and will prompt you to update the route system. It may also prompt you to create a new .net file. If you're not making changes to the route system, you do not need to make a .net file.