/jump to repo

Repos Recent Bookmarks Watched Notes Tags Discover Compare Stats GitHub

Repository brief

awesomedata/awesome-public-datasets

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis

cached 2026-03-30T12:54:06.837Z

3mo ago

awesomedata/awesome-public-datasets

A large, actively updated curated list of high-quality public datasets, organized by topic. The repo is mostly a generated README plus a `Datasets` directory, and it appears to be used as a catalog rather than a code project.

Loading tags...

Stars73,742

Forks11,225

Default branchmaster

Last pushed2026-03-17T20:37:52Z

Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

10 of 10 fork briefs

Maintenance:

Magnitude:

Sort:

Selected

Prefer upstream for current dataset discovery. Prefer this fork only if you want the older, smaller catalog and specifically value the extra niche additions more than freshness or completeness.

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.

Fork comparison

ChristosChristofidis/awesome-public-datasets

37/100

stale

significant_divergence

Prefer upstream for current dataset discovery. Prefer this fork only if you want the older, smaller catalog and specifically value the extra niche additions more than freshness or completeness.

Likely purpose

To preserve or extend an earlier version of the dataset directory for users who want a simpler, older catalog with some extra manual additions rather than the actively maintained upstream generator-driven repo.

Best for

People wanting an older reference snapshot of the dataset list.; Users specifically interested in the extra niche dataset categories this fork added.; Anyone who prefers manual curation over the upstream automated generation pipeline, and can tolerate staleness.

Additional features

Adds manual entries for areas called out in commit history such as museums, transportation and marine traffic, GIS datasets, government open data portals, and the Protein Data Bank.
Appears to be a simpler hand-edited catalog snapshot that may be easier to browse if you want the 2014-era structure instead of the larger generated upstream README.
Adds fork-specific behavior in `README.rst` and `LICENSE`.

Missing features

Falls far behind upstream and is missing much of the newer dataset coverage and ongoing README refreshes.
Does not appear to follow the upstream apd-core generation and update workflow, so keeping entries current is harder.
Likely omits newer topic expansion and link maintenance present in the actively updated upstream catalog.
Contains at least one explicit removal of an entry with a broken link, which means some upstream breadth is intentionally trimmed.
Some upstream behavior appears to be removed, disabled, or intentionally stripped down in this fork.
It trails upstream by 200 commits, so some recent upstream features and fixes are likely not present yet.

Strengths

Small, frozen snapshot with a clear historical state.
Includes some useful domain-specific additions that may matter if you care about GIS, transport, museums, or open-government datasets.

Risks

Very stale compared with upstream.
High chance of broken or outdated links and incomplete coverage.
Not a good choice if you want an up-to-date discovery catalog.