Click to edit Master text styles

Second level

Third level

Fourth level

Fifth level

‹#›

The USDOT research initiative for wirelessly connected vehicles, travelers, and infrastructure includes the Real-Time Data Capture and Management (DCM) Program.

The goal of the DCM program is to provide data that supports connected vehicle application development including enhanced weather and environmental applications, real-time transit signal priority, traveler information, fleet management applications, and safety advisory systems.

-Just read through the Purpose of the OSA

-Objectives:

-Collaborative development – one of the primary goals of the project to create an environment that cultivates friendly dialog between users and developers in a effort to create and enhance existing transportation applications.

-Transparency –By removing the unknown factor of the software by having everything available and open to the users and developers, including full access to the source code, the community as a whole can create better applications. This type of access allows users to understand exactly how a application will work and then make changes as needed to improve it’s use under different environments, security measures, and many other facets of the application.

-Reusability – The DMA program is working to change the old software paradigm that software is typically only used for one project then forgotten. The new OSADP paradigm is each application information can be captured and used again in future projects. Now do we believe that each application can be used as-is for each new projects, in a perfect world that would be true, but most likely the application overall information including the source code, documentation, and lessons learned will hopefully provide users of the OSADP a strong starting point for new applications with similar goals.

-Provide complete application packages – To make this all work the OSADP has to provide applications that include all of their required information. This includes the source code, licensing information, user guides, test data sets where possible and system documents for the applications

Application download page – The main feature for the OSADP is the application download page where users can download the applications. This page provides users with a description of the applications, its version, release date, and link to download the applications and all of its files.

Information on new applications – the site main page provides a series of news articles that mostly cover new applications that are added to the site. This news feed can also cover new features to the site and is available as an RSS feed.

Resources to use application and OSADP – The site also provides general information and guides on how to use the site and upload new code

Platform to test (GitHub) – To allow for continues development of the applications and to validate submitted applications against OSADP requirements the OSADP site uses GitHub. GitHub is a web-based versioning repository were applications are stored and checked before they are upload to the OSADP. GitHub firewalls the OSADP from code that is not ready for posting and also allows developers of that code direct access to the development version of the software.

Application Submittal – Finally the site has a number of user forms that can be submitted to allow users to upload software and become part of the development team of existing applications.

This slides shows a list of the applications that are currently available for download on the OSADP.

The first two applications are USDOT sponsored Los Angeles and Dallas Fort Worth Freight Advanced Traveler Information System or FRATIS applications. These two applications where used to optimize drayage movement at these two sites.

Cross-Town Improvement Project Drayage Optimizing 1.0 – sometimes also know as C-TIP is the back end optimization algorithm that is used at each of the FRATIS applications sites to optimize drayage operations based on work load and distanced traveled.

TCA – The TCA is program that is designed to produce series of transportation messages including BSM, PDM, Japanese ITS-Spot messages, and European CAM messages under a variety of different message strategies. The software uses trajectory data from flat files or can be run directly with VISSIM or PARAMICS simulation models.

Performance Measurement Applications 1.0 – The final application on the list processes regional trip based trajectory data and creates high level performance measure from that information.

I now want to take a minute and show you a sample of what you might find when you download an application from OSADP.

Here is what is found in the TCA package. As you can see there is documentation including a user guide, system requirements, release notes and licensing information. The application also includes the full Python source code and documents all required additional libraries to run the software. This application package also includes sample data files to allow users to quickly get started running the software.

Now that I have told you what you can find on the OSADP I want to walk you through what is required of you if you use these applications.

First all applications release through the OSADP are required to be license as open source to support the goals of the OSADP.

The default and preferred license for the OSADP is the Apache 2.0 Open Source License. Applications that are submitted to the OSADP without a license will be given this license.

The OSADP will consider other open source licenses other then the Apache license but these considerations will be evaluated on a case-by-case bases by the OSADP leadership group. Things that will be consider with other licenses include any restrictions the license may put on the end user and relevance and usefulness as a whole for the DMA program. Please don’t let this discourage you from submitting applications under other licenses though.

As with all applications, users of the OSADP applications must adhere to the terms and conditions that are included with the applications licenses.

Since Apache 2.0 is the preferred license I want to take a minute to explain a little about the license.

What you can do with the license:

-You can download the applications and use them on as many computers as you like for no charge or fee

-You can take the code and add it to proprietary software package that you created and license it under another license. Note however the original code must still stay under the Apache license

-You can make changes to the code and not have to resubmit the new code back to the OSADP. We hope you don’t do this as we would like everyone to benefit from any improvements you make but it is not a requirement.

What can’t you do with the license:

-You may not redistribute it with out giving the original developer credit for their work.

-Must include the license if you redistribute the software.

-Must document how you changed any of the original code in a new distribution.

-Must not use trademarks or logos of the FHWA to market or endorses you new application.

Here are some of the Applications you can expect on the OSADP in the near future.

Applications that are under review means we have already received some information on these applications and we are in the process of reviewing them to make sure they are ready to be released on the OSADP.

Some of the DMA bundles that are under review include RESCUME, IDTO, and INFLO. We are also looking at SPaT software, Connected Vehicle RSD develop kits and Pikalert which is software that checks and reports road weather information.

Other applications we expect to hear from soon include two DMA bundles ATIS and MMITSS and finally Mobile Devices application which is software for testing out mobile messages within the Connected Vehicle framework

So who can submit Applications?

Well everyone is welcome and encouraged to submit their applications to the OSADP.

It should be noted however that focus of the OSADP is for DMA applications and ITS Program sponsored projects, but don’t let that stop you from submitting applications you think may be helpful to the community as a whole.

If you are looking to submit your applications to the OSADP these are the things your application need to have. This list is also available on the OSADP website under the upload guide page.

Required for submission is:

-The complete source code for the application

-Documentation that is web ready. This means it needs to be 508 compliant.

-A basic README file with information on the application including description, version number and installation instructions

-Licensing information about the application

-And core documentation for the application or links to the core documentation

Optional items that are encouraged if available are:

- Sample data files to run the software

-Attribution documenting all people involved with the applications

Examples of any of these files can be downloaded directly from the OSADP or sent to you if requested.

Now we are going to walk you through a demo of the site. These are the things we are going to highlight during the demo.

Just say each bullet point