Six layers, six provenance rows: the Week 5 audit in PHLT 8076 traces tract boundaries, census estimates, visit records and two screening indexes, then flags a vintage mismatch between them. Searches like "phlt 8076 week 5 assignment example", "phlt8076 week 5 sample" and "phlt 8076 week 5 example" land here.
What a finished PHLT 8076 Week 5 layer provenance audit looks like
At its center sits a table, wrapped in a short paper. Rows are layers: tract boundaries from the Census Bureau's TIGER/Line files, child population from American Community Survey five-year estimates, emergency visit records geocoded to home address across the made-up county, the CDC Social Vulnerability Index, EPA's EJScreen indicators, and a state roads layer marking the freight corridor. Columns record publisher, purpose, vintage, geographic unit, known exclusions and the date the layer was retrieved. The prose then interprets the table. ACS figures are period estimates with margins of error, not counts. SVI ranks tracts relative to others and carries its own release year. EJScreen is a screening tool, not a finding. The central finding is a vintage problem: visit years span a decennial census, so some visits were geocoded to tracts that were later redrawn.
How a PHLT 8076 Week 5 example is structured
A short introduction states why provenance matters for this map in particular: every layer was built for someone else's purpose. The table follows immediately, one row per layer and the same six columns throughout, so gaps are visible as blank cells. Interpretation is grouped by problem rather than by layer. One section covers estimates that carry uncertainty, chiefly the ACS denominators. A second covers derived indexes, SVI and EJScreen, explaining that each combines other variables and inherits their vintages. A third covers the visit file, including its geocoding and the addresses that failed to match. The vintage mismatch gets the longest section and a proposed remedy, allocating visits to consistent boundaries. The paper ends by stating which claims the finished map can support once the mismatch is handled, and which remain out of reach.
Six rows, six columns
Each layer is described by publisher, purpose, vintage, unit, exclusions and retrieval date. Blank cells stay blank, since an unknown vintage is itself a finding the reader needs.
Estimates, not counts
ACS five-year figures describe a period and carry margins of error that grow in small tracts. The audit notes that a denominator's uncertainty travels into every rate built on it.
Indexes built from other layers
SVI ranks tracts on social factors drawn from census estimates, and EJScreen combines environmental and demographic indicators for screening. Each inherits the dates of its inputs, which the audit records.
Addresses that did not land
Some visit records fail to geocode, and the failures may cluster on rural routes or in new developments. The audit reports the unmatched share as unknown for the composite file and leaves the rate blank.
Boundaries that moved
Tracts are redrawn after each decennial census, and the visit years straddle one. The audit proposes allocating records to a single boundary vintage before any rate is mapped.
Where marks go in PHLT 8076 Week 5
Most drafts of this audit fall short in the vintage column, and completeness of the table is marked before anything else. An audit that names each layer's publisher but leaves dates blank, or gives a download date in place of the data's reference period, has audited the website rather than the layer. Interpretation counts for more than tabulation: a layer's provenance matters only through what it does to the map, and papers that list facts without drawing consequences stop halfway. Treating ACS figures as exact counts, or EJScreen output as a determination of harm, are accuracy errors that graders note quickly. The mismatch section earns the largest analytic share when it proposes a remedy and says what the remedy cannot fix. Consistent citation of each dataset, including version or release, completes the grade.
Get a PHLT 8076 Week 5 example written to your instructions
List the layers in your map, or send the project description, with the Week 5 prompt and rubric; the provenance audit, table included, arrives in 24-48h and the first is free. Vintages are reported as each publisher documents them, and when a date cannot be confirmed the cell says unknown instead of guessing.
PHLT 8076 Week 5 questions, answered
What counts as a layer's vintage?
The period the data describe, not the day they were downloaded. A boundary file has a census year, an ACS estimate covers a five-year span, and an index has a release that may draw on older inputs. The sample records both the reference period and the retrieval date, because a reader checking your map later may find the publisher has replaced the version you used.
Why include EJScreen and SVI if the map shows visit rates?
Because the composite county's final map uses them as context layers, and any layer on a map needs an entry in the audit. Both are indexes rather than measurements, which is exactly the kind of provenance detail a reader needs. If your map uses neither, the audit simply covers the layers you actually draw, with the same six columns.
Is geocoding accuracy part of provenance?
Yes. Turning addresses into decimal coordinates and then into tracts is a processing step with its own failures, and records that fail to match drop out silently unless someone reports them. The sample flags the unmatched share as a required entry. Your audit reports the match rate from your own processing or from the data provider's documentation.