• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • You already know Dokkio is an AI-powered assistant to organize & manage your digital files & messages. Very soon, Dokkio will support Outlook as well as One Drive. Check it out today!

View
 

TransitCampBayAreaProposedSessions

Page history last edited by janass 14 years, 9 months ago

 

TransitCamp Bay Area Proposed Sessions

 

The Wiki Password is c4mp

 

Propose session ideas below for the TransitCampBayArea:

  1. Microformats & Transit brainstorming -- William Lawrence
    1. Problem: How to markup transit tables for trains/light-rail, buses, etc, in such a way that aggregation and navigation of schedules across varying transit systems becomes possible.
    2. Solution: Does there exist a solution within microformats, and if so what would be a good practice?
    3. Goal: After all the talks about Data Portability and standards, let's figure out how to mark-up HTML so the data can be repurposed.
    4. Reference:
      1. http://microformats.org/wiki/transit-table-examples
      2. http://microformats.org/discuss/mail/microformats-discuss/2005-October/001595.html

 

  1. Onboard Information:
    1. Problem: What information should be presented to passengers on board train/bus? What is the best way to present this information.
      1. For example: How to make the best use of the limited display space; How to make to most efficient use of the passenger's limited time to read/scan the information?
      2. The idea is to talk about static displays, as well as more sophisticated technological solutions which allow dynamic content (e.g., "this train currently running 15 min. late").
      3. Will there be a bus on the bus? Or will each new piece of equipment have it's own independent wireless radio and operator interface? What information on the bus should speak to each other (Reference J1708 wiring standard).

 

  1. 11:30 AM Room 1: New XML Schemas and Metadata for Transportation: Whiteboard Design Session for Data Geeks
    1. There's very little the world needs less than a new protocol. But the transit world is missing widely adopted protocols, which puts many next generation applications partially blind or on shaky ground. With GTFS having pretty much wrapped up the fixed route fixed schedule format, what else do we need? Which should be microformats, XML, or TSV files? In a Saturday brainstorming session we listed:
      1. Schema for describing anticipated schedule disruptions (e.g. parades, track work).
      2. Microformat for describing unanticipated schedule disruptions (e.g. flood, track closure).
      3. Twitter network for riders to tell other riders
        1. Delays
        2. Overcrowding
      4. Measuring crowding on a vehicle.
      5. Annotations to the road network layer, coding:
        1. Bicycle permeable barriers.
        2. Bike paths.
        3. Sidewalk quality.
        4. Pedestrian barriers which make otherwise reasonable connections impossible.
      6. Transit node amenities
        1. Restrooms
        2. Elevators
        3. Escalators
        4. Snack bar
        5. Taxi Stand
        6. Bike Lockers
        7. eLockers
        8. mail box (if privately owned?)
        9. DVD rental
      7. Parking spots
      8. Bike Repair (the moral equivalent to gas stations for cars)
      9. Protocol to check if a reservable mode is available now, in the future, and to actually book it (e.g. reserve a bike at CalTrain at 6pm):
        1. Level 1: Basic contact information, areas, costs, and locations of services provided.
        2. Level 2: Adds real time status to level 1 (e.g. "53 bikes available now").
        3. Level 3: Allows future queries as to availability and price of service (e.g. 10 bikes at 6pm, $1 per hour).
        4. Level 4: Allows reserving a future service (e.g. I want a bike at 6pm).
        5. Level 5: Integrated fare payment (e.g. Here's my credit cared).
      10. Modal shifting opportunities
        1. Taxi Stands
        2. Shared Bicycles
        3. Bike stations
        4. Bike shuttles
      11. Multi-modal Rideshare
        1. I'm going to ____ via ___ want to travel with me?
        2. An XML trip query/document format ( TripML )
        3. Automatically transferring a [car share/taxi/air taxi] booking to a social ride share.

 

Proposer: Bryce Nesbitt bryce aht citycarshare.org

Cosponsors: Dave Guerrieri aht www.garyair.us

 

  1. Bike Sharing and the "last mile" -- Sean Savage and Paul Bois, Call-A-Bike/FaberNovel
    1. Problem: How can we make it easier for people to get from their starting points to the nearest public transit stops, and from transit stops to their destinations? Do shared bicycles present a feasible and desirable solution? If so, what's the best way to fund such a system? (Private bike rental firms? Municipally-funded or nonprofit solutions? Public/private hybrids? Can/should bike sharing be publically subsidized?)
    2. Solution:
  2. Identify the "extreme users":
    1. Problem: IDEO's Tim Brown recommends observing "extreme users" to find ideas for innovation. So who are the "extreme users" as far as transit is concerned?
    2. Possible answers: first time travelers (tourists etc.), people who use the system a lot (commuters), people with disabilities... What can we learn from each class of "extreme users"?

 

  1. Cellphones and public transportation:
    1. Problem: How can cellphone be used to make the transit experience easier?
    2. Goal: Design an easy to implement solution that will enable travelers to receive real time updates regarding their planned and ongoing trip via SMS etc. keeping in mind the various transit systems that are part of most trips around the Bay Area.
      1. Share Project: Message Muni - A simple and forgiving text message service for SF Muni arrival times (John Vollmer)
    3. Less realistic goal: Find a way for the user information to be relayed back to the transit operators (e.g., "15 people on board Amtrak train 537 are going to miss their Caltrain connection since the train is running late") in the hope that they can make use of it to readjust schedules etc.

 

  1. Multimodal transport information in Paris
    1. Problem: how to make sure a rider knows where he will arrive, how he will get there and if there won't be any interruptions in his trip, providing him information on all transportation he can use.
    2. Solution: 1) information display and availability 2) making different realtime systems talk.
    3. Goal: Let's see how all agencies/companies can share their RT transportation data (+ congestion/perturbation data) and how we can distribute this information.
    4. Reference:
      1. Multimodal information screens: EDIM
      2. http://wap.ratp.fr/siv/home (iphone)
      3. RT transportation norms: transmodel / chouette / SIRI
  2. Mapping:
    1. Goal: Design the ultimate transportation map for the Bay Area!
    2. Problems: Online as well as paper maps; Logical versus geographical presentation; how to include schedule info on the map? etc.

 

  1. SimCity for keeps:
    1. Goal: Scenario modeling and visualization for citizens and decision-makers
    2. Problems: The current modeling process is centralized, and assumptions are not transparent. What if we could use visualization and modeling tools to consider the future of transit?
  2. Efficient Palo Alto of the Future: (12 noon or later works best)
    1. Problem: To meet 2050 carbon target, transform energy-hogging US suburban culture into cooperative problem solving green culture.
    2. Solution: productive social networking: communities of practice, dual online & physical/residential communities, local tipping point.
    3. Problem: Develop green, 100 mpg transit that competes well with the private auto for finicky Palo Alto users. Reduce driving by 50%+.
    4. Solution: Personal Rapid Transit + comprehensive new mobility {GPS phones, zimride + RideSpring, 511.org on steroids, Caltrain}. Single organization and single user interface provides ubiquitous access.
    5. Steve Raney, efficientPA.htm

 

  1. The Transit Gap: Low-wage transit riders versus higher paid commuters:
    1. Goal: Identify the information and technology gaps between low income and higher income riders that effect our perception of priorities in improving information on transit
    2. Problem: A transit system that depends increasingly on technology risks further marginalizing low income riders who are not as "hooked in" technologically.
    3. Solution:

 

  1. Title: topic -- presenter, etc
  2. ...
  3. ...
  4. ...

TransitCampBayAreaProposedSessions