Region datasets page lists 50 of 88, and hides every dataset with no extent

[mosoriob]

Question

Build it. #97 decided the rule and wrote the extractor. This ticket applies both to the browse surface, which #97 deliberately left alone.

The problem

/regions/:id/datasets carries the exact fault #97 fixed in the thread wizard, plus a silent row cap.

RegionDatasets.tsx:20-23 sends CKAN an ext_bbox and asks for rows: 50 with a bounding box, rows: 20 without.

Two consequences, measured against TACC on 2026-08-09:

Packages in TACC's catalog	215
ext_bbox returns for Texas	88
The page lists	50 — no count, no "show more"
Packages with no spatial extent	104, none of which can ever appear

Classifying the whole catalog client-side against Texas gives 90 inside, 21 outside, 104 unknown. The page can show at most 88 of those 111 that are not unknown, and does show 50.

What to build

Both halves already exist.

• The rule — #97: unknown extent is shown and badged; known-but-outside is hidden behind a counted link. Same rule, so the two surfaces agree.
• The extractor — lib/geo/bbox.ts, which handles the Feature, FeatureCollection, Point and MultiPolygon that ext_bbox and the old readers drop.
• The paging — searchAllPackages in lib/datasets/ckan.ts, which Thread datasets: ui-react searches CKAN free text instead of the mint_standard_variables field #94 taught to page. rows: 50 predates it.

Scope

Client-only. No change at TACC. No Hasura metadata change.

It does not block the flip (#77). This is a browse surface, not the first thing a person meets in a thread, which is why #97 was made a blocker and this is not. That is a judgement, not a measurement — re-decide it if TACC opens the regions pages first.

Also check /datasets/browse while here. It rendered on #76, but that proved reachability, not that it lists the right rows.