General field guides

Publish useful disease maps without exposing farm locations

Publish disease maps at the geographic detail needed for the public question and supported by the source permissions. Keep precise operational locations in a separately controlled record, review the actual exports and explain the reporting unit. Generalized points, suppressed values and missing records must not imply unsupported occurrence or absence.

Updated 857 words · 4 min read

Start with the public question

A map that compares reports by state does not need a pin on every barn. Decide whether readers need a region, jurisdiction, approximate area or exact public facility. The level of detail should follow that purpose rather than the precision available in a spreadsheet.

Do not assume that an exact coordinate is suitable for publication because somebody included it in an attachment. Establish how the information was obtained, who maintains it and what disclosure was agreed. This guide describes publication design; it does not determine legal permission for a particular dataset.

Review more than the visible marker

Precise locations can remain in downloadable files, map-layer properties, popup text, image filenames and embedded metadata after a visible pin has been generalized. Review the material a visitor can actually download or inspect, not just the opening map view.

A public copy should have its own export specification. Remove fields that have no public purpose rather than relying on a hidden column or an unselected map layer. Keep the restricted original under its established access arrangements.

Avoid misleading replacement points

Placing every record at a county center can create an apparent cluster at that location. If the public unit is a county, a shaded county or a table may communicate the information more clearly than an apparently exact point.

Describe the geographic unit explicitly. “Reported within the county” is different from “occurred at this coordinate.” Do not move a private point slightly and then present the result as a real occurrence location.

An illustrative export review

Consider a fictional archive with a public state summary and a private contact workbook. The summary needs disease label, reporting period and state. It does not need farm name, telephone number, gate location or the private workbook's row link.

Build a public-only table from the allowed fields and inspect its exports. Check a sample popup, the downloaded CSV and the map-layer attributes. Then confirm that the legend explains the reporting unit and whether the entries describe historical records or a current reporting period.

Remember small groups and indirect clues

Removing a farm name may not make a record unidentifiable. A distinctive date, rare animal group and narrow location can point to one operation when combined with other public information. Review the combined display and explain any suppression or aggregation rule.

If an entry is withheld, do not display its absence as proof of no disease. A map's omissions may reflect privacy, reporting coverage, permissions or missing records. Those are limitations of the display, not biological findings.

Document the publication decision

Retain the export fields, geographic treatment, source restrictions and review date. When the dataset changes, repeat the review on the new file; a previously safe export does not guarantee that newly added columns are suitable.

The surveillance reference helps describe population and reporting scope. The data-release reference explains how to preserve a specific public release without exposing its restricted working material.

Keep county display states distinct

In a fictional county map, one county has a published zero, another has a value withheld by the source and a third has no submitted value in the release. Give those states distinct labels in the legend and table. Do not fill all three with zero just to simplify the color scale or CSV.

Preserve the source’s suppression wording and release period. Check that the public download does not contain values intentionally withheld in the map, and that related summaries do not defeat the intended disclosure limit. This review needs the complete proposed release; a blank map cell alone establishes neither anonymity nor an absence of disease.

Questions for the public export review

Does hiding a map layer remove its private attributes?

Inspect the actual delivered files, downloads and layer properties. A field can remain accessible even when the initial view does not display it. Use a public-only export specification rather than relying on visual hiding.

Can a slightly moved point be called the real location?

Choose and explain a suitable geographic representation. A generalized unit or table may be clearer than a displaced point that appears exact. Do not imply precision or a real occurrence coordinate the public data do not supply.

Does a suppressed value mean zero disease?

Keep withheld, missing and measured zero states distinct. Preserve the source's period and suppression wording. The absence of a public value can reflect the display's disclosure or coverage limits rather than a biological finding.

In a second fictional review, the map omits a farm name but a downloadable filename retains it alongside a narrow date and rare host group. The publication decision is applied to the full release, including filenames and dependent summaries. That correction can reduce unnecessary disclosure without promising anonymity or deciding a specific legal question. Keep the precise working record controlled and available to authorized reviewers for its legitimate purpose.

Cite this reference

LivestockDefense. “Publish useful disease maps without exposing farm locations.” Updated 2026-11-03. https://livestockdefense.com/guides/avoiding-farm-gps-disclosure-in-outbreak-reference-maps/

Add the date you accessed the page. This identifies the current reference; keep a permitted saved copy if your work depends on its exact wording. A citation alone does not establish support for a claim.

How to cite a page and its revision ↗