Why Is My Dataset Loading Slowly?

Dataset loading performance depends on network latency, visual layer configuration, ROI resolution settings, and browser memory.

Consider the following common factors and optimization steps:

• Initial Dataset Manifest Load: The first time a dataset opens, CartoScope fetches the catalog.yaml metadata and spatial tile indexes. External datasets (AWS S3, Zenodo) may take a moment depending on server location and network bandwidth.

• Active Layer Stack: Each visible layer renders independently. In the Layer Drawer, click the eye icon to hide unused layers. Switching RAW_PIXEL factor layers to HEX or CELL modes reduces GPU shader workload.

• ROI Resolution Mode: Fetching large ROIs with "Full ROI Loading" retrieves all raw transcript points at full spatial resolution. Use Current-Level Loading during exploration to speed up tile fetching.

• Browser Hardware Acceleration: Ensure GPU acceleration is enabled (chrome://settings/system) so WebGL tile rendering does not fall back to CPU processing.

---

Related Pages

FAQ

• What Are the ROI Data Loading Options?
• Why Is the Map Laggy?