Department of Transportation

http://www.dot.gov/

Milestone 14 - February 28th 2017

OMB Review In Progress: OMB is currently reviewing the agency for this milestone. This review status indicator will change once the review is complete.

Leading Indicators

These indicators are reviewed by the Office of Management and Budget

Review Status in-progress
Reviewer Bryant Renaud
Last Updated April 18, 2017, 1:28 pm EDT by Bryant Renaud

Assessment Summary

EDI is Yellow: DOT does not document license for all datasets. DOT does not document any APIs.

PDL is Yellow: Schema validation throwing errors on implementation of redaction.

Other: Can DOT either 1) provide human-readable list of datasets on /data page or 2) more prominently link to such a list on data.gov (i.e. add hyperlink to first paragraph's mention of 'data inventory page' on /data.

Large proportion of links in HTML.

Large proportion of links are redirects.

Inventory Composition

Public Dataset Status

Dataset Link Quality

Status Indicator Automated Metrics
Overall Progress this Milestone
Inventory Updated this Quarter
4150 Number of Datasets
Number of APIs
14 Bureaus represented
107.7% Percentage of bureaus represented
30 Programs represented
49.2% Percentage of programs represented
2450 Number of public datasets
1306 Number of restricted public datasets
394 Number of non-public datasets
0.0% 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/dot-open-data-inventory-approach. We continue to review our Web sites to identify data sets that are public (especially at the FAA) and this quarter's update reflects a number of moves from non-public to public status as a result of this concentrated effort. This quarter demonstrates additional progress completing the inventory and reflects a number of updates to refactor entries from the FAA and include additional research data sets from the Intelligent Transportation Systems program.
Agency provides a public Enterprise Data Inventory on Data.gov
Agency provided updated Enterprise Data Inventory to OMB
99.2% License specified Crawl details
Number of datasets with redactions
Percent of datasets with redactions
Status Indicator Automated Metrics
Overall Progress this Milestone
4150 Number of Datasets Crawl details
218 Number of Collections Crawl details
741 Number of datasets not contained in a collection Crawl details
3750 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
3938 Total number of access and download links Crawl details
Quality Check: Links are sufficiently working Crawl details
229 Quality Check: Accessible links Crawl details
3091 Quality Check: Redirected links Crawl details
56 Quality Check: Error links Crawl details
332 Quality Check: Broken links Crawl details
57.2% Quality Check: Percentage of download links in correct format as specified in metadata Crawl details
71.6% Quality Check: Percentage of download links in HTML Crawl details
1.3% Quality Check: Percentage of download links in PDF Crawl details
0.0% Percentage growth in records since last quarter
98.3% Valid Metadata Crawl details
/data exists Crawl details
Provides datasets in human-readable form on /data
/data.json Crawl details
Harvested by data.gov
2450 Number of public datasets Crawl details
1306 Number of restricted public datasets Crawl details
394 Number of non-public datasets Crawl details
0.0% Percent growth of public datasets
0.0% Percent growth of restricted public datasets
0.0% 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
See below Link to or description of Feedback Mechanism
The Department offers a wide range of public feedback mechanisms - both online and offline - to support our data users and respond to their requests for support. The Chief Data Officer operates opendata@dot.gov and the National Transportation Library offers support for data and other questions through answers@dot.gov and the Ask-A-Librarian system at https://ntl.custhelp.com/app/ask/. The Library also provides answers to frequently-asked questions at https://ntl.custhelp.com/app/answers/list/. The Department also responds to queries and comments received through the data.gov contact tool (http://www.data.gov/contact). In addition to these general support mechanisms, each of the Department's programs offers their own unique contact tools on their Web sites and each data set we list on data.gov has contact information for a DOT employee responsible for stewarding that data. As just one example, the Federal Aviation Administration has developed an extensive user engagement and outreach effort for its real-time flight data feeds (http://www.faa.gov/nextgen/programs/swim/users_forum/). In addition to these contact mechanisms, the Department hosts a number of forums to hear from data users. We have held three Transportation Datapaloozas (https://www.fhwa.dot.gov/2015datapalooza/) as well as three Safety Datapaloozas (https://www.data.gov/event/safety-datapalooza/). In conjunction with the Transportation Research Board Annual Meeting, which brings over 10,000 transportation professionals from around the world together, we regularly participate in data user forums. During the 2016 Annual Meeting, we participated in the 12th Annual Travel Data User Forum as well as a Freight Data User Forum. In addition, we are actively involved with our stakeholders and users through their own conferences, which are too numerous to list here. The Department has also been involved in the planning of hackathons, including the recent Celebrating Cities hackathon (http://celebratingcities.github.io/) and Bayes Hack 2016 (http://bayeshack.org/). The Department is actively considering a problem statement for the National Day of Civic Hacking, as well. We view hackathons as an opportunity to not only increase attention to our data, but also to learn from new users of our data about their challenges and recommendations for how we can improve our data products.
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\u2019s data inventory activities and release management capabilities. We continue to focus on Open Government and recently hosted a Datapalooza at the Department.\r\n\r\nThe 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.
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
Chief Data Officer (if applicable)
Status Indicator Automated Metrics
Overall Progress this Milestone
Provided narrative evidence of open data impacts for this quarter
Digital Analytics Program on /data
Views on data.gov for this quarter
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 98.3%(4081 of 4150)
Valid Schema Invalid
For more complete and readable validation results, see the full schema validator results
Schema Errors There are validation errors on 69 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:
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 9:
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
Datasets 4150
Number of Collections 218
Number of datasets not in a collection 741
Datasets with Distribution URLs 90.4% (3750 of 4150)
Datasets with Download URLs 90.4% (3750 of 4150)
Total Distribution URLs 3938
Total Download URLs 3938
Total APIs 0
Public APIs 0
Restricted Public APIs 0
Non-public APIs 0
Public Datasets 2450
Restricted Public Datasets 1306
Non-public Datasets 394
Bureaus Represented 14
Programs Represented 30
License Specified 99.2% (4115 of 4150)
Datasets with Redactions 0.0% (0 of 4150)
Redactions without explanation (rights field) 0.0% (0 of 4150)
File Size 4.77MB
Last modified Tuesday, 28-Feb-2017 09:30:16 EST
Last crawl Tuesday, 28-Feb-2017 23:00:32 EST
Analyze archive copies Analyze archive from 2017-02-28
Nearby Daily Crawls