Skip to content

Bike share open data desires

Jump to bottom Edit New page
dme212 edited this page Apr 10, 2014 · 1 revision
    1. Introduction
Currently in NYC, there are two efforts underway to build a foundation of bike share open data. First, BetaNYC and NYU Rudin are hosting a monthly hacknight around #BikeNYC data. Second, there is a pending bill in City Council to open up trip data on a quarterly basis. All of this is just a start.

To have the best informed position on what data to desire, this page is designed outline bike share best practices and who is sharing that data. Collectively, this page should be a listing of bike share data best practices and desires.

To improve this page, research other Bike Share Data Systems and integrate insights into this page. Don't forget to cite which cities are leading the way. If you are interested in looking at a sample bike share data schema, visit Bike Share Open Data Schema.

    1. System Data we would like to see...
In general, we would like historical data since the program launched.
      1. Trip Duration Data (Looking at Boston)
  • Trip ID
  • Start date and time
  • End date and time
  • Start station location
  • End station location
  • Bike number
  • membership type
  • Zipcode of rider (of registered user)
  • Age of rider (of registered user)
  • Gender of rider (of registered user)
      1. Station Information, Status, & Capacity (Looking to Paris)
  • Station Number
  • Station Name
  • Station Name (Secondary)
  • Station Address
  • Station Position (lat / Lng)
  • Station Payment Terminal Availability - Does the station have the ability to process credit/debit cards.
  • Station Terminal Availability - Is the terminal working
  • Installed Status - Yes / No (Looking at Boston)
  • Installed Date (Looking at Boston)
  • Removal Date
  • Installed Type - Permanent / Temporary (Looking at Boston)
  • Station Public - If the station is available to the general public. For bike stations that are part of the system but are locked off to the public. Industrial, Police, or Military installations.
  • Station Status (Open / Closed)
  • Station Stands Total
  • Station Stands Available
  • Bikes Available
  • Broken Bikes at station
  • Last communication with central server.
  • Last update from station.
    1. Performance Data
      1. Ridership (Looking to DC)
  • Number of trips per Month
  • Trip Origin/Destination by Municipality
  • Trip Origin/Destination by Station
  • Trips per Time Interval
  • Percentage of trips per time interval
  • Miles Travelled per Month
      1. Fleet Performance and Safety (Looking to DC)
  • Bicycles in Service
  • Fleet Maintenance (Number of Bikes Inspected/Repaired) per Month
  • Bicycles Damaged per Month
      1. Membership/Pass Status (Looking to DC)
  • Total Number of Users
  • New Members
      1. Customer Service Data (Looking to DC)
  • Stations Full or Empty - Number of Instances
  • Stations Full or Empty - Time Interval
  • Stations Full or Empty - Percentage of Instances per Time Interval
  • Stations Full - Instances of Additional Time Granted
  • Stations Full - Total Number of Extra Minutes Granted
  • Rebalancing - Number of Times Bicycles Picked up and dropped off at Stations
  • Customer Service Calls - Number of Incoming Calls and Lost Calls
    1. Other NYC Bike Data that should be open as part of the NYC bike ecosystem.
      1. City Bike Map Data
      1. Bike Parking
  • Bicycle Parking Racks location and capacity.
  • Bicycle Parking Shelters location and capacity.
      1. Bicycle Safety
  • Crash Data in an open format but with no personal identifiable information.
  • Abandoned bicycle reports geolocated and in an open format.
      1. Bicycle Ridership Statistics
  • Bicycle "Cycle counts" in a geo tagged and open format.
  • Bicycle Screen line counts in a geo tagged and an open format.
    1. The any Open Data Bike bill should be asking for...
      1. Formats
The bill shouldn't legislate specific formats. The bill should bring CitiBike Data (Availability, Performance, Usage, and Historical) into line with the City's existing open data law, [NYC](http://www.nyc.gov/html/doitt/html/open/local_law_11_2012.shtml).
  • A website and a commonly available non-proprietary format via programatic access, as defined via [NYC](http://www.nyc.gov/html/doitt/html/open/local_law_11_2012.shtml) Section 23-501.
  • All Citi Bike data should fall under compliance of [NYC](http://www.nyc.gov/html/doitt/html/open/local_law_11_2012.shtml)'s 23-502 license.
  • Data set policy and technical standards should fall inline with [NYC](http://www.nyc.gov/html/doitt/html/open/local_law_11_2012.shtml)'s 23-505.
      1. When it should take affect
  • Law should take effective immediately. Within 30 days of passing, the first disclosure of data (a subset of data should be prioritized). Within 90 Days of passing, all data should be available in download. Within 120 days, implementation of an API. If these deadlines are unachievable, a report must tell the public a timeline for access to this data.
      1. Frequency of Data Refresh
  • As near to realtime as possible via an [API](http://en.wikipedia.org/wiki/Application_programming_interface) as defined by [NYC](http://www.nyc.gov/html/doitt/html/open/local_law_11_2012.shtml), section 23-505.
Add a custom footer
Add a custom sidebar
Clone this wiki locally