awesomedata/awesome-public-datasets

Prefer upstream for current dataset discovery. Choose this fork only if you want a frozen copy with no expectation of updates.

Choose this fork only if you want a narrower, more manual public-domain/government dataset catalog. If you want the latest breadth, freshness, and autogenerated maintenance from the upstream project, upstream is the better default.

Prefer upstream unless you specifically need a historical, read-only snapshot. This fork offers no visible added capability and is materially behind on catalog freshness.

Prefer this fork only if you specifically want the added government section and are comfortable with a stale catalog. For most adopters, upstream is the better choice because it is much more current, broader, and actively maintained.

Prefer upstream unless you specifically want an older, manually edited snapshot with a few niche additions. For most adopters, this fork is too stale to trust as a current dataset catalog.

Prefer upstream for current dataset discovery. Choose this fork only if you explicitly want a frozen snapshot and do not care about recent updates.

Prefer upstream if you want current coverage and active maintenance. Choose this fork only if you specifically want its older manual curation, cleanup work, or the extra dataset picks it added.

Prefer upstream for current coverage and active maintenance. Choose this fork only if you want the older, manually curated dataset list and its added society/regional entries, and you accept substantial staleness.

Prefer upstream for an up-to-date, broader dataset catalog. Choose this fork only if its niche additions matter more than freshness and coverage.