Gridlook is a WebGL-based viewer for Earth system model (ESM) output. It supports cloud-hosted Zarr, Icechunk and NetCDF datasets, as well as local Zarr stores and local NetCDF files opened directly from your file system.
Try out the example dataset:
You can view any CORS-enabled, public Zarr, Icechunk or NetCDF dataset with Gridlook:
https://gridlook.pages.dev/#<DATASET_URL>
Gridlook can also load catalog JSON files that list multiple datasets. The catalog format and deployment options are documented in docs/catalogs.md.
Gridlook can follow live datasets (a Zarr store where only the current timestep is available, updated as a simulation runs) by appending ::live=true to the dataset URL. See docs/live-datasets.md.
A guide to the viewer keyboard, mouse, and touch interaction is available in docs/Controls.md.
Besides remote URLs, the "Open dataset" dialog lets you open a local Zarr store (select the whole dataset directory) or a local NetCDF file (.nc, .nc4, .cdf) directly from your file system. Local NetCDF files are read in-browser via WebAssembly; nothing is uploaded to a server.
URL-sharing does not work for local datasets. Gridlook's URL only stores a reference to the file that was selected, not its content, so a shared link, bookmark, or page reload cannot restore a local dataset — you will need to re-select the file or directory. URL sharing (#<DATASET_URL>) is only supported for remote, publicly reachable datasets.
Gridlook opens remote Zarr stores, Icechunk repositories, Kerchunk reference files and NetCDF files by URL. The data type is detected automatically or can be forced with a URL prefix like netcdf+. For datasets that need authentication, the "Open dataset" dialog can send a bearer token, custom headers and cookies. See docs/data-sources.md.
This project uses Node.js and vue.js
npm installnpm run devnpm run buildLint with ESLint
npm run lintThe project is served at http://localhost:3000/ when you run npm run dev.
Gridlook loads datasets directly in the browser, so the server hosting the data must allow cross-origin browser requests with CORS.
To check whether CORS is enabled, open the dataset URL in Gridlook and inspect the browser's developer tools. If the request is blocked, the Console or Network tab usually shows a message such as "blocked by CORS policy" for the dataset metadata or chunk request.
You can also check the response headers with curl by sending an Origin header:
curl -I -H "Origin: https://gridlook.pages.dev" "https://s3.eu-dkrz-1.dkrz.cloud/wrcp-hackathon/data/ICON/d3hp003.zarr/P1D_mean_z7_atm"If CORS is enabled for Gridlook, the response should include an Access-Control-Allow-Origin header that matches the origin or allows all origins with *:
access-control-allow-origin: https://gridlook.pages.dev
If you run the data server yourself, ask your server administrator before relaxing CORS settings, especially before allowing requests from every origin. Broad CORS permissions can expose data to untrusted websites and may conflict with your organization's security policy.
