You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<p><strong>Safe Agricultural Products and Water Graph (SAWGraph)</strong>: An <b>Open Knowledge Network </b> to Monitor and Trace PFAS and Other Contaminants in the Nation's Food and Water Systems
<p>The goal of SAWGraph is to connect federal and other datasets to more quickly analyze data and make decisions around per- and polyfluoroalkyl substances (PFAS) sources, testing, impacts, and risks
43
-
The graph will integrate data data and provide interfaces that support analysis, mapping and communication of the results of testing for PFAS contamination, spatial connections to known and potential sources to support PFAS research and decision making around PFAS testing and mitigation.
44
-
The primary end users of SAWGraphs are personnel at state and federal agencies who monitor the environment and the safety of drinking water and agricultural land and products. End users include but are not limited to personnel at EPA and state environmental protection agencies (e.g. state environmental toxicologists) and at USDA and state agricultural agencies. Other potential users include experts from FDA, USGS and similar state agencies.
45
-
We distinguish four types of users based on their primary responsibility: (1) drinking water monitoring; (2) understanding the extent and sources of environmental contamination with PFAS; (3) PFAS researchers; (4) environmental justice.
46
-
The graph is expected to empower these users to: (1) formulate and implement comprehensive test plans aimed at monitoring elevated PFAS levels in drinking water or agricultural lands, (2) pinpoint the most significant sources of PFAS in a state and how it impacts disadvantaged communities; (3) identify populations at elevated risk and prioritize testing resources and support accordingly; (4) design contamination management and remediation plana; and (5) identify research gaps in knowledge about PFAS fate and transport. Collectively, these applications will expedite comprehension of PFAS contamination and its mitigation, while ensuring the efficient and equitable allocation of testing and remediation resources.
47
-
</p>
48
-
42
+
<p>The goal of SAWGraph is to connect federal and other datasets to more quickly analyze data and make decisions around per- and polyfluoroalkyl substances (PFAS) sources, testing, impacts, and risks.
43
+
The graph integrates data and provides interfaces that support:
44
+
<ul><li>analysis, mapping and communication of the results of testing for PFAS contamination</li>
45
+
<li>spatial connections to known and potential sources</li></ul>
46
+
to support PFAS research and decision making around PFAS testing and mitigation.</p>
47
+
<p>
48
+
The primary end users of SAWGraphs are personnel at state and federal agencies who monitor the environment and the safety of drinking water and agricultural land and products.
49
+
End users include but are not limited to :
50
+
<ul><li>personnel at EPA and state environmental protection agencies (e.g. state environmental toxicologists)</li>
51
+
<li>personnel at USDA and state agricultural agencies.</li>
52
+
<li>experts from FDA, USGS and similar state agencies. </li></ul>
53
+
We distinguish four types of users based on their primary responsibility:
54
+
<ol>
55
+
<li>drinking water monitoring </li>
56
+
<li>understanding the extent and sources of environmental contamination with PFAS </li>
57
+
<li>PFAS researchers </li>
58
+
<li>environmental justice</li>
59
+
</ol>
60
+
The graph is expected to empower these users to:
61
+
<ol><li>formulate and implement comprehensive test plans aimed at monitoring elevated PFAS levels in drinking water or agricultural lands,</li>
62
+
<li>pinpoint the most significant sources of PFAS in a state and how it impacts disadvantaged communities;</li>
63
+
<li>identify populations at elevated risk and prioritize testing resources and support accordingly;</li>
0 commit comments