互动式 3D 卫星图像浏览器将 NASA GIBS 和 Copernicus Sentinel 数据引入到一个基于 Three.js 的地球上,具有区域缩放、时间滑动和 OpenAI/Anth
互动式 3D 卫星图像浏览器将 NASA GIBS 和 Copernicus Sentinel 数据引入到一个基于 Three.js 的地球上,具有区域缩放、时间滑动和 OpenAI/Anth
Earth View is an open-source satellite imagery explorer built with React, Vite, Three.js, Tailwind CSS, and Zustand. It starts with a 3D NASA GIBS globe, lets you zoom into a detailed regional pass, and opens a modal workspace for higher-resolution inspection, Sentinel imagery, time lapses, Google Maps handoff, and optional AI-assisted image analysis.
Not a developer? Grab the desktop app — no setup required:
⬇ Download Earth View for Windows
Run the installer (on first launch Windows may show a SmartScreen warning — click More info → Run anyway). The NASA globe works right away. To unlock Sentinel imagery and Ask AI, add your own free Copernicus keys (and optional OpenAI / Anthropic keys) in the app's Settings window. Build details: desktop/README.md.
This README is focused on getting a new copy running from scratch. For deeper architecture notes and feature details, see README-extended.md.
You can run the app immediately with no credentials. The no-key mode includes:
Optional credentials unlock:
Clone the repo:
git clone
cd earth-viewInstall dependencies:
npm installCreate a local environment file:
cp .env.example .envOn Windows PowerShell:
Copy-Item .env.example .envStart the dev server:
npm run devOpen the app at:
http://127.0.0.1:5173If you add or change .env values while the dev server is running, stop it and restart npm run dev.
.env.example contains all supported local variables:
COPERNICUS_CLIENT_ID=
COPERNICUS_CLIENT_SECRET=
OPENAI_API_KEY=
ANTHROPIC_API_KEY=All of these are optional for basic NASA GIBS usage. Do not prefix them with VITE_; they are read by the local/API server layer and should not be exposed to browser code.
Older Sentinel Hub variable names are still accepted:
SENTINELHUB_CLIENT_ID=
SENTINELHUB_CLIENT_SECRET=Prefer COPERNICUS_CLIENT_ID and COPERNICUS_CLIENT_SECRET for new setups.
Sentinel support is optional, but it unlocks regional Sentinel-2 and Sentinel-1 imagery in the modal.
.env:COPERNICUS_CLIENT_ID=your_client_id
COPERNICUS_CLIENT_SECRET=your_client_secretThe app uses these credentials server-side to request access tokens from the Copernicus Data Space token endpoint, then calls the Sentinel Hub Process and Catalog APIs. The official authentication guide is here: Sentinel Hub API authentication.
After saving .env, restart the dev server.
Ask AI is optional. It appears inside the modal and can analyze the currently displayed image with view context such as coordinates, date, imagery provider, bbox, scene metadata, and follow-up chat history.
You can configure either provider or both.
.env:OPENAI_API_KEY=your_openai_keyOpenAI's current quickstart is here: OpenAI developer quickstart.
.env:ANTHROPIC_API_KEY=your_anthropic_keyAnthropic's current API overview is here: Claude API overview.
After saving .env, restart the dev server.
On the globe:
In the modal:
npm run dev # Start Vite with local API middleware
npm run build # Type-check and build the production bundle
npm run preview # Preview the production build locally
npm run lint # Run ESLintThe app is a Vite SPA with serverless-style API handlers in api/.
For a hosted deployment:
npm install.npm run build.dist/ directory.api/ or adapt them to your server/runtime.NASA GIBS-only functionality does not require server-side credentials, but Sentinel and Ask AI do.
The globe loads but Sentinel layers fail
Check that COPERNICUS_CLIENT_ID and COPERNICUS_CLIENT_SECRET are set in .env, then restart the dev server. Also confirm the OAuth client is active in the Copernicus Data Space Sentinel Hub Dashboard.
Ask AI is visible but requests fail
Set OPENAI_API_KEY or ANTHROPIC_API_KEY, restart the dev server, and verify the provider account has billing/API access enabled.
Environment variables are not being picked up
Restart npm run dev. Vite and the local API middleware read .env at server startup.
Imagery appears stale for the current day
Some public satellite products lag behind real time. The app intentionally defaults to a recent likely complete VIIRS day to avoid requesting incomplete current-day true-color imagery.
The browser is sluggish
The globe uses large WebGL textures and can be demanding on older hardware. Try closing other GPU-heavy tabs or reducing browser zoom.
The concise setup guide lives here in README.md. The fuller technical document is preserved as README-extended.md, including architecture notes, provider details, and implementation-oriented guidance.
暂无开放 Issues,或尚未同步最近议题。