geospatial-frontend

Build satellite imagery retrieval web apps using a Vite and vanilla TypeScript setup with MapLibre for 3D globe rendering and DuckDB-WASM for spatial data access. It supports interactive AOI drawing and tutorial-driven search flows.

DuckDB-WASM handles geospatial filtering by loading Parquet manifests and shards in a web worker, performing spatial queries on demand. This keeps heavy compute operations off the main thread for efficient metadata and embedding retrieval.

Yes, MapLibre works with vanilla TypeScript to support interactive box and polygon AOI drawing on a 3D globe. The implementation uses GeoJSON-based map layer pipelines with state-driven re-rendering for responsive updates.

Scaffold a map-centric demo using a fixed HUD layout with transparent panels for search, controls, status, and results overlaid on a warm-dark MapLibre globe. This provides a guided multi-step spotlight walkthrough for retrieval flows.

Yes, web workers are required to run DuckDB-WASM spatial queries and compute similarity for embeddings without blocking the UI. This two-phase loading approach fetches metadata first, then loads embeddings on demand.

A two-phase loading approach is needed to efficiently manage satellite data by loading metadata first, then fetching embeddings on demand. This prevents large data payloads from degrading the map rendering performance.