Environmental Protection Agency


Milestone 16 - August 31st 2017

OMB Review Has Not Begun: OMB has not begun reviewing the agency for this milestone. The review will begin after the milestone date.

Leading Indicators

These indicators are reviewed by the Office of Management and Budget

Review Status
Last Updated January 30, 2018, 3:51 pm EST by Rebecca Williams

Assessment Summary

Autofill not complete. Final review pending.

Inventory Composition

Public Dataset Status

Status Indicator Automated Metrics
Overall Progress this Milestone
Inventory Updated this Quarter
2610 Number of Datasets
Number of APIs
1 Bureaus represented
Percentage of bureaus represented
19 Programs represented
Percentage of programs represented
2549 Number of public datasets
4 Number of restricted public datasets
57 Number of non-public datasets
Percentage growth in records since last quarter
To what extent is your agency’s Enterprise Data Inventory (EDI) complete?
What steps have you taken to ensure your Enterprise Data Inventory is complete
Agency provides a public Enterprise Data Inventory on Data.gov
Agency provided updated Enterprise Data Inventory to OMB
License specified Crawl details
Number of datasets with redactions
Percent of datasets with redactions
Status Indicator Automated Metrics
Overall Progress this Milestone
2610 Number of Datasets Crawl details
22 Number of Collections Crawl details
2400 Number of datasets not contained in a collection Crawl details
Number of Public Datasets with File Downloads Crawl details
1761 Number of APIs Crawl details
1666 Number of public APIs Crawl details
Number of restricted public APIs Crawl details
50 Number of non-public APIs Crawl details
Total number of access and download links Crawl details
Quality Check: Links are sufficiently working Crawl details
Quality Check: Accessible links Crawl details
Quality Check: Redirected links Crawl details
Quality Check: Error links Crawl details
Quality Check: Broken links Crawl details
Quality Check: Percentage of download links in correct format as specified in metadata Crawl details
Quality Check: Percentage of download links in HTML Crawl details
Quality Check: Percentage of download links in PDF Crawl details
Percentage growth in records since last quarter
Valid Metadata Crawl details
/data exists Crawl details
Provides datasets in human-readable form on /data
/data.json Crawl details
Harvested by data.gov
2549 Number of public datasets Crawl details
4 Number of restricted public datasets Crawl details
57 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
Describe the agency's data publication process
Status Indicator Automated Metrics
Overall Progress this Milestone
Open Data Primary Point of Contact
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

Expected Data.json URL http://www.epa.gov/data.json (From USA.gov Directory)
Resolved Data.json URL https://edg.epa.gov/data.json
Number of Redirects 3 redirects
HTTP Status 200
Content Type application/json
Valid JSON Invalid Check a JSON Validator
Datasets with Valid Metadata
Valid Schema Invalid
File Size 7.74MB
Last modified Thursday, 24-Aug-2017 14:30:47 EDT
Last crawl Thursday, 31-Aug-2017 01:25:27 EDT
Analyze archive copies Analyze archive from 2017-08-31
Nearby Daily Crawls
/data page
Expected /data URL http://www.epa.gov/data (From USA.gov Directory)
Resolved /data URL https://developer.epa.gov/category/data/
Redirects 4 redirects
HTTP Status 200
Content Type text/html; charset=UTF-8
Last crawl Thursday, 31-Aug-2017 01:25:06 EDT
Expected /digitalstrategy.json URL http://www.epa.gov/digitalstrategy.json (From USA.gov Directory)
Resolved /digitalstrategy.json URL https://www.epa.gov/sites/production/files/2015-05/digitalstrategy.json
Redirects 2 redirects
HTTP Status 200
Content Type text/plain
Valid JSON Valid
Last modified Monday, 29-Feb-2016 17:17:07 EST
Last crawl Thursday, 31-Aug-2017 01:25:07 EDT
Digital Strategy

Date specified: Friday, 31-May-2019 09:16:54 EDT

Date of digitalstrategy.json file: Monday, 29-Feb-2016 17:17:07 EST

1.2.4 Develop Data Inventory Schedule - Summary

Summarize the Inventory Schedule

In 2005 the EPA developed a metadata catalog for Agency datasets known as the Environmental Dataset Gateway (EDG). In response to Project Open Data requirements the EPA CIO issued an Agency-wide data call in Fall of 2013 asking all EPA organizations to register their datasets in EDG. Since that time the Agency has been committed to increasing the percentage of EPA data cataloged within the EDG. The Office of Environmental Information works with the Agency's Information Management Officers on an ongoing basis to encourage them to ensure that data within their program offices are registered in the EDG and has increased its network of stakeholders to ensure that any datasets not identified during the 2013 data call are registered in EDG.

1.2.5 Develop Data Inventory Schedule - Milestones

TitleProvide reports to programs to identify metadata holes.
DescriptionEPA uses its registry of IT Systems, READ, to identify datasets that may not be cataloged in the EDG. The EDG team works with the data stewardship network to identify and catalog the missing datasets.
Milestone DateOngoing
Description of how this milestone expands the InventoryThis milestone allows EPA to identify and catalog new datasets that were not identified in the original 2013 data call within the Agency's Environmental Dataset Gateway, the metadata catalog which is used to create the Enterprise Data Inventory.
Description of how this milestone enriches the InventoryThis milestone brings new and important datasets into EPA's Enterprise Data Inventory.
Description of how this milestone opens the InventoryThis milestones provides additional datasets that are publicly available through both the EDG and data.gov.

1.2.6 Develop Customer Feedback Process

Describe the agency's process to engage with customers

EPA interacts with the public on its data in numerous ways including public meetings/forums, feedback buttons on websites, webinars, mailboxes, FOIA Online and help desks. Recently the Agency launched an online public data forum to communicate with the public about its data in a fully transparent manner: http://developer.epa.gov/forums/forum/dataset-qa/. This forum enables two-way, transparent feedback between the Agency and the public. It can be accessed through three different webpages: the Environmental Dataset Gateway (EDG) webpage, the Developer Central webpage, and EPA's Digital Strategy webpage.  The forum shows both the public user's question and the Agency's answer and categorizes questions to increase discoverability about specific topics. Development work is underway to embed the forum into the Agency's metadata stylesheet. This would allow people to ask questions about a specific dataset directly from a metadata record and have that question routed to the metadata owner for response.
 In addition to the Forum, EPA has developed an error correction tool which allows the public to report errors that they find relating to data, especially in relation to the geographic locations of data points. The errors are routed through a system that returns feedback to the person who has reported the error.

1.2.7 Develop Data Publication Process

Describe the agency's data publication process

EPA has a number of policies and procedures concerning the publication of Agency data.  The Enterprise Information Management Policy requires all EPA Organization officials, employees, and individuals or non-EPA organizations, if applicable, to ensure information is cataloged and or labeled with metadata.  This includes geographic references, as appropriate, in EPA and Federal-wide registries, repositories or other information systems.  The EPA GeoPlatform Publishing Workflow Standard Operating Procedure and the EPA Environmental Dataset Gateway (EDG) Governance Structure and Standard Operating Procedure outline the details of EPA data publishing.
 EPA provides a range of tools and registry content (e.g. Reusable Component Services, Environmental Dataset Gateway, and Data Element Registry) through its System of Registries located at: www.epa.gov/sor. EPA is continuing efforts to document APIs through the development of an Agency-wide API Strategy.  The proposed strategy is based on 18F's API standards.  The proposal encourages the use of api.data.gov's API management platform. In addition, APIs produced by the EPA should be described using one of the common API definition formats (such as Swagger, API Blueprint and RAML).  The strategy is being finalized and an Agency-wide communication plan is being developed.  This communication plan will include Standard Operating Procedures (SOPs) that require API developers to register dataset APIs in the EPA's Environmental Dataset Gateway, which will allow these APIs to become part of the EPA's EDI/PDL.  All other APIs will be registered in EPA's Reusable Components Services (RCS).