Department of Transportation

http://www.dot.gov/

Evidence Act Milestone 4 - June 30th 2020

Previous Milestone: The milestone selected is the most recently complete one. The Automated Metrics are a snapshot from the milestone date.

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://data.transportation.gov/data.json
Number of Redirects
HTTP Status 200
Content Type application/json; charset=utf-8
Valid JSON Valid
Detected Data.json Schema federal-v1.1
Datasets with Valid Metadata 99.8%(3950 of 3959)
Valid Schema Invalid
For more complete and readable validation results, see the full schema validator results
Schema Errors There are validation errors on 9 records

Errors on record 362:
bureauCode
  • The property bureauCode is required
programCode
  • The property programCode is required
keyword
  • The property keyword is required
contactPoint.hasEmail
  • Does not match the regex pattern ^mailto:[\w\_\~\!\$\&\'\(\)\*\+\,\;\=\:.-]+@[\w.-]+\.[\w.-]+?$
  • Does not match the regex pattern ^(\[\[REDACTED).*?(\]\])$
  • Failed to match at least one schema
description
  • Must be at least 1 characters long
Errors on record 519:
accrualPeriodicity
  • Does not have a value in the enumeration ["irregular"]
  • Does not match the regex pattern ^R\/P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • 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 2064:
accrualPeriodicity
  • Does not have a value in the enumeration ["irregular"]
  • Does not match the regex pattern ^R\/P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • 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 2258:
distribution
  • Array value found, but a null is required
  • Array value found, but a string is required
  • Failed to match at least one schema
Errors on record 2407:
distribution
  • Array value found, but a null is required
  • Array value found, but a string is required
  • Failed to match at least one schema
Errors on record 2648:
accrualPeriodicity
  • Does not have a value in the enumeration ["irregular"]
  • Does not match the regex pattern ^R\/P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • 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 3272:
accrualPeriodicity
  • Does not have a value in the enumeration ["irregular"]
  • Does not match the regex pattern ^R\/P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • 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 3769:
accrualPeriodicity
  • Does not have a value in the enumeration ["irregular"]
  • Does not match the regex pattern ^R\/P(?:\d+(?:\.\d+)?Y)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?W)?(?:\d+(?:\.\d+)?D)?(?:T(?:\d+(?:\.\d+)?H)?(?:\d+(?:\.\d+)?M)?(?:\d+(?:\.\d+)?S)?)?$
  • 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 3844:
distribution
  • Array value found, but a null is required
  • Array value found, but a string is required
  • Failed to match at least one schema
Datasets 3959
Number of Collections 186
Number of datasets not in a collection 865
Datasets with Distribution URLs 96.8% (3831 of 3959)
Datasets with Download URLs 96.8% (3831 of 3959)
Total Distribution URLs 4138 (but only 619 accessible)
Total Download URLs 4138
Total APIs 0
Public APIs 0
Restricted Public APIs 0
Non-public APIs 0
Public Datasets 2290
Restricted Public Datasets 1287
Non-public Datasets 382
Server Not Found 0.0% (0 of 4138)
Working links (HTTP 2xx)
Broken links (HTTP 4xx)
Error Links (HTTP 5xx)
Redirected Links (HTTP 3xx)
Correct format
PDF for raw data
HTML for raw data
Bureaus Represented 13
Programs Represented 31
License Specified 99.3% (3930 of 3959)
Datasets with Redactions 0.0% (0 of 3959)
Redactions without explanation (rights field) 0.0% (0 of 3959)
File Size 7.83MB
Last crawl Tuesday, 30-Jun-2020 07:12:48 EDT
Analyze archive copies Analyze archive from 2020-06-30
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
HTTP Status 200
Content Type text/html; charset=UTF-8
Last modified Tuesday, 30-Jun-2020 03:01:16 EDT
Last crawl Tuesday, 30-Jun-2020 03:01:17 EDT
/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
HTTP Status 200
Content Type application/json
Valid JSON Valid
Last modified Thursday, 12-Dec-2013 17:06:46 EST
Last crawl Tuesday, 30-Jun-2020 03:01:18 EDT
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.