The National Academies Press

Currently Skimming:

Pages 13-47

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.

From page 13... ... 13 Twenty-eight guidelines were developed based on identified barriers to effective freight data sharing and measures that have been taken to overcome the barriers. Table 3.1 shows the 28 guidelines organized into six categories. Read the entire page →
From page 14... ... 14 Freight Data Sharing Guidebook Table 3.1. Summary of guidelines for freight data sharing. Read the entire page →
From page 15... ... Freight Data Sharing Guidelines 15 Table 3.2. Public and commercial data sources. Read the entire page →
From page 16... ... 16 Freight Data Sharing Guidebook permission to use some datasets and the ease with which other data, without restrictions, could be used. Guideline 2 – Use Nonrestricted or Open Source Data if Available Most of the freight data collected by government agencies or trade and industry associations can be accessed without restrictions. Read the entire page →
From page 17... ... Freight Data Sharing Guidelines 17 Example 2-2. Impacts of Columbia-Snake River Extended Lock Outage The WSU's Freight Policy Transportation Institute completed a study that assessed the transportation and environmental impacts of extended lock outages on the Columbia-Snake River System. Read the entire page →
From page 18... ... 18 Freight Data Sharing Guidebook of eastern states) Read the entire page →
From page 19... ... Freight Data Sharing Guidelines 19 parties to remove sensitive information from data to be exchanged or to restrict the uses that can be made of data can be important in gaining acceptance of data sharing. Table 3.4 below shows seven guidelines and some case study project examples that exhibited those guidelines. Read the entire page →
From page 20... ... 20 Freight Data Sharing Guidebook concerns including long term stable contracting relationships and also standard nondisclosure agreements or NDAs. Guideline 4 – If Unrestricted Data is not Enough, be Aware that Privacy Concerns Must be Addressed Since freight is usually carried by the private sector, public sector program use of private freight data depends, to some degree, on the public sector's ability to collect private sector data. Read the entire page →
From page 21... ... Freight Data Sharing Guidelines 21 Example 4-1. Cross-Town Improvement Project (C-TIP) Read the entire page →
From page 22... ... 22 Freight Data Sharing Guidebook prevent any such disclosure. The NDA may require that the organizations receiving the data limit access of the data only to employees having a need to know in connection with the data. Read the entire page →
From page 23... ... Freight Data Sharing Guidelines 23 Guideline 6 – A Stable Contracting Relationship with Data Providers Can be Very Helpful in Successful Data Sharing The FPMs GPS truck data project and the Canada Borders project both had longer term contractual arrangements that supported data sharing. See Example 6-1. Read the entire page →
From page 24... ... 24 Freight Data Sharing Guidebook contract with U.S. Read the entire page →
From page 25... ... Freight Data Sharing Guidelines 25 Example 8-1. Otay Mesa Border Delay Project The project began in October 2007 to assess GPS and license plate recognition technology for the measurement of travel times for trucks through the Otay Mesa international border crossing from Mexico into the United States. Read the entire page →
From page 26... ... 26 Freight Data Sharing Guidebook Guideline 9 – Public Agencies Desiring to Obtain Data from Private Companies May Need to Research FOIA Laws For governmental agencies, privacy protection may be complicated by open information laws that allow individuals to request information from governmental agencies. For example, the 1966 FOIA is a federal law that gives individuals access to any U.S. Read the entire page →
From page 27... ... Freight Data Sharing Guidelines 27 3.3 Guidelines for Scrubbing or Restricting Access to Freight Data In a 2009-10 FHWA project entitled Freight Data Sharing Compendium, the primary barrier to freight data sharing identified was the possible disclosure of individual shipment or company data. The primary mitigation for this disclosure problem is aggregating or scrubbing data to remove individuality. Read the entire page →
From page 28... ... 28 Freight Data Sharing Guidebook Guideline 11 – Consider the Use of Software and Database Tools to Protect and Access Freight Data by Removing Private or Competitive Information A common approach to overcoming data privacy concerns is to scrub the data of all company, shipment, and/or operator or driver information prior to delivering it to a public agency. This has been the approach for several truck GPS tracking projects including the ATRI and Washington State performance measures projects, the Southern California Truck modeling project, and the Canada Gateways project. Read the entire page →
From page 29... ... Freight Data Sharing Guidelines 29 set and is internally consistent to allow for functions such as geographic tracking but reduces the ability to identify specific businesses. This approach was used by the vendors that supplied GPS data to the Washington State Freight Performance Measures project. Read the entire page →
From page 30... ... 30 Freight Data Sharing Guidebook and its partners to collect and disseminate pertinent inland waterway operational data to lock operators and barge captains. Additional data streams may become available in future iterations of the system, but the initial deployment is already providing information valuable to lock operators. Read the entire page →
From page 31... ... Freight Data Sharing Guidelines 31 Guideline 13 – Place a High Priority on Coordination and Devote the Needed Resources to Extensive Coordination with Public and Private Stakeholders The more parties there are in a project, the more difficult it is to work through all of the coordination issues. This is particularly true of projects that involve international borders with multiple federal, state/provincial, and local governments as well as private firms in both Guideline Project Examples 13 Place a high priority on coordination and devote the needed resources to extensive coordination with public and private stakeholders. Read the entire page →
From page 32... ... 32 Freight Data Sharing Guidebook countries. Thus, stakeholder coordination was an important element in a number of successful freight data sharing efforts including several border crossing travel time studies and the CREATE rail improvement public-private partnership in Chicago. Read the entire page →
From page 33... ... Freight Data Sharing Guidelines 33 provide access to appropriate owners of freight data. For example, in the Minnesota Performance Measures study, the researchers obtained data dealing with rail freight from the Association of American Railroads, data on intermodal freight from the IANA, and waterway and port data on intermodal freight from both the PIERS and AAPA. Read the entire page →
From page 34... ... 34 Freight Data Sharing Guidebook for the electronic seals project from the Whatcom Council of Governments' (a Washington State MPO) through their International Mobility and Trade Committee (IMTC) Read the entire page →
From page 35... ... Freight Data Sharing Guidelines 35 project helps to assure its success. There are seven guidelines that deal with benefits of sharing, shown in Table 3.7, along with examples from case studies. Read the entire page →
From page 36... ... 36 Freight Data Sharing Guidebook Example 18-1. C-TIP The C-TIP Intermodal Transfer Project is a technology application, supported by U.S. Read the entire page →
From page 37... ... Freight Data Sharing Guidelines 37 Example 19-1. Washington State FPMs The state-funded Washington State GPS FPMs Project used data from commercial GPS devices in trucks to develop a statewide freight performance measure program. Read the entire page →
From page 38... ... Example 20-1. EPA SmartWay The U.S. Read the entire page →
From page 39... ... Freight Data Sharing Guidelines 39 Example 21-1. Detroit Windsor Bridge The Detroit-Windsor New International Trade Crossing, formerly known as the Detroit River International Crossing (DRIC) Read the entire page →
From page 40... ... 40 Freight Data Sharing Guidebook Guideline 22 – Add Value to the Data and Make it Available to All Stakeholders If partners see value in the data products offered by agencies and are offered access to the information resources that their data helps to generate, they may be more willing to provide data. This is especially true for public-public data sharing, i.e., the sharing of information between government entities. Read the entire page →
From page 41... ... Freight Data Sharing Guidelines 41 Example 22-2. Border Crossing Information System Project The purpose of the Border Crossing Information System (BCIS) Read the entire page →
From page 42... ... 42 Freight Data Sharing Guidebook Guideline 24 – Explore New Market Opportunities with Potential Data Providers Historically, agencies have had to make do with inadequate public data or engage in expensive data collection efforts to accomplish freight planning goals, even though it is widely known that superior data exists but is controlled by private firms. In some cases, however, third party data providers may find that there is an untapped market for anonymous freight movement data that public sector agencies can use for transportation planning and modeling purposes. Read the entire page →
From page 43... ... Freight Data Sharing Guidelines 43 3.6 Guidelines for Funding for Data Sharing and Projects Most freight data projects originate because of a public and sometimes public-private interest in furthering a transportation objective. Federal, state, or regional/local planning or transportation agencies conduct projects that look at the performance of the transportation system, address the impacts of congestion, and analyze the costs and benefits of proposed infrastructure improvements. Read the entire page →
From page 44... ... 44 Freight Data Sharing Guidebook Example 25-2 explains in more detail some of the contracts involved with several of the border crossing projects. Guideline 26 – Be Sure to Include Funding to Cover Costs of Data Sharing and Needed Agreements to Protect Data If it costs data providers to share data and they do not otherwise perceive benefits, reimbursement sometimes helps. Read the entire page →
From page 45... ... Freight Data Sharing Guidelines 45 stipend to trucking companies to help with their costs of providing data. Example 26-2 below discusses the CREATE program in Chicago that used TIGER funds to support data sharing, coordination, and infrastructure improvements. Read the entire page →
From page 46... ... 46 Freight Data Sharing Guidebook The Turn Time Study at the Port of Long Beach, described in Example 27-2, was funded by several different private groups and the port operators; it used data collection equipment and data collected in an earlier project that received federal funding. Projects to improve air quality in Southern California almost always include co-funding by private sector partners and/or other government agencies. Read the entire page →
From page 47... ... Freight Data Sharing Guidelines 47 Guideline 28 – Consider Gathering Data from Volunteer Stakeholder Groups or Roundtables In addition to open source data usually available without cost, some projects obtain data through the network of stakeholder groups involved in the projects. Such data lowers cost and reduces the need to set up data sharing agreements. Read the entire page →

From page 13...

... 13 Twenty-eight guidelines were developed based on identified barriers to effective freight data sharing and measures that have been taken to overcome the barriers. Table 3.1 shows the 28 guidelines organized into six categories.