Default Configuration

Main
1. Load from no config object
2. Load with wrong JSON object
3. Load with bad config values
4. Load layers with bad config values
5.A Load config from URL params
5.B Load config from div params
6. Load config from file
7. Load config from function call
This page is used to showcase how we validate map configuration object before creating the map.

1. Load from no config object

Top

This map will will load with default configuration because none is provided.


2. Load with wrong JSON object

Top

This map will load with bad configuration ('center': [-100, x]) replaced with default.


3. Load with bad config values

Top

This map will load with bad configuration replaced with default.


4. Load layers with bad config values

Top

This map will not load layers with bad configuration and inform the user.


5.A. Load config from URL params

Top

This map loads it's configurations from the URL parameters by providing a data-shared attribute. If a data-config attribute was also provided then the later will have its configuration overriden with config from url parameters.


5.B. Load config from div params

Top

This map loads it's configurations from the div parameters by providing a data-geocore-keys and optionally a data-geocore-endpoint.


6. Load config from file

Top

This map loads it's configurations from a file by providing data-config-url, the map is static!


7. Load config from function call

Top

This map loads it's configurations from a function call (after 10 seconds). Configuration error with double layer id.