Skip to content

Catalogues and sources

All runtime data is hosted with the application. Import scripts clean source snapshots, normalise identifiers and units, validate references, create binary catalogues or spatial tiles, and update the versioned manifest before deployment.

Current coverage

LayerRuntime coverageScientific treatment
Solar SystemSun, eight planets, selected moons and minor bodiesLocal ephemerides and documented orbital providers
Confirmed exoplanets6,333 planets around 4,747 hostsNASA composite catalogue facts; illustrative close-up systems
Stellar catalogue10,000 selected HYG starsObserved catalogue coordinates with proper-motion support
Constellations88 modern figures, 644 segmentsCultural line conventions mapped to HYG identifiers
Historical supernovas6 events and remnantsDocumented positions and dates; illustrative visual evolution
Local Group31 galaxiesCatalogue positions with adapted morphology and size
Nearby Universe720 galaxiesStatic local-volume octree and catalogue-backed overview
Cosmicflows-437,730 galaxy groupsCalculated three-dimensional positions from published catalogue fields
Large-scale structures26,520 positionable detectionsSeparate cluster, supercluster, wall, basin, attractor, repeller, void, and filament products
Tempel filaments15,421 spines and 275,599 pointsPublished spine geometry preserved in a compact binary layer

The Tempel binary is fetched and validated in a dedicated Web Worker at cosmic-web scale. Its six decoded typed-array buffers are transferred back without copying; browsers without Worker support use the same validated loader on the main thread.

The 20 named flow landmarks are not merged into the Tempel network: two walls retain their published representative extents, 15 probabilistic basins use the published Table 2 centres and probabilities, and attractor/repeller symbols mark reconstructed velocity-field extrema. Basin radii are equivalent display radii derived from published volumes, not observed spherical boundaries.

Principal sources

The repository records detailed licences and transformations beside the static datasets and texture assets. Bundled third-party material remains subject to its original licence even though the application source is MIT licensed.

Static manifest

/data/manifest.json is the browser entry point. Every dataset declares an identifier, URL, type, and format where applicable. The loader validates JSON structures and binary headers before exposing data to the engine. A failed optional catalogue produces a development warning without corrupting unrelated layers.

Rebuilding data

The repository includes deterministic Node.js import commands for stars, exoplanets, nearby galaxies, constellations, Cosmicflows groups, cosmic volume, and published structures. Source snapshots are not part of the browser runtime.

bash
cd client
npm run data:stars
npm run data:exoplanets
npm run data:nearby-galaxies
npm run data:cosmic-web
npm run data:cosmic-structures
npm run test:data

Not every import should be run on each application build. Prepared versioned artefacts are committed and validated; import commands are used when intentionally refreshing a source snapshot.

Next: Performance and limits.

Scientific data and visual adaptations are identified separately.