Documentation overview

The Masterportal requires various configuration files documented on these pages. Furthermore, available URL parameters and required proxies are described.

Table of Contents

• Documentation overview
  • Configuration files
    • Global configuration files
    • Portal-specific configuration files
  • URL parameters
  • Proxies

Configuration files

The Masterportal builds on global and portal-specific configuration files alike.

Global configuration files

These files describe central information to be used by multiple portals:

• services.json: lists all available layers
• rest-services.json: URLs to various external services
• style.json: holds style definitions for vector layers

Portal-specific configuration files

These files define the distinguishing features of an instance:

• config.js: Configuration of paths to further configuration files and services
• config.json: Configuration of portal appearance and available contents (If the bitbucket site isn´t displayed correctly please use this link: alternative config.json documentation)

The following figure schematically demonstrates the ensemble of files. Please mind that the files index.html, config.js, and config.json must be placed in the same path.

URL parameters

The Masterportal can be called with URL parameters to e.g. call functions initially or describe a view.

Proxies

For requesting attribution information via WMS GetFeatureInfo and for loading WFS layers, proxies have to be defined.