---
title: "Web-Processed Data"
slug: "web-processed-data"
updated: 2026-03-09T09:48:44Z
published: 2026-03-09T09:48:44Z
canonical: "knowledge.navvis.com/web-processed-data"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.navvis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Web-Processed Data

NavVis IVION works in the browser. During web processing, each dataset is converted into a structured `datasets_web/<date-time>` folder that contains everything NavVisIVIONneeds: calibrated panorama tiles, point clouds for streaming, geo-registration and quality maps, control point and logging data, and core metadata about the capture. This guide explains the purpose of each file and directory in that structure so you can quickly understand, validate, and troubleshoot your processed datasets.

In order to view images and Point clouds in the browser, the data needs to be prepared for NavVis IndoorViewer. This is done during [Web Processing](/v1/docs/web-processing-1).

- For each Web-processed dataset, a corresponding folder is created named `datasets_web/<date-time>`.
- A Web-processed dataset contains the following folders and files:

| **File/Directory** | **Description** |
| --- | --- |
| `anchors/` | Contains various**`<anchors>.txt` files as well as an `origin.json` file. These files provide control point information and indicate the state and success of anchor usage during different steps of post-processing with anchors. See also [Dataset Control Point Info File](/v1/docs/dataset-control-points-info-file). |
| `cam/` | Optional. Tiles generated from the original images to use for previewing Datasets for the NavVis M6. |
| `cam/info.list` | If a `cam/` folder was generated: Lists the `*info.json` files created in the `info/` folder. |
| `info/*.json` | An `*info.json` file (see [Capture Location Info Files](/v1/docs/capture-location-info-files)) is created for each successful capture event (the panorama has been successfully web-processed). |
| `logs/` | See [Log files](/v1/docs/logs). |
| `maps/` | Contains 2D geo-registration maps (see [2D Geo-Registration Maps](/v1/docs/2d-geo-registration-maps)) for the processed data in different resolutions. Quality maps (see [Quality Map](/v1/docs/quality-map)) in different resolutions are also provided. |
| `pano/` | Contains tiles in four different resolutions generated from the panorama images for use in IndoorViewer. Each resolution has a sub-folder, e.g. `pano/tiles/r3`. Within that are further sub-folders (numbered from 0) containing the tiles for up to 100 capture locations. |
| `pano/info.list` | List of metadata (`*info.json`) files for each successful capture event (the panorama has been successfully web-processed). Only panoramas listed here are shown in IndoorViewer. |
| `pano_depth/` | Internal use |
| `ooc/` | Point cloud for streaming into NavVis IVION. Older format v1. |
| `webcloud/` | Point cloud for streaming into NavVis IVION. Newer format v2. |
| `wifi/` | See [Captured WiFi data](/v1/docs/wifi-data). |
| `dataset.json` | Contains the dataset name entered by the operator, the version layout (dataset identifier), and statistics such as the mapped area and mapping duration. |
| `pointcloud-pcs/ply` | Point cloud for the IV backend, internal use |
| `sensor_frame.xml` | See [Calibration file](/v1/docs/calibration-parameters). |
| `sensor_frame:xml/sig` | Digital signature of the calibration file |

A three-dimensional representation of an environment, made up of many points. A point is defined by x, y and z coordinates, and it may or may not contain RGB, an intensity value, and normals.

Aggregate of data generated from post-processed dataset by running a web-processing task.

A dataset is a piece of a site, the result of a continuous recording with a NavVis mapping device or the result of an imported point cloud. Datasets can contain panoramic images and point clouds.