Consolidate progressive globe + explorer into one Interactive Explorer page

[rdhyee]

Context

Hana's wireframe shows a single "Interactive Explorer" page with: map, search bar, faceted filters (Source, Material, Sampled Feature), sample card, and collapsible code sections.

We currently have two separate pages:

• progressive_globe.qmd — H3 cluster visualization with source filtering
• isamples_explorer.qmd — search + faceted filters + globe (currently buggy)

Wireframe spec

1. Interactive Map (top)
2. Search bar ("Search Samples")
3. Collapsible Filters panel:
   • Source (4 checkboxes) ✅ already on globe
   • Material (4 checkboxes) — needs facet_summaries.parquet
   • Sampled Feature (4 checkboxes) — needs facet_summaries.parquet
4. Sample Card (below filters)
5. Collapsible Code sections (Setup, Search & Filters, Database & Queries, Debug Info)

Approach options

A. Enhance progressive_globe.qmd — add search + material/feature filters to the working globe page. Simpler, builds on what works.

B. Fix and enhance isamples_explorer.qmd — it already has the structure but is buggy (PR #54 fixed one issue, still has schema mismatch issues).

C. New page — start fresh combining best of both. Most work but cleanest result.

Recommend Option A — the progressive globe is stable, performant, and already has source filtering. Adding search + two more filter facets is incremental.

Related

• Figma wireframe: Interactive Explorer (node 7:186)
• Issue Zenodo analysis: material category section empty due to PQG schema change #57 (material category schema mismatch)
• Wide format should include denormalized human-readable columns pqg#20 (denormalized columns needed)

[rdhyee]

UX note from Hana's testing (2026-03-17): Chrome on Windows 11 hit a transient TProtocolException: Invalid data error loading parquet data. Brave on the same machine worked fine. Likely a browser-specific issue with HTTP range requests to R2.

Action item: Add user-friendly error handling when DuckDB-WASM parquet reads fail — show a "Data failed to load — try refreshing" message with a retry button, instead of silent failure or cryptic console errors.