In order to view images and {{glossary.Point cloud}}s in the browser, the data needs to be prepared for NavVis IndoorViewer. This is done during Web Processing.

For each {{glossary.Web-processed dataset}}, a corresponding folder is created named datasets_web/<date-time>.
A {{glossary.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.
`cam/`	Optional. Tiles generated from the original images to use for previewing {{glossary.Dataset}}s 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) is created for each successful capture event (the panorama has been successfully web-processed).
`logs/`	See Log files.
`maps/`	Contains 2D geo-registration maps (see 2D Geo-Registration Maps) for the processed data in different resolutions. Quality maps (see 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.
`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.
`sensor_frame:xml/sig`	Digital signature of the calibration file

Introduction