The Difference Between Open Data and Public Data
Two Words That Sound Alike
On slashopen.net we often hear people say "we publish open data" when what they really mean is "we publish public data". The two phrases look similar, but they describe very different legal and practical situations. Public data simply means information that anyone can view. Open data means information that anyone can view, use, reuse, modify, and redistribute, usually under a clear license.

A PDF on a government website is public. A CSV with an explicit open license is open. The first one lets you read. The second one lets you build.
What Public Data Actually Means
Public data is data that has been made accessible to the general public. It may be a budget report, a transport timetable, or a list of registered businesses. The key point is visibility, not permission.
Because public data carries no explicit license, the default rules of copyright usually apply. You can read the file, but you may not have the right to republish it, merge it with other datasets, or sell a product built on top of it. Visibility is not the same as permission.
"Public" describes who can see the data. "Open" describes what they are allowed to do with it.
What Open Data Adds
Open data begins where public data stops. It adds a license that grants everyone the freedom to use, reuse, and redistribute the material, including commercially. The Open Definition captures this clearly: data is open if anyone is free to use, reuse, and redistribute it, subject only to attribution or share-alike requirements.
That license is what turns a static file into infrastructure. Developers can cache it, transform it, combine it with other sources, and ship it inside real products without asking for permission each time.
Why the Difference Matters
The difference is not academic. It shapes what a community can build. Consider two portals that both publish the same bus schedule:
- Portal A posts a PDF with no license. Readers can look, but app developers cannot legally reuse it.
- Portal B posts a CSV under an open license. Anyone can build a journey planner, a map layer, or an accessibility tool.
The data is identical. The freedom is not. One produces readers, the other produces ecosystems.
| Aspect | Public Data | Open Data |
|---|---|---|
| Access | Anyone can view | Anyone can view |
| Reuse | Often restricted | Explicitly allowed |
| License | Usually unclear | Clear and stated |
| Redistribution | Risky | Permitted |
A Practical Checklist
Before you call a dataset open, ask a few simple questions. If you cannot answer yes to all of them, you are probably describing public data.
- Is the data available in a machine-readable format?
- Is there an explicit license attached to it?
- Does that license allow commercial reuse?
- Does it allow modification and redistribution?
- Is the license easy to find, not buried in a legal notice?
Publishing a file online is a start. Granting others the freedom to use it is the real commitment. Openness lives in the license, not in the URL.
