Open Data: Challenges and Opportunities for Transit Agencies (2015) / Chapter Skim
Currently Skimming:
Pages 35-42
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 35... ...
36 The survey results show that almost all agencies providing open data see it as a way to maintain or increase ridership. Fifty-four or more than 96% of responding agencies that provide open data did not use any evaluation measures to assist them in deciding to open their data.
|
From page 36... ...
37 TABLE 4 RESPONDING AGENCIES Agency Name City State/Province/ Country Alameda–Contra Costa Transit District (AC Transit) Oakland CA Ann Arbor Area Transportation Authority (AAATA)
|
From page 37... ...
38 TABLE 4 (continued) Agency Name City State/Province/ Country Pinellas Suncoast Transit Authority St.
|
From page 38... ...
39 TABLE 6 REASONS FOR NOT PROVIDING OPEN DATA Reasons for Not Providing Open Data Number of Respondents Percent of Agencies Not Providing Open Data Too much effort to produce the data/we do not have the time or people to do the work required 5 38.5 Too much effort to clean the data 4 30.8 We cannot control what someone will do with our data 3 23.1 We do not know the accuracy of our data 3 23.1 2 15.4 It will put a strain on our systems 2 15.4 Proprietary vendor contracts preclude us from sharing data with third parties 2 15.4 Our agency is too small 2 15.4 Our data could be misused or misinterpreted Our agency will be liable if erroneous data are provided to the public 2 15.4 Our agency does not know how to open our data 2 15.4 There is a lack of interest internally 1 7.7 There is a risk-averse culture within our agency 1 7.7 Other (please specify) We are in the planning phases of opening our data, but the above have been our roadblocks.
|
From page 39... ...
40 TABLE 7 FACTORS IN DECIDING WHICH DATA TO OPEN Decision Factor Number of Respondents Percent Based on the ease of releasing the data 33 58.9 Based on observing what other transit agencies have done regarding open data 21 37.5 Decided internally without asking any groups outside our agency 17 30.4 Asked potential users of the data 11 19.6 Based on the cost associated with producing or cleaning the data 11 19.6 Asked the community in which your agency operates service 8 14.3 Asked riders 1 1.8 Other: Approached by Google. Approached by transit enthusiast.
|
From page 40... ...
41 FIGURE 28 Underlying technologies that generate open transit data (from survey responses)
|
From page 41... ...
42 FIGURE 29 Frequency with which open data are updated or modified (from survey responses)
|
From page 42... ...
43 How Agencies Make Data Available Number of Responses Percent Via your agency's existing website 39 69.6 GTFS Data Exchange website 18 32.1 As an application programming interface (API) 18 32.1 Via a separate agency website 12 21.4 Via a third-party site 11 19.6 Via a single regional centralized site 9 16.1 Public Feeds Wiki page on Google Transit Data Feed Google Code project 8 14.3 Providing data in bulk 7 12.5 Via an ftp site 3 5.4 Other: CD Bustools API IN-TIME platform (Co-Cities project)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.