Overview

TerriaJS can be extensively customized, often without writing any code. The catalog and many aspects of the look and feel are controlled by JSON configuration files.

This section explains the various ways to customize a TerriaJS application. It assumes you have already completed the Getting Started section and have a working Terria Map.

• Client-side Config: Configure which catalog (init) files to load, the application name and support email address, the branding at the top of the application, disclaimers, keys for Bing Maps and Google Analytics, and more.
• Initialization Files: TerriaJS init files describe the catalog that will be presented to the user, the initial map view, and more. Init files let you connect TerriaJS to your servers and data.
• Server-side Config: Configure which domains the server will proxy for (to avoid Cross-Origin Resource Sharing (CORS) problems), persistence of sharing data, and more.
• Skinning: Customize the look and feel of a TerriaJS application.
• Cloning and Building: Build TerriaMap locally to customize your application further