MediaWiki API result

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Regional_Strategic_Planning_Model_(RSPM)",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "17": {
                "pageid": 17,
                "ns": 0,
                "title": "Real-time information",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[Image:SFMTA_RealTime.jpg|right|thumb|350px|The San Francisco Municipal Transportation Agency (SFMTA) offers real time arrival information on its train platforms. Photo by Flickr user AgentAkit.]]\n==Introduction==\nReal-time information, broadly defined, means any information available to transit providers or customers about the current status of vehicles, including approximate locations and predictive arrival times. Most real-time information relies on [[Automatic vehicle location|automatic vehicle location (AVL)]] and Global Positioning Systems (GPS) in order to estimate approximate arrival times for passengers and transit system operators. Passengers access real-time arrival and departure information through dynamic signs at stops and stations, or through the [[Internet communications|Internet]] at home or on smartphones. As smartphones become more prevalent, they have made access to third-party scheduling information and apps highly accessible for passengers.<ref name=\"enhancing\">National Center for Transit Research at the Center for Urban Transportation Research, University of South Florida.[[media:CUTR RealTime.pdf|\u201cEnhancing the Rider Experience: The Impact of Real-Time Information On Transit Ridership.\u201d]] 2005.</ref> \n\n==Features==\n===Mobile technology=== \nBecause cellular phones and smartphones are so prevalent today, they can be very useful for disseminating real-time transit information. Mobile phones allow passengers to use SMS (or Short Message Service) to access schedule and real-time information via text message. This is a two-way method of communicating wherein the passenger can send a text message to an agency, usually with a code for the stop they want information about. The agency then automatically sends a response with the next bus\u2019 arrival times. These services do not necessarily always use real-time information, instead responding with the next scheduled bus arrival time. However, real time information makes texting more useful to customers.\n\n===Dynamic messaging signs===\nThese signs at stops and stations tell passengers when the next transit vehicle will arrive and can warn them if a bus or train is delayed. They are also the most common method for agencies to communicate real-time information to passengers. These can be expensive to implement because of the costs of installation, maintenance, and electricity for operation.<ref name=\"tcrp91\">Transit Cooperative Research Program. [http://www.trb.org/main/blurbs/166249.aspx \u201cSynthesis 91: Use and Deployment of Mobile Device Technology for Real-Time Transit Information.\u201d] 2011.</ref>\n\n===On-board annunciators===\nReal-time information on-board buses and trains can include automated announcements of  next stops and upcoming transfer points. This feature also adds to ADA compliance and relieves drivers from this obligation.<ref>Transit Cooperative Research Program. [http://www.trb.org/Publications/Blurbs/153753.aspx \"TCRP Research Results Digest 5: Electronic On-Vehicle Passenger Information Displays (Visual and Audible).\"] 1995.</ref>\n\n=== Vehicle occupancy information ===\nAgencies can combine real-time vehicle location data with on-board [[automated fare collection (AFC)]] and/or [[automated passenger counter]] data to provide an estimate of how crowded a bus or train is, allowing customers to evaluate whether to wait for a vehicle that's likely to be full (and if the next vehicle is too full, whether there will be another one soon after). Transit agencies in Seoul<ref>Karlen, Leif. ''Innovative Governance of Large Urban Systems'', \"Case study: Displaying real-time bus occupancy levels in Seoul, South Korea\". 2017. http://iglus.org/case-study-displaying-real-time-bus-occupancy-levels-in-seoul-south-korea/</ref>, Singapore<ref>''Land Transport Authority'', \"Enhanced Real-Time Bus Information At Your Fingertips\". 2015.\n\nhttps://www.lta.gov.sg/apps/news/page.aspx?c=2&id=a759467d-4ff4-4bd0-9a78-79f7fb7772a4\n</ref>, and Sydney<ref>Reilly, Claire. ''CNET'', \"Real-time Opal data now lets you track how full your bus is\". 2016 https://www.cnet.com/au/news/real-time-opal-data-now-lets-you-track-how-full-your-bus-is-trip-view/</ref> offer this information to their bus riders. \n\n==Benefits and Costs to Agencies==\nUsing real-time technology can benefit agencies by improving safety and security, and has been demonstrated to increase customer satisfaction and perceptions of the transit agency. Agencies also benefit from these systems because they reduce the staff time needed to monitor for schedule adherence. \n\nThe costs of implementing these systems varies widely by the size of the agency, type of system, and which amenities the agency chooses to use.  Implementing a real-time system also has costs. There are financial costs, which can vary widely depending on the technology, as well as time and staff costs associated with training and maintaining real-time technologies. Sometimes the existing information technology infrastructure and staff are not sufficient, so they must be bolstered. Finally, as mobile technology is constantly changing, it is difficult for transit agencies and even technology developers to keep abreast of changes and to create mobile applications that will work for all versions of the wide variety of platforms available for passengers\u2019 mobile devices.<ref name=\"tcrp91\" />\n\n==Benefits to Riders==\nHaving access to real-time information reduces passengers\u2019 anxiety during wait time. It also reduces time spent waiting when passengers can learn about a delayed bus or other problem prior to arriving at a stop or station. This way, if buses are delayed passengers can make informed decisions about taking alternative routes or modes. After implementing AVL systems, combined with improving real-time information for customers, several agencies saw steep declines in customer complaints.<ref name=\"enhancing\" />\n\n==Implementation==\nTransit agencies that want to avoid the expense and risk of building a proprietary system to convey real-time information may work with vendors or produce data using established standards. See \n[[Category:Real-time applications]]\nfor a full list of real-time implementation applications.\n\n*'''General Transit Feed Specification-Real Time Format (GTFS-RT)''' [https://developers.google.com/transit/gtfs-realtime/]: Developed by Google as an extension to [[Providing GTFS data|General Transit Feed Specification (GTFS)]] and released via Creative Commons in 2011, [https://developers.google.com/transit/gtfs-realtime/ GTFS-RT] is a software-agnostic standard that allows public transportation agencies to provide realtime updates about their fleet to the public vis-a-vis application developers and [[Google Maps]]. The GTFS-RT standard allows transit operators to provide the following:\n:* Trip Updates - delays, cancellations, changed routes\n:* Service alerts - stop moved, unforeseen events affecting a station, route or the entire network\n:* Vehicle positions - information about the vehicles including location and congestion level\n:Agencies do not pay Google to use the format display the data on Google Products.  The GTFS-realtime specification is a free alternative to NextBus.com for agencies that currently produce or plan to produce real-time arrival data and route or stop specific service alerts.  [https://developers.google.com/transit/gtfs-realtime/ More information] is available from Google.\n\n*'''NextBus.com''' is a product offered by Cubic, a multi-national company with a software suite targeted to transit operators.  [[NextBus]] offers a full-service solution, from GPS installation on vehicles, to communications with users via a desktop and mobile web site.  NextBus is the market leader, with more than a dozen transit agencies as customers.  [http://www.cubic.com/Transportation/Solutions/Real-Time-Passenger-Information More information] about their products is available from the company.  ''This section is provided for informational purposes only and is not an endorsement to purchase the Nextbus product. See [[TransitWiki:General_disclaimer#Commercial Products and Services Appearing on TransitWiki]].''\n\n*[http://onebusaway.org/ '''The OneBusAway Project'''] is a free [[open-source software]] stack that seeks to make it easy for transit operators to build and maintain mobile applications which disseminate predictive real time arrival information. Originally started by a University of Washington Ph.D student named Brian Ferris, the OneBusAway software stack is the foundation for mobile applications maintained by MARTA, Hillsborough Transit in Tampa, Puget Sound, and the New York MTA. To build an application using OneBusAway, transit agencies do not require AVL equipment. [http://onebusaway.org/transit-agency-resources/].\n\n==References==\n<references />\n\n\n==Additional Reading==\nTransit Cooperative Research Program. [http://www.trb.org/main/blurbs/166249.aspx \u201cSynthesis 91: Use and Deployment of Mobile Device Technology for Real-Time Transit Information.\u201d] 2011. \n: This recent synthesis, sponsored by the Federal Transit Administration, includes a literature review and survey of transit providers, with a specific focus on the underlying technology necessary for delivering real-time information to passengers using mobile phones. Survey respondents reported that automatic vehicle location is the most commonly used technology for delivering real-time information and many agencies use third-party developers to develop applications for delivering this information to passengers.  \n\nTransit Cooperative Research Program.   [http://www.trb.org/Publications/Blurbs/152932.aspx \u201cTCRP Synthesis 48: Real-Time Bus Arrival Information Systems.\"] 2003. \n: This report, also sponsored by the Federal Transit Administration, describes the basics of how real-time information systems work and uses several case studies to demonstrate common agency experiences when using them on bus systems. It is a comprehensive document outlining broad system benefits and costs, customer reactions to the changes, and a literature review. This synthesis evaluates several case studies, including San Luis Obispo\u2019s transit system, which uses a real-time information system that utilizes dynamic messaging signs. The system was developed by the California State Polytechnic University and was fully deployed in 2001.\n\nTransit Cooperative Research Program. [http://www.trb.org/Main/Blurbs/152927.aspx \u201cTCRP Report 92: Strategies for Improved Traveler Information.\u201d] 2003.\n: This report updates previous reports on traveler information and includes a literature review of a variety of other reports on the same topic. It also examines the possibiliies for transit to take lessons from other industries, such as the airline or parcel delivery industries, in providing information to customers through the internet. The report was sponsored by the Federal Transit Administration.   [[Category:Technology]]"
                    }
                ]
            },
            "551": {
                "pageid": 551,
                "ns": 0,
                "title": "Regional Public Transportation GIS Architecture and Data Model",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "Many transportation planning organizations seek to better utilize public transportation data within a holistic planning process that involves other modes of transportation.  However, achieving this goal is difficult if obtaining current public transportation network data and integrating this information into an enterprise GIS database is very effort-intensive.\n\nThe Florida Department of Transportation (FDOT) District 7 identified the need to obtain and view spatial data from many public transportation agencies within the district and region to aid in their multimodal planning efforts.  A research team at the University of South Florida\u2019s National Center for Transit Research completed a prototype Regional Public Transportation GIS Architecture and Data Model in May 2012 <ref>Sean J. Barbeau, Khoa Tran, and Edward L. Hillsman. \"Development of a Regional Public Transportation GIS Architecture and Data Model.\" Accessed August 1, 2012 from https://github.com/CUTR-at-USF/RegionalTransitArchitecture/wiki</ref>.  The research project has produced tools that automatically download new GTFS datasets from the regional transit agencies and store them in the FDOT D7 enterprise geodatabase.  Additionally, a web-application has been developed to visualize and query transit data alongside other data, such as proposed, planned, and in-progress road construction projects.  The open-source software is available under the Apache 2.0 license on Github <ref>Sean J. Barbeau, Khoa Tran, and Edward L. Hillsman. \"Development of a Regional Public Transportation GIS Architecture and Data Model.\" Accessed August 1, 2012 from https://github.com/CUTR-at-USF/RegionalTransitArchitecture/wiki</ref>.\n\n==References==\n[[Category:GTFS-consuming applications]]\n[[Category:Network planning software]]"
                    }
                ]
            }
        }
    }
}