Department of Transportation

http://www.dot.gov/

Milestone 10 - February 29th 2016

OMB Review Complete: OMB has completed the agency review for this milestone. Agencies should contact their OMB desk officer if anything looks incorrect.

Leading Indicators

These indicators are reviewed by the Office of Management and Budget

Review Status complete
Reviewer Justin Grimes
Last Updated April 21, 2016, 10:54 am EDT by Justin Grimes

Assessment Summary

Department of Transportation is commended for its excellent list of priority datasets for external and internal use. Department of Transportation is commended for its in-person outreach to its data users through events and social media. The Department still lacks a public, two-way communication mechanism for data at the Department level. Fails to have 100% valid data.json. Agency also fails to provides datasets in human-readable form on agency /data page. Fails to provide an updated public EDI as a dataset in your data.json file (i.e. wrong file/link). Fails to document any outstanding APIs i.e. “format”: “API”; For instructions on how to properly document APIs see OMB guidance https://project-open-data.cio.gov/v1.1/api/ Fails to document any outstanding Licensing information

Inventory Composition

Public Dataset Status

Dataset Link Quality

Status Indicator Automated Metrics
Overall Progress this Milestone
Inventory Updated this Quarter
3703 Number of Datasets
Number of APIs
14 Bureaus represented
107.7% Percentage of bureaus represented
29 Programs represented
47.5% Percentage of programs represented
1967 Number of public datasets
1285 Number of restricted public datasets
451 Number of non-public datasets
Percentage growth in records since last quarter
To a very great extent (>75%) To what extent is your agency’s Enterprise Data Inventory (EDI) complete?
See below What steps have you taken to ensure your Enterprise Data Inventory is complete
The Department of Transportation followed our structured, published process for completing the Enterprise Data Inventory. We released that process at https://www.transportation.gov/mission/dotopendatainventoryapproach.
Agency provides a public Enterprise Data Inventory on Data.gov
Agency provided updated Enterprise Data Inventory to OMB
97.4% License specified Crawl details
Number of datasets with redactions
Percent of datasets with redactions
Status Indicator Automated Metrics
Overall Progress this Milestone
3703 Number of Datasets Crawl details
103 Number of Collections Crawl details
745 Number of datasets not contained in a collection Crawl details
3102 Number of Public Datasets with File Downloads Crawl details
Number of APIs Crawl details
Number of public APIs Crawl details
Number of restricted public APIs Crawl details
Number of non-public APIs Crawl details
3303 Total number of access and download links Crawl details
Quality Check: Links are sufficiently working Crawl details
2490 Quality Check: Accessible links Crawl details
595 Quality Check: Redirected links Crawl details
42 Quality Check: Error links Crawl details
76 Quality Check: Broken links Crawl details
71.4% Quality Check: Percentage of download links in correct format as specified in metadata Crawl details
13.7% Quality Check: Percentage of download links in HTML Crawl details
0.2% Quality Check: Percentage of download links in PDF Crawl details
Percentage growth in records since last quarter
91.4% Valid Metadata Crawl details
/data exists Crawl details
Provides datasets in human-readable form on /data
/data.json Crawl details
Harvested by data.gov
1967 Number of public datasets Crawl details
1285 Number of restricted public datasets Crawl details
451 Number of non-public datasets Crawl details
Percent growth of public datasets
Percent growth of restricted public datasets
Percent growth of non-public datasets
Percent datasets licensed as U.S. Public Domain
Percent datasets licensed as Creative Commons Zero
Percent datasets with other licenses
Percent datasets with no license
Status Indicator Automated Metrics
Overall Progress this Milestone
Description of feedback mechanism delivered Crawl details
Data release is prioritized through public engagement
Provided narrative evidence of data improvements based on public feedback this quarter
Feedback loop is closed, 2 way communication
Link to or description of Feedback Mechanism
Provides valid contact point information for all datasets
Status Indicator Automated Metrics
Overall Progress this Milestone
Data Publication Process Delivered Crawl details
Information that should not to be made public is documented with agency's OGC
See below Describe the agency's data publication process
The DOT uses our Departmental Data Release Policy (DOT Order 1351.34) as a guide for disseminating data sets. This policy addresses protections for security, privacy, confidentiality, and other traditional concerns that may warrant redaction of some information in our datasets. Identification of a data set does not mean that DOT will release the entire data set without appropriate redactions. We regularly update the DOT data inventory to reflect the Department’s data inventory activities and release management capabilities. We continue to focus on Open Government and recently hosted a Datapalooza at the Department. The Departmental Data Release Policy sets the default state of DOT data to open by stating, DOT policy is to make data available at the most detailed level possible, subject only to the limits imposed by data quality and the need to protect national/homeland security, individual privacy, and confidentiality. Further, the policy states, DOT policy is to disseminate data as soon as possible following collection, subject only to the limits imposed by resources, technology, authority, regulation and data quality while protecting security, privacy, and confidentiality. DOT has existing processes for performing pre-dissemination reviews and public disclosure risk assessments. Regardless of the releasability of a dataset, that dataset much be registered in the DOT data inventory.

Best Practice: Department of Transportation has been highlighted for demonstrating a best practice on the Human Capital indicator

Status Indicator Automated Metrics
Overall Progress this Milestone
See below Open Data Primary Point of Contact
daniel.morgan@dot.gov
POCs identified for required responsibilities
See below Chief Data Officer (if applicable)
daniel.morgan@dot.gov
Status Indicator Automated Metrics
Overall Progress this Milestone
Provided narrative evidence of open data impacts for this quarter
Digital Analytics Program on /data
2398 Views on data.gov for this quarter
-7.2% Percentage growth in views on data.gov for this quarter
Views on agency /data page for this quarter

Automated Metrics

These metrics are generated by an automated analysis that runs every 24 hours until the end of the quarter at which point they become a historical snapshot

data.json
Expected Data.json URL http://www.dot.gov/data.json (From USA.gov Directory)
Resolved Data.json URL https://www.transportation.gov/sites/dot.gov/files/docs/data.json
Number of Redirects 3 redirects
HTTP Status 200
Content Type application/json
Valid JSON Valid
Datasets with Valid Metadata 91.4%(3386 of 3703)
Valid Schema Invalid
For more complete and readable validation results, see the full schema validator results
Schema Errors There are validation errors on 317 records

Only showing errors from the first 10 records:

Errors on record 0:
temporal
  • does not match the regex pattern ^([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • does not match the regex pattern ^(R\d*\/)?([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\4([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\18[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • does not match the regex pattern ^(R\d*\/)?P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?\/([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\4([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\18[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 1:
license
  • Invalid URL format
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 2:
license
  • Invalid URL format
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 3:
license
  • Invalid URL format
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 4:
license
  • Invalid URL format
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 5:
license
  • Invalid URL format
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 6:
license
  • Invalid URL format
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 7:
license
  • Invalid URL format
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 8:
temporal
  • does not match the regex pattern ^([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • does not match the regex pattern ^(R\d*\/)?([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\4([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\18[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • does not match the regex pattern ^(R\d*\/)?P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?\/([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\4([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\18[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Errors on record 9:
temporal
  • does not match the regex pattern ^([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\3([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\17[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • does not match the regex pattern ^(R\d*\/)?([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\4([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\18[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?(\/)P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • does not match the regex pattern ^(R\d*\/)?P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?\/([\+-]?\d{4}(?!\d{2}\b))((-?)((0[1-9]|1[0-2])(\4([12]\d|0[1-9]|3[01]))?|W([0-4]\d|5[0-2])(-?[1-7])?|(00[1-9]|0[1-9]\d|[12]\d{2}|3([0-5]\d|6[1-6])))([T\s]((([01]\d|2[0-3])((:?)[0-5]\d)?|24\:?00)([\.,]\d+(?!:))?)?(\18[0-5]\d([\.,]\d+)?)?([zZ]|([\+-])([01]\d|2[0-3]):?([0-5]\d)?)?)?)?$
  • string value found, but a null is required
  • does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • failed to match at least one schema
Datasets 3703
Number of Collections 103
Number of datasets not in a collection 745
Datasets with Distribution URLs 83.8% (3102 of 3703)
Datasets with Download URLs 82.3% (3048 of 3703)
Total Distribution URLs 3303
Total Download URLs 3048
Total APIs 0
Public Datasets 1967
Restricted Public Datasets 1285
Non-public Datasets 451
Bureaus Represented 14
Programs Represented 29
License Specified 97.4% (3607 of 3703)
Datasets with Redactions 0.0% (0 of 3703)
Redactions without explanation (rights field) 0.0% (0 of 3703)
File Size 4.77MB
Last modified Monday, 29-Feb-2016 17:10:24 EST
Last crawl Monday, 29-Feb-2016 23:13:54 EST
Analyze archive copies Analyze archive from 2016-02-29
Nearby Daily Crawls
/data page
Expected /data URL http://www.dot.gov/data (From USA.gov Directory)
Resolved /data URL https://www.transportation.gov/data
Redirects 2 redirects
HTTP Status 200
Content Type text/html; charset=utf-8
Last modified Monday, 29-Feb-2016 18:36:25 EST
Last crawl Monday, 29-Feb-2016 23:12:51 EST
/digitalstrategy.json
Expected /digitalstrategy.json URL http://www.dot.gov/digitalstrategy.json (From USA.gov Directory)
Resolved /digitalstrategy.json URL https://www.transportation.gov/sites/dot.dev/files/docs/digitalstrategy.json
Redirects 3 redirects
HTTP Status 200
Content Type application/json
Valid JSON Valid
Last modified Thursday, 12-Dec-2013 17:06:46 EST
Last crawl Monday, 29-Feb-2016 23:12:52 EST
Digital Strategy

Date specified: Wednesday, 27-Nov-2013 12:38:47 EST

Date of digitalstrategy.json file: Thursday, 12-Dec-2013 17:06:46 EST

1.2.4 Develop Data Inventory Schedule - Summary

Summarize the Inventory Schedule


The Department of Transportation (DOT) approach to ensuring all data assets from each bureau and program in the agency will be identified and accounted for in its Enterprise Data Inventory is focused on linking various information management programs together. Specifically, the DOT Enterprise Data Inventory is considered complete when each of its Operating Administrations (OAs) has accounted for all datasets that are:
•	collected under an OMB-approved Information Collection Request
•	contained in Records Disposition Schedules (RDS) and Electronic Information Systems (EIS) list
•	covered by a Privacy Act System of Records Notice (SORN)
•	associated with an information technology (IT) investment reported on the Exhibit 53
Each OA will register all datasets in the DOT metadata registry. 

The DOT Enterprise Data Inventory schedule takes a methodical approach to completing the task. Each DOT Operating Administration (OA) will review data from each of its information management programs to identify a complete list of information collections, record schedules, and IT investments that contain data. Once the list is complete, OAs will proceed with inventorying the datasets contained in those information systems. The milestones are:

1.2.5 Develop Data Inventory Schedule - Milestones

TitleDevelop OA implementation plan
DescriptionEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
Milestone DateJanuary 17, 2014
Description of how this milestone expands the InventoryEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
Description of how this milestone enriches the InventoryEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
Description of how this milestone opens the InventoryEach DOT OA will formulate an implementation plan to conduct its data inventory activities, identifying team members and gathering data from its information management programs.
TitleInventory public datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Milestone DateFebruary 28, 2014
Description of how this milestone expands the InventoryEach DOT OA will analyze the data from its information management programs to identify those that contain data and will gather any information regarding the releasability of those datasets.
Description of how this milestone enriches the InventoryEach DOT OA will analyze the data from its information management programs to identify those that contain data and will gather any information regarding the releasability of those datasets.
Description of how this milestone opens the InventoryEach DOT OA will analyze the data from its information management programs to identify those that contain data and will gather any information regarding the releasability of those datasets.
TitleInventory public datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Milestone DateApril 28, 2014
Description of how this milestone expands the InventoryUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Description of how this milestone enriches the InventoryUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
Description of how this milestone opens the InventoryUsing the data gathered at Milestone 2, each DOT will register its publicly available datasets in the DOT metadata registry.
TitleInventory mission-oriented datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable..
Milestone DateJune 30, 2014
Description of how this milestone expands the InventoryUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone enriches the InventoryUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone opens the InventoryUsing the data gathered at Milestone 2, each DOT will register its mission-oriented datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
TitleInventory administrative datasets
DescriptionUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Milestone DateSeptember 29, 2013
Description of how this milestone expands the InventoryUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone enriches the InventoryUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.
Description of how this milestone opens the InventoryUsing the data gathered at Milestone 2, each DOT will register its administrative datasets in the DOT metadata registry. This will include datasets that may have restrictions on access or that may not be releasable.

1.2.6 Develop Customer Feedback Process

Describe the agency's process to engage with customers


Engagement is a core value at DOT and is integral in our decision-making process. The Department has hosted 170 roundtable sessions throughout the country over the last year. In September 2011, DOT hosted a Public Meeting to discuss how to connect public and private organizations through a Digital Transportation Exchange designed to find innovative ways to better serve the public. In addition, with the launch of Safety.Data.gov, we played a leading role in a White House session to identify potential apps and data needs relating to Safety. The event included a Data Jam to select apps for development and to form teams to identify necessary steps. Finally, in July 2010, President Obama signed into law P.L. 112-141, Moving Ahead for Progress in the 21st Century Act (MAP-21). This legislation will transform the policy and programmatic framework for investments to guide system growth and development.  In addition to these in-person engagement methods, DOT has established an email address, opendata@dot.gov, to receive feedback from data users. We are also establishing a listserv for developers and data users to announcements about open data at DOT.

1.2.7 Develop Data Publication Process

Describe the agency's data publication process


The DOT uses our Departmental Data Release Policy (DOT Order 1351.34) as a guide for disseminating data sets. This policy addresses protections for security, privacy, confidentiality, and other traditional concerns that may warrant redaction of some information in our datasets. Identification of a data set does not mean that DOT will release the entire data set without appropriate redactions. We regularly update the DOT data inventory to reflect the Department’s data inventory activities and release management capabilities. We continue to focus on Open Government and recently hosted a Datapalooza at the Department.

The Departmental Data Release Policy sets the default state of DOT data to open by stating, DOT policy is to make data available at the most detailed level possible, subject only to the limits imposed by data quality and the need to protect national/homeland security, individual privacy, and confidentiality. Further, the policy states, DOT policy is to disseminate data as soon as possible following collection, subject only to the limits imposed by resources, technology, authority, regulation and data quality while protecting security, privacy, and confidentiality. DOT has existing processes for performing pre-dissemination reviews and public disclosure risk assessments. Regardless of the releasability of a dataset, that dataset much be registered in the DOT data inventory.