-
Notifications
You must be signed in to change notification settings - Fork 0
brainstorming features
Below are the notes from the brainstorming an prioritization session done using sticky notes. I've done my best to transcribe these faithfully; where there was no ambiguity or loss of information, I combined notes and simplified the text. For everything else, I copied the text verbatim.
The Positive and Negative columns correspond to the number of green and red dots the sticky received, respectively.
||Name||Category||Positive||Negative||
||Informative error messages/provide solutions, not error messages||User-facing||12||0||
||System external API and standard API between engine and interface||API||11||0||
||Data import modules and interoperability||data interoperability||10||0||
||Address geocoder||geocoder||10||0||
||Dynamic schedule data (service disruptions, real-time detours)||Real-time||10||0||
||Smartphone interface||User-facing||10||0||
||Real-time arrival algorithm||Real-time||8||0||
||Preferences (number of transfers, preferred mode, dwell time, lee-way time, bike amenity, cheapest trip, walking distance, ADA)||user parameters||8||0||
||Data validators (GTFS, import utility)||data interoperability||7||0||
||Packaging and developer resources||open source||7||0||
||Data admin interface||admin||6||0||
||Test harness||architecture||6||0||
||Feedback to data origin and fix/absence of data||fixing data||6||1||
||Route accuracy||User-facing||6||0||
||Web service (XML/JSON)||API||5||0||
||Scalable, multi-server, clustered, failover||architecture||5||0||
||Fares||data layers||5||3||
||Neighborhood layers, landmarks, fares (or just URLs), points of interest||data layers||5||0||
||Printing||User-facing||5||0||
||Analyze planned trips||admin||4||0||
||GTFS structure/database and import||data interoperability||4||0||
||Bicycle routes, lanes, parks, transportation, terrain||data layers||4||0||
||Variable walking/biking speed||user parameters||4||0||
||Ability to easily make changes to stops||admin||3||0||
||Role-based administration||admin||3||0||
||Logging and capture of trip variables (for site, pages, lat/lng, travel plans, etc)||API||3||0||
||Field trips||API||3||0||
||Fast algorithm||architecture||3||1||
||Open system technology||architecture||3||1||
||Portable||architecture||3||1||
||Open street map||data interoperability||3||0||
||ADA compliance/stops||data layers||3||0||
||Call-N-Ride/Para-transit||data layers||3||5||
||Walking (sidewalks, parking lots/paths/alternatives to standard streets, intersection info)||data layers||3||0||
||Bikes (elevation, safety, lanes, stop signs, parking/racks)||data layers||3||0||
||Future schedules||data layers||3||0||
||Fuzzy' time-based planning||exotic algorithms||3||2||
||Integration with car/bike-sharing systems||mode||3||0||
||Include/exclude routes||user parameters||3||3||
||User profiles||User-facing||3||0||
||Ability to save/share trips||User-facing||3||0||
||Diagnostic tool||admin||2||0||
||ESRI interface||data interoperability||2||0||
||User-specified data||data interoperability||2||0||
||Meta data on a route (wifi availability, walking accessibility, etc)||data layers||2||1||
||Geographic map rendering (?)||data layers||2||0||
||Transit sheds (reachability for open ended transportation)||exotic algorithms||2||0||
||Connect/link to remove standard adjacent trip planner||exotic algorithms||2||0||
||Highly multi-modal: bus, walk, bike, boat, ZipCar, etc||mode||2||0||
||Revision change control||admin||1.5||0||
||Data stating preview||admin||1.5||0||
||Reduce burden on agency to provide system data||admin||1||1||
||Mail merge||admin||1||10||
||Routes serving a location||data layers||1||0||
||Park and ride availability||data layers||1||1||
||Data interval flexibility||data layers||1||0||
||Traveling salesman problem||exotic algorithms||1||0||
||Sandbox for development and testing||admin||0||0||
||Hidden timepoint||data interoperability||0||0||
||Multiple origin, single destination||exotic algorithms||0||1||
||CRM interface --> problem with planned trip --> forward itinerary to agent for followup||fixing data||0||1||
||Integration with ride-sharing systems||mode||0||2||
||Support for pre-defined trips||User-facing||0||1||
||Persistent UI||User-facing||0||0||