Notes
Slide Show
Outline
1
Open Data/Open Source
Panel and Discussion
  • Mobility Program Workshop
  • Arlington, Virginia
  • December 1, 2010


  • James Pol, Moderator
  • U.S. DOT / ITS Joint Program Office
2
Purpose of Panel
    • Introduction – Definitions of Open Data/Open Source
      Randy Butler, RITA (10 min)
    • Open Data/Open Source Research Initiatives at Federal Level:
      • Open Data in the Clarus Program
        Paul Pisano, FHWA Office of Operations  (15 min)
      • Open Source Development for TRANSIMS
        Brian Gardner, FHWA Office of Planning  (15 min)
    • Open Data/Open Source Implementation Initiatives at Local Level:
      • TriMet's Experience with Open Source Software Implementations, Open Source Software Development, and Open Data
          •     Bibiana McHugh, Tri-Met (25 min)
    • Tools and Guidance for IntelliDrive Mobility:
      • IntelliDrive Open Source Mobility Applications Development Portal and Test Data Environment(s)
        Randy Butler, FHWA Office of Operations  (20 min)
3
Definition of Open Data/Open Source
  • Formal Definitions:
  • Open Data:
    •     Data and metadata are free and available for use without restriction; data are re-usable without requiring further permission.
  • Open Source:
    •     A method for collaborative development of software through peer input, review, and transparency. Methods, algorithms, and source code will be made available by participants to all.


  • In the Context  of IntelliDrive Mobility:
  •       Provide a Web location for broad sharing of  multi-source and multi-modal IntelliDrive data and source code while adhering to open source and detailed governance rules that protect the integrity, privacy, and quality of the data.
4
Definition of Open Data/Open Source
  • Why?  Philosophy: Gather once, reuse many times
  • Cost savings
  • Better quality, higher reliability, more flexibility, lower cost.
  • Open systems vs. proprietary systems


  • How?
  • Use of Open Source Licenses – Granting rights in support of a balance between collaboration and commercialization
  • Acquisitions – Identifying requirements and restrictions/limitations in contract language
  • Use of ITS Standards