Search results

Jump to navigation Jump to search
  • In addition to features for trip planning, [[OpenTripPlanner]] (OTP) includes analysis tools within the core software [[Category:GTFS-consuming applications]]
    2 KB (262 words) - 01:02, 10 February 2017
  • ...ixed guideway transit projects around the country. The rule specifies that applications for these projects require ridership forecasts for new lines, since mobilit ...n components with worker-flow tabulations from the [[Census Transportation Planning Package]]
    7 KB (938 words) - 22:27, 6 April 2017
  • |data_out= GIS shapefile, maps, trip generation estimates ...cts of changes to the transportation network on transportation demand. The trip generation estimates might differentiate by mode.
    5 KB (640 words) - 02:59, 7 April 2017
  • ...rogram written in C that has implemented multiple public transport journey planning algorithms. The software accepts [[General Transit Feed Specification|GTFS] [[Category:GTFS-consuming applications]]
    3 KB (395 words) - 01:46, 4 February 2016
  • ...ools for transit planning and operations analysis, and other categories of applications outlined in this article. ...t and Google then decided to team up to implement one of the first transit trip planners in Portland.
    18 KB (2,665 words) - 18:12, 2 December 2019
  • ...validation traditionally required specialized machinery, mobile validation applications developed by Masabi<ref>“Inspect Validation Suite.” Masabi.com. [http:/ ...isual verification, tickets are activated by the customer when beginning a trip and displayed to the fare inspector. One of the simplest mobile ticketing t
    18 KB (2,424 words) - 17:49, 4 December 2019
  • ...that when calculating travel time for transit, Sugar calculates the entire trip length, including walking to and from the station and wait time. Because st ...time is 2-4 hours<ref>Personal email contact with Matthew Pettit, Product Applications Engineer at Citilabs</ref>. Measuring transit accessibility tends to take l
    5 KB (738 words) - 00:29, 13 May 2017
  • |The ratio of one month of round-trip commuting to one month of poverty-line income. If a = average one-way fare |Average amount of time traveled between subsequent stops along a route trip.
    5 KB (805 words) - 23:39, 6 April 2017
  • ...ion systems should be placed in a way to help riders navigate their entire trip, rather than just at stations and stops. Signs, logos, color schemes, and o ...can result in extremely useful mobile applications, interactive maps, and trip planners; many cities now use [[general transit feed specification]] which
    9 KB (1,384 words) - 01:01, 18 February 2017
  • ...17/fulltext.pdf “International Study of Current and Potential Social Media Applications in Unplanned Passenger Rail Disruptions,”] Transportation Research Record ...tisfaction, but this information may also be quite useful in future agency planning which could save staff time in the long run.<ref name="penderetal" />
    17 KB (2,520 words) - 23:52, 1 May 2019
  • ...e are many vendors providing software for the transit industry for various applications. While the field includes a few large, well-known players, there are also s ...solutions which can incorporate various aspects of transit operations and planning into one procurement. Specificity about what your agency needs in a softwar
    7 KB (964 words) - 18:45, 9 December 2019
  • ...ng on the shoulder improves on-time reliability and even decreases overall trip time. ...urnalonline.trb.org/doi/pdf/10.3141/2111-02 Metaxatos, P., & Thakuriah, P. Planning for Bus-on-Shoulders Operations in Northeastern Illinois: A Survey of Stake
    15 KB (2,177 words) - 22:05, 17 January 2018
  • ...s query the Agency API when certain events occur in their systems, such as trip starts<ref name="github" />. This allows agencies to monitor mobility serv MDS data can be used to help inform transit planning by providing data on how many dockless mobility trips start or end at trans
    7 KB (1,021 words) - 23:51, 14 November 2019

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)