GeoLeaf Configuration Guide

Product Version: GeoLeaf Platform V2 Version: 2.0.0 Last Updated: avril 2026 Level: Intermediate to Advanced

Version courante : GeoLeaf v2.0.0. Structure de profil modulaire avec fichiers séparés basemaps.json et ui.json.

This comprehensive guide documents all JSON configuration files used by GeoLeaf JS to customize behavior, appearance, and data sources for different business profiles (Tourism, Custom…).

Overview
geoleaf.config.json - Main Configuration
profile.json - Profile Configuration
taxonomy.json - Categories and Icons
themes.json - Layer Visibility Presets
layers.json - Layer Definitions
mapping.json - Data Normalization
Style Files - Layer Styling
POI Configuration
Route Configuration
POI Add Feature — showAddPoi vs poiAddConfig.enabled
geocodingConfig — Address Search

1. Overview

Configuration File Hierarchy

geoleaf.config.json              (Racine — optionnel, sélection du profil)
  └── profiles/
      └── {profile-name}/
          ├── profile.json       (REQUIS — métadonnées, section Files)
          ├── basemaps.json      (REQUIS — sources de tuiles)
          ├── ui.json            (REQUIS — contrôles UI)
          ├── layers.json        (REQUIS — liste des couches)
          ├── taxonomy.json      (REQUIS — catégories & icônes POI)
          ├── themes.json        (REQUIS — préréglages de visibilité)
          ├── mapping.json       (Optionnel — normalisation données POI)
          └── layers/            (Optionnel — configs & données GeoJSON)
              └── {layer-id}/
                  ├── {layer-id}_config.json
                  └── styles/
                      ├── defaut.json
                      └── *.json

Load Order

geoleaf.config.json is loaded first (or defaults are used)
profile.json is loaded based on activeProfile
taxonomy.json, themes.json, mapping.json are loaded in parallel
Layer configs and styles are loaded on-demand when layers are activated
POI/route data loaded as configured in profile.json

Configuration Principles

JSON Schema validation - All files validated against schemas (see schema/)
Graceful fallbacks - Missing optional files use sensible defaults
Profile isolation - Each profile is self-contained
Hot-reloading - Most configs can be updated without page reload
Type safety - TypeScript definitions available in index.d.ts

2. geoleaf.config.json - Main Configuration

Location: Project root or custom path
Required: No (uses defaults if missing)
Purpose: Define which profile to load and debug settings

Complete Structure

json

{
    "debug": false,
    "data": {
        "activeProfile": "tourism",
        "profilesBasePath": "/profiles/"
    },
    "logging": {
        "level": "info"
    },
    "branding": {
        "enabled": false,
        "text": "Mon Application",
        "position": "bottom-left"
    },
    "security": {
        "httpsOnly": false
    }
}

Field Reference

`debug` (boolean, optional)

Active le logging verbeux dans la console. Valeur par défaut : false.

json

{ "debug": true }

Pour contrôler le niveau de log, utilisez la section logging :

json

{
    "logging": {
        "level": "debug"
    }
}

Niveaux disponibles : "debug", "info", "warn", "error", "production".

`branding` (object, optional)

Overlay de branding affiché sur la carte.

Champ	Type	Description
`enabled`	boolean	Activer l'overlay. Défaut `false`.
`text`	string	Texte affiché.
`position`	string	Position sur la carte (ex. `"bottom-left"`).

`security` (object, optional)

Champ	Type	Description
`httpsOnly`	boolean	Rejette les URLs `http:` (sauf images `data:`). Défaut `false`.

`data` (object, required)

Data loading configuration.

Field	Type	Default	Description
`activeProfile`	string	`"default"`	Profile name to load. Must match a directory in `profilesBasePath`
`profilesBasePath`	string	`"/profiles/"`	Base path to profiles directory (relative to HTML page or absolute URL)

Example:

json

{
    "data": {
        "activeProfile": "tourism",
        "profilesBasePath": "https://cdn.example.com/geoleaf-profiles/"
    }
}

`performance` (object, optional)

Performance optimization settings.

Champ	Type	Défaut	Description
`maxConcurrentLayers`	number	`10`	Nombre maximum de couches chargées en parallèle
`layerLoadDelay`	number	`200`	Délai en ms entre chaque chargement de couche
`fitBoundsOnThemeChange`	boolean	`false`	Recadrer la carte lors du changement de thème

3. profile.json - Profile Configuration

Location: profiles/{profile-name}/profile.json
Required: Yes (each profile must have this file)
Purpose: Define UI, basemaps, file paths, and default settings

Complete Structure

json

{
    "id": "my-profile",
    "label": "Mon Profil",
    "description": "Description du profil",
    "version": "1.3.0",
    "map": {
        "bounds": [
            [-56, -74],
            [-21, -53]
        ],
        "center": [-15, -62],
        "zoom": 6,
        "maxZoom": 18,
        "positionFixed": true
    },
    "Files": {
        "taxonomyFile": "taxonomy.json",
        "themesFile": "themes.json",
        "layersFile": "layers.json",
        "basemapsFile": "basemaps.json",
        "uiFile": "ui.json"
    },
    "performance": {
        "maxConcurrentLayers": 10,
        "layerLoadDelay": 200,
        "fitBoundsOnThemeChange": false
    },
    "clusteringConfig": {
        "enabled": true,
        "strategy": "by-layer",
        "maxClusterRadius": 80,
        "disableClusteringAtZoom": 12
    },
    "poiConfig": {
        "enabled": false
    }
}

Field Reference

`ui` (object, optional)

UI component configuration. Each component has the same structure:

Field	Type	Default	Description
`enabled`	boolean	`false`	Whether component is visible
`position`	string	varies	MapLibre GL JS control position: `"topleft"`, `"topright"`, `"bottomleft"`, `"bottomright"`
`collapsed`	boolean	`false`	Initial collapsed state (if applicable)
`title`	string	varies	Component title/label

Available components:

layerManager - Layer visibility controls
filterPanel - POI filtering UI
searchBar - Search input with autocomplete
cacheControls - Offline cache management buttons
themeSelector - Theme dropdown selector

`basemaps` (array, required)

Background map definitions.

Field	Type	Required	Description
`id`	string	✅	Unique basemap identifier
`name`	string	✅	Display name in UI
`url`	string	✅	Tile URL template with `{z}`, `{x}`, `{y}` placeholders
`attribution`	string	✅	Copyright/attribution HTML
`maxZoom`	number	❌	Maximum zoom level (1-20)
`minZoom`	number	❌	Minimum zoom level (1-20)
`default`	boolean	❌	Whether this is the default basemap
`tileSize`	number	❌	Tile size in pixels (default: 256)
`subdomains`	`array<string>`	❌	Subdomains for load balancing (default: `["a","b","c"]`)

Common tile providers:

json

{
    "basemaps": [
        {
            "id": "osm",
            "name": "OpenStreetMap",
            "url": "https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png",
            "attribution": "&copy; OpenStreetMap",
            "default": true
        },
        {
            "id": "topo",
            "name": "OpenTopoMap",
            "url": "https://{s}.tile.opentopomap.org/{z}/{x}/{y}.png",
            "attribution": "&copy; OpenTopoMap",
            "maxZoom": 17
        },
        {
            "id": "cartodb-light",
            "name": "CartoDB Light",
            "url": "https://{s}.basemaps.cartocdn.com/light_all/{z}/{x}/{y}.png",
            "attribution": "&copy; CartoDB"
        }
    ]
}

`Files` (object, required)

Paths to configuration and data files (relative to profile directory).

Champ	Type	Requis	Description
`taxonomyFile`	string	✅	Chemin vers `taxonomy.json`
`themesFile`	string	✅	Chemin vers `themes.json`
`layersFile`	string	❌	Chemin vers `layers.json` (index des couches)
`basemapsFile`	string	❌	Chemin vers `basemaps.json` (fonds de carte)
`uiFile`	string	❌	Chemin vers `ui.json` (composants UI)
`mappingFile`	string	❌	Chemin vers `mapping.json` (normalisation POI)

`Directory` (object, optional)

Path templates for layer-specific files. Use {layerId} placeholder.

Field	Type	Description
`styles`	string	Path template to styles directory
`data`	string	Path template to GeoJSON data file

Example:

json

{
    "Directory": {
        "styles": "layers/{layerId}/styles/",
        "data": "layers/{layerId}/data.geojson"
    }
}

Resolved for layer "cities":

Styles: profiles/tourism/layers/cities/styles/
Data: profiles/tourism/layers/cities/data.geojson

`poiAddConfig` (object, optional)

Configuration for POI creation form.

Field	Type	Default	Description
`enabled`	boolean	`true`	Allow users to add POIs
`categories`	`array<string>`	`[]`	Available categories in form
`defaultCategory`	string	first in array	Pre-selected category
`requiredFields`	`array<string>`	`["title","latlng"]`	Required form fields
`optionalFields`	`array<string>`	`[]`	Optional form fields
`allowCustomCategories`	boolean	`false`	Allow users to create new categories
`validation`	object	`{}`	Field validation rules

Validation rules:

json

{
    "validation": {
        "title": {
            "minLength": 3,
            "maxLength": 100,
            "pattern": "^[a-zA-Z0-9\\s-]+$"
        },
        "phone": {
            "pattern": "^\\+?[0-9\\s-]+$"
        },
        "website": {
            "pattern": "^https?://.*$"
        }
    }
}

`search` (object, optional)

Search configuration.

Field	Type	Default	Description
`enabled`	boolean	`true`	Enable search functionality
`sources`	`array<string>`	`["poi"]`	Data sources to search: `"poi"`, `"layers"`
`fields`	`array<string>`	`["title"]`	Fields to search in
`fuzzyMatch`	boolean	`false`	Enable fuzzy string matching
`fuzzyThreshold`	number	`0.6`	Fuzzy match threshold (0-1, lower = more strict)

`defaultSettings` (object, optional)

Initial map state.

json

{
    "defaultSettings": {
        "map": {
            "center": [48.8566, 2.3522],
            "zoom": 12,
            "minZoom": 5,
            "maxZoom": 18
        },
        "theme": "light",
        "basemap": "osm",
        "language": "fr"
    }
}

basemaps.json

Localisation : profiles/{profile-name}/basemaps.jsonRequis : Oui (depuis v2.0.0) Référencé par : profile.json → Files.basemapsFile

Définit les sources de tuiles disponibles. Chaque entrée est indexée par son ID.

json

{
    "basemaps": {
        "street": {
            "id": "street",
            "label": "OpenStreetMap",
            "type": "tile",
            "url": "https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png",
            "subdomains": "abc",
            "attribution": "&copy; OpenStreetMap contributors",
            "minZoom": 3,
            "maxZoom": 19,
            "tileSize": 256,
            "defaultBasemap": true,
            "offline": true
        },
        "maplibre_vector": {
            "id": "maplibre_vector",
            "label": "Carte vectorielle",
            "type": "maplibre",
            "style": "https://cdn.example.com/styles/vector.json",
            "fallbackUrl": "https://{s}.tile.openstreetmap.org/{z}/{x}/{y}.png",
            "defaultBasemap": false
        }
    }
}

Champ	Type	Description
`id`	string	Identifiant (miroir de la clé)
`label`	string	Libellé dans le sélecteur
`type`	`"tile"` \| `"maplibre"`	`"tile"` = raster, `"maplibre"` = vectoriel GL
`url`	string	Template URL raster avec `{s}`, `{z}`, `{x}`, `{y}`
`style`	string	URL du style MapLibre GL (type `"maplibre"` uniquement)
`fallbackUrl`	string	URL raster de secours si MapLibre GL indisponible
`tiles`	string[]	Tableau d'URLs explicites (remplace expansion `{s}`)
`subdomains`	string \| string[]	Sous-domaines de rotation
`attribution`	string	Attribution HTML
`tileSize`	number	Taille des tuiles en pixels. Défaut `256`.
`defaultBasemap`	boolean	Basemap active au démarrage
`offline`	boolean	Support du cache offline

ui.json

Localisation : profiles/{profile-name}/ui.jsonRequis : Oui (depuis v2.0.0) Référencé par : profile.json → Files.uiFile

Configure la visibilité et le comportement des composants UI. Ces paramètres étaient dans la section ui de profile.json avant v2.0.0 (toujours supporté en rétrocompat inline).

json

{
    "ui": {
        "theme": "light",
        "language": "fr",
        "showBaseLayerControls": false,
        "showLayerManager": true,
        "showFilterPanel": true,
        "showThemeSelector": true,
        "showLegend": false,
        "showTable": true,
        "showGeolocation": true,
        "showCoordinates": true,
        "showScale": true,
        "showCacheButton": false,
        "showAddPoi": false,
        "permalink": {
            "enabled": false,
            "mode": "hash",
            "fields": ["lat", "lng", "zoom", "layers"]
        }
    }
}

Champ	Type	Défaut	Description
`theme`	`"light"` \| `"dark"` \| `"auto"`	`"auto"`	Thème UI
`language`	string	`"fr"`	Code langue
`showBaseLayerControls`	boolean	`true`	Bouton sélecteur de fond de carte
`showLayerManager`	boolean	`true`	Panneau de gestion des couches
`showFilterPanel`	boolean	`true`	Panneau de filtres/recherche
`showThemeSelector`	boolean	`true`	Bouton sélection de thème
`showLegend`	boolean	`true`	Panneau légende
`showTable`	boolean	`true`	Panneau tableau de données
`showGeolocation`	boolean	`true`	Bouton géolocalisation GPS
`showCoordinates`	boolean	`true`	Affichage des coordonnées
`showScale`	boolean	`true`	Affichage de la barre d'échelle
`showCacheButton`	boolean	`false`	Bouton cache offline (@geoleaf-plugins/storage requis)
`showAddPoi`	boolean	`false`	Bouton ajout POI (@geoleaf-plugins/addpoi requis)
`permalink.enabled`	boolean	`false`	Synchronisation état dans l'URL
`permalink.mode`	`"hash"` \| `"query"` \| `"compact"`	`"hash"`	Stratégie d'encodage URL
`permalink.fields`	string[]	all fields	Champs d'état à sérialiser dans l'URL (ex: `["lat","lng","zoom","layers"]`)

Note : cache offline — showCacheButton: true pré-suppose l’installation du plugin commercial @geoleaf-plugins/storage (IndexedDB). Le core @geoleaf/core ne fournit qu’un détecteur de connectivité (offline-detector). Sans le plugin, le bouton ne s’affiche pas même si l’option est activée.

searchConfig (objet, optionnel)

Configure le panneau de filtres/recherche (affiché si ui.showFilterPanel: true). Dans ui.json depuis v2.0.0, cette clé remplace search de l'ancien profile.json inline.

json

{
    "searchConfig": {
        "title": "Filtrer",
        "radiusMin": 1,
        "radiusMax": 200,
        "radiusStep": 1,
        "radiusDefault": 10,
        "searchPlaceholder": "Rechercher un POI\u2026",
        "filters": [
            {
                "id": "searchText",
                "type": "search",
                "label": "Recherche textuelle",
                "placeholder": "Rechercher...",
                "searchFields": ["title", "properties.name", "description"]
            },
            {
                "id": "proximity",
                "type": "proximity",
                "label": "Recherche par proximit\u00e9",
                "buttonLabel": "Activer",
                "instructionText": "Cliquez sur la carte pour d\u00e9finir le point central"
            },
            {
                "id": "categories",
                "type": "tree",
                "label": "Cat\u00e9gories"
            },
            {
                "id": "tags",
                "type": "multiselect-tags",
                "label": "Tags",
                "field": "attributes.tags"
            }
        ],
        "actions": {
            "applyLabel": "Appliquer",
            "resetLabel": "R\u00e9initialiser"
        }
    }
}

Champ	Type	Description
`title`	string	Titre du panneau de filtres
`radiusMin`	number	Rayon minimum de la recherche par proximité (km)
`radiusMax`	number	Rayon maximum (km)
`radiusStep`	number	Pas du curseur de rayon (km)
`radiusDefault`	number	Rayon par défaut (km)
`searchPlaceholder`	string	Placeholder du champ de recherche textuelle
`filters`	array	Liste des filtres (voir types ci-dessous)
`actions.applyLabel`	string	Libellé du bouton "Appliquer"
`actions.resetLabel`	string	Libellé du bouton "Réinitialiser"

Types de filtre disponibles (filters[].type) :

Type	Description
`"search"`	Champ de recherche textuelle libre
`"proximity"`	Filtre géographique par rayon autour d'un point
`"tree"`	Arbre de sélection hiérarchique (catégories)
`"multiselect-tags"`	Sélection multiple par tags
`"select"`	Liste déroulante (valeur unique)
`"range"`	Curseur de plage numérique

tableConfig (objet, optionnel)

Configure le panneau tableau de données (module Table, lazy-loadé).

json

{
    "tableConfig": {
        "title": "Tableau",
        "enabled": true,
        "defaultVisible": false,
        "pageSize": 50,
        "maxRowsPerLayer": 10000,
        "enableExportButton": true,
        "virtualScrolling": true,
        "defaultHeight": "40%",
        "minHeight": "20%",
        "maxHeight": "60%",
        "resizable": true
    }
}

Champ	Type	Défaut	Description
`title`	string	—	Titre affiché dans l'en-tête du panneau
`enabled`	boolean	`true`	Active ou désactive le module Table
`defaultVisible`	boolean	`false`	Panneau visible au démarrage
`pageSize`	number	`50`	Nombre de lignes par page
`maxRowsPerLayer`	number	`10000`	Limite de lignes affichées par couche
`enableExportButton`	boolean	`true`	Affiche le bouton d'export CSV
`virtualScrolling`	boolean	`true`	Active le défilement virtuel (performances sur grands jeux)
`defaultHeight`	string	`"40%"`	Hauteur initiale du panneau (CSS)
`minHeight`	string	`"20%"`	Hauteur minimale lors du redimensionnement
`maxHeight`	string	`"60%"`	Hauteur maximale lors du redimensionnement
`resizable`	boolean	`true`	Permet à l'utilisateur de redimensionner le panneau

scaleConfig (objet, optionnel)

Configure l'affichage de l'échelle (activé si ui.showScale: true).

json

{
    "scaleConfig": {
        "scaleGraphic": true,
        "scaleNumeric": true,
        "scaleNumericEditable": true,
        "scaleNivel": true,
        "position": "bottomleft"
    }
}

Champ	Type	Défaut	Description
`scaleGraphic`	boolean	`true`	Affiche la barre d'échelle graphique
`scaleNumeric`	boolean	`true`	Affiche la valeur numérique de l'échelle
`scaleNumericEditable`	boolean	`true`	Permet la saisie manuelle d'une valeur d'échelle
`scaleNivel`	boolean	`true`	Affiche le niveau de zoom numérique
`position`	string	`"bottomleft"`	Position : `bottomleft`, `bottomright`, `topleft`, `topright`

4. taxonomy.json - Categories and Icons

Location: profiles/{profile-name}/taxonomy.json
Required: Yes
Purpose: Define hierarchical categories, subcategories, and icon mappings

Complete Structure

json

{
    "icons": {
        "spriteUrl": "icons/sprite_tourism.svg",
        "symbolPrefix": "tourism-poi-cat-",
        "defaultIcon": "activity-generic"
    },
    "defaults": {
        "icon": "activity-generic"
    },
    "categories": {
        "activites": {
            "label": "Activités",
            "icon": "activity-generic",
            "subcategories": {
                "randonnee": {
                    "label": "Randonnée",
                    "icon": "activity-mountain"
                },
                "velo": {
                    "label": "Vélo",
                    "icon": "activity-vehicle"
                }
            }
        },
        "hebergement": {
            "label": "Hébergements",
            "icon": "lodging-hotel",
            "subcategories": {
                "hotel": {
                    "label": "Hôtel",
                    "icon": "lodging-hotel"
                },
                "camping": {
                    "label": "Camping",
                    "icon": "lodging-camping"
                }
            }
        },
        "culture": {
            "label": "Culture",
            "icon": "culture-building",
            "subcategories": {
                "musee": {
                    "label": "Musée",
                    "icon": "culture-building"
                },
                "monument": {
                    "label": "Monument",
                    "icon": "culture-building"
                }
            }
        }
    }
}

Field Reference

`icons` (object, required)

Configuration du sprite SVG pour les icônes POI (format MapLibre GL JS).

Field	Type	Required	Description
`spriteUrl`	string	✅	Chemin vers le fichier sprite SVG (relatif au profil)
`symbolPrefix`	string	✅	Préfixe des noms de symboles dans le sprite (ex: `"tourism-poi-cat-"`)
`defaultIcon`	string	✅	Identifiant du symbole utilisé en fallback

`defaults` (object, optional)

Field	Type	Required	Description
`icon`	string	❌	Icône par défaut pour les POI sans catégorie

`categories` (object, required)

Définitions des catégories de premier niveau, sous forme d'objet clé→valeur. Les clés sont les identifiants de catégorie.

Field	Type	Required	Description
`label`	string	✅	Nom d'affichage de la catégorie
`icon`	string	✅	Identifiant du symbole dans le sprite
`subcategories`	object	❌	Sous-catégories (objet clé→valeur)

`subcategories` (object, optional)

Sous-catégories d'une catégorie parente, sous forme d'objet clé→valeur. Les clés sont les identifiants de sous-catégorie.

Field	Type	Required	Description
`label`	string	✅	Nom d'affichage de la sous-catégorie
`icon`	string	✅	Identifiant du symbole (peut différer du parent)

5. themes.json - Layer Visibility Presets

Location: profiles/{profile-name}/themes.json
Required: Yes
Purpose: Define named presets that control which layers are visible

Complete Structure

json

{
    "config": {
        "defautTheme": "defaut",
        "primaryThemes": {
            "enabled": true,
            "position": "top-map"
        },
        "secondaryThemes": {
            "enabled": true,
            "showNavigationButtons": true,
            "position": "top-layermanager"
        }
    },

    "themes": [
        {
            "id": "defaut",
            "label": "Vue par défaut",
            "description": "Vue standard avec les couches principales",
            "type": "primary",
            "icon": "🗺️",
            "layers": [
                { "id": "cities", "visible": true, "style": "defaut" },
                { "id": "climate", "visible": true, "style": "defaut" },
                { "id": "poi", "visible": true, "style": "defaut" }
            ]
        },
        {
            "id": "nature",
            "label": "Nature",
            "description": "Zones naturelles et protégées",
            "type": "primary",
            "icon": "🌿",
            "layers": [
                { "id": "cities", "visible": false, "style": "defaut" },
                { "id": "climate", "visible": false, "style": "defaut" },
                { "id": "poi", "visible": true, "style": "defaut" },
                { "id": "conservation-zones", "visible": true, "style": "defaut" }
            ]
        }
    ]
}

Field Reference

`config` (object, optional)

Theme system configuration.

Field	Type	Default	Description
`defautTheme`	string	first theme ID	Identifiant du thème actif au démarrage
`primaryThemes.enabled`	boolean	`true`	Afficher le sélecteur de thèmes primaires
`primaryThemes.position`	string	`"top-map"`	Position du contrôle dans l'UI
`secondaryThemes.enabled`	boolean	`false`	Activer les thèmes secondaires
`secondaryThemes.showNavigationButtons`	boolean	`false`	Afficher les boutons de navigation
`secondaryThemes.position`	string	`"top-layermanager"`	Position du contrôle secondaire

`themes` (array, required)

Theme definitions.

Field	Type	Required	Description
`id`	string	✅	Identifiant unique du thème
`label`	string	✅	Nom d'affichage du thème
`description`	string	❌	Description affichée dans l'UI
`type`	string	✅	`"primary"` (visible dans le sélecteur) ou `"secondary"` (programmatique)
`icon`	string	❌	Icône (emoji ou identifiant) pour le bouton thème
`layers`	array	✅	Tableau d'entrées `{id, visible, style}` définissant la visibilité de chaque couche

Format d'entrée dans layers :

Field	Type	Required	Description
`id`	string	✅	Identifiant de la couche (doit correspondre à l'id dans layers.json)
`visible`	boolean	✅	Visibilité initiale de la couche pour ce thème
`style`	string	❌	Variante de style à appliquer (défaut : `"defaut"`)

Theme types:

primary — Affiché dans le sélecteur de thèmes, accessible par l'utilisateur
secondary — Masqué dans l'UI, déclenché programmatiquement ou utilisé comme preset

Layer References

The layers object keys must match layer IDs defined in:

Layer directories: layers/{layerId}/
Layer config files: layers/{layerId}/config.json
GeoJSON layer IDs added via /* GeoLeaf.GeoJSON est interne - configurer via geojsonLayers dans geoleaf.config.json */

Example matching:

profiles/tourism/
  layers/
    climate/          ← ID: "climate"
    cities/           ← ID: "cities"
    monuments/        ← ID: "monuments"
  themes.json         ← References "climate", "cities", "monuments"

Dynamic Theme Creation

javascript

// Create custom theme programmatically
await GeoLeaf.Theme.create({
    id: "my-custom",
    name: "My Custom Theme",
    type: "secondary",
    layers: {
        poi: true,
        cities: true,
        climate: false,
    },
});

// Activate it
await GeoLeaf.Theme.setActive("my-custom");

6. layers.json - Layer Definitions

Location: profiles/{profile-name}/layers.json OR profiles/{profile-name}/layers/{layerId}/config.json
Required: No (layers can be defined inline or in separate files)
Purpose: Define GeoJSON layer properties, data sources, and default styles

Complete Structure

layers.json (fichier d'index) :

json

{
    "layers": [
        {
            "id": "cities",
            "configFile": "layers/cities/cities_config.json",
            "layerManagerId": "data-administration"
        },
        {
            "id": "climate",
            "configFile": "layers/climate/climate_config.json",
            "layerManagerId": "data-environment"
        }
    ]
}

Config individuelle (layers/{layerId}/{layerId}_config.json) :

json

{
    "id": "cities",
    "label": "Villes principales",
    "zIndex": 40,
    "geometry": "point",
    "data": {
        "directory": "data",
        "file": "cities.geojson"
    },
    "styles": {
        "directory": "styles",
        "default": "defaut.json",
        "available": [{ "id": "defaut", "label": "Défaut", "file": "defaut.json" }]
    },
    "table": { "enabled": false },
    "clustering": { "enabled": false }
}

Field Reference

`layers.json` — Fichier d'index

Field	Type	Required	Description
`id`	string	✅	Identifiant unique de la couche
`configFile`	string	✅	Chemin relatif vers la config individuelle de la couche
`layerManagerId`	string	❌	Identifiant du groupe dans le gestionnaire de couches

Config individuelle `{layerId}_config.json`

Field	Type	Required	Description
`id`	string	✅	Identifiant unique (doit correspondre au nom de répertoire)
`label`	string	✅	Nom d'affichage de la couche
`zIndex`	number	❌	Ordre de rendu (plus élevé = dessiné au-dessus)
`geometry`	string	✅	Type géométrique : `"point"`, `"polyline"`, `"polygon"`
`data.directory`	string	❌	Sous-répertoire des données (défaut : `"data"`)
`data.file`	string	✅	Fichier GeoJSON (relatif au répertoire de la couche)
`styles.directory`	string	❌	Sous-répertoire des styles (défaut : `"styles"`)
`styles.default`	string	✅	Nom du fichier de style par défaut
`styles.available`	array	❌	Variantes de style disponibles `{id, label, file}`
`table.enabled`	boolean	❌	Activer le panneau table de données
`clustering.enabled`	boolean	❌	Activer le clustering (couches de type `point`)

Multi-Layer Configuration File

To define all layers in one file (layers.json):

json

{
    "layers": [
        {
            "id": "climate",
            "name": "Climate Zones",
            "type": "polygon",
            "dataSource": "layers/climate/data.geojson",
            "defaultStyle": "default"
        },
        {
            "id": "cities",
            "name": "Cities",
            "type": "point",
            "dataSource": "layers/cities/data.geojson",
            "defaultStyle": "default"
        }
    ]
}

7. mapping.json - Data Normalization

Location: profiles/{profile-name}/mapping.json
Required: No
Purpose: Mapper les noms de champs externes vers la structure interne de GeoLeaf

Complete Structure

json

{
    "source": "description ou endpoint source (informatif)",
    "mapping": {
        "id": "external_id",
        "title": "name",
        "lat": "latitude",
        "lng": "longitude",
        "categoryId": "poi_type"
    }
}

Field Reference

Field	Type	Required	Description
`source`	string	❌	Description ou URL de la source de données (informatif)
`mapping`	object	✅	Table de correspondance : `{champGeoLeaf: "champExterne"}`

Champs mappables dans mapping :

Clé GeoLeaf	Description
`id`	Identifiant unique du POI
`title`	Nom du POI
`lat`	Latitude
`lng`	Longitude
`categoryId`	Identifiant de catégorie (correspond à taxonomy)

Pour le format complet du normaliseur et les options de transformation avancées, voir data-normalizer.md.

8. Style Files - Layer Styling

Location: profiles/{profile-name}/layers/{layerId}/styles/{styleId}.json
Required: At least one style (usually default.json) per layer
Purpose: Define visual appearance, labels, and legend for layer

Complete Structure

json

{
    "id": "default",
    "name": "Default Style",
    "name_fr": "Style par défaut",
    "description": "Standard visualization for climate zones",

    "label": {
        "enabled": true,
        "visibleByDefault": false,
        "field": "name",
        "format": "{name}",
        "minZoom": 10,
        "maxZoom": 18
    },

    "layerScale": {
        "minZoom": 5,
        "maxZoom": 18
    },

    "labelScale": {
        "minZoom": 10,
        "maxZoom": 18
    },

    "style": {
        "fillColor": "#3388ff",
        "fillOpacity": 0.2,
        "color": "#3388ff",
        "weight": 2,
        "opacity": 1,
        "dashArray": null
    },

    "styleRules": [
        {
            "condition": { "property": "climate_type", "equals": "Temperate" },
            "style": {
                "fillColor": "#66cc66",
                "color": "#44aa44"
            }
        },
        {
            "condition": { "property": "climate_type", "equals": "Mediterranean" },
            "style": {
                "fillColor": "#ff8833",
                "color": "#dd6611"
            }
        }
    ],

    "legend": {
        "enabled": true,
        "title": "Climate Types",
        "items": [
            {
                "label": "Temperate",
                "label_fr": "Tempéré",
                "color": "#66cc66",
                "icon": null
            },
            {
                "label": "Mediterranean",
                "label_fr": "Méditerranéen",
                "color": "#ff8833",
                "icon": null
            },
            {
                "label": "Continental",
                "label_fr": "Continental",
                "color": "#3388ff",
                "icon": null
            }
        ]
    }
}

Field Reference

`label` (object, required)

Label configuration for this style.

Field	Type	Required	Description
`enabled`	boolean	✅	Whether labels are supported for this style
`visibleByDefault`	boolean	✅	Initial label visibility when layer activated (depuis v2.0.0 — voir Labels documentation)
`field`	string	❌	GeoJSON property field to use for label text
`format`	string	❌	Label template with `{fieldName}` placeholders
`minZoom`	number	❌	Minimum zoom for label visibility (overrides `labelScale.minZoom`)
`maxZoom`	number	❌	Maximum zoom for label visibility

Note : visibleByDefault doit se trouver dans le fichier de style, pas dans la config de couche. Voir la documentation Labels.

Label format examples:

jsonc

{
  "format": "{name}"                           // Simple field
}
{
  "format": "{name} ({population})"            // Multiple fields
}
{
  "format": "{name} - {climate_type}"          // With separator
}

`layerScale` (object, optional)

Zoom range for layer visibility (features are rendered).

Field	Type	Default	Description
`minZoom`	number	1	Minimum zoom level
`maxZoom`	number	18	Maximum zoom level

`labelScale` (object, optional)

Zoom range for label visibility (typically narrower than layerScale to avoid clutter).

Field	Type	Default	Description
`minZoom`	number	10	Minimum zoom level for labels
`maxZoom`	number	18	Maximum zoom level for labels

Best practice: Set labelScale.minZoom higher than layerScale.minZoom:

jsonc

{
    "layerScale": { "minZoom": 5, "maxZoom": 18 }, // Layer visible from zoom 5
    "labelScale": { "minZoom": 10, "maxZoom": 18 }, // Labels visible from zoom 10
}

`style` (object, required)

MapLibre GL JS paint/layout options for styling features.

For polygons/multipolygons:

Field	Type	Description
`fillColor`	string	Fill color (hex, rgb, or named color)
`fillOpacity`	number	Fill opacity (0-1)
`color`	string	Border color
`weight`	number	Border width in pixels
`opacity`	number	Border opacity (0-1)
`dashArray`	string	Dash pattern (e.g., `"5, 10"`) or `null` for solid

For lines:

Field	Type	Description
`color`	string	Line color
`weight`	number	Line width in pixels
`opacity`	number	Line opacity (0-1)
`dashArray`	string	Dash pattern or `null`
`lineCap`	string	Line cap style: `"butt"`, `"round"`, `"square"`
`lineJoin`	string	Line join style: `"miter"`, `"round"`, `"bevel"`

For points (markers):

Markers use taxonomy icon configuration, not style settings.

`styleRules` (array, optional)

Conditional styling based on feature properties.

Rule structure:

jsonc

{
    "condition": {
        "property": "field_name",
        "operator": "equals", // equals, contains, gt, gte, lt, lte, in
        "value": "comparison_value",
    },
    "style": {
        // Override style properties
    },
}

Operators:

equals - Exact match
contains - String contains substring
gt / gte - Greater than / greater than or equal
lt / lte - Less than / less than or equal
in - Value in array

Examples:

json

{
    "styleRules": [
        {
            "condition": { "property": "population", "operator": "gt", "value": 1000000 },
            "style": { "fillColor": "#ff0000", "weight": 3 }
        },
        {
            "condition": { "property": "type", "operator": "in", "value": ["city", "town"] },
            "style": { "fillColor": "#ffff00" }
        }
    ]
}

`legend` (object, optional)

Legend configuration for this style.

Field	Type	Required	Description
`enabled`	boolean	✅	Whether to display legend
`title`	string	❌	Legend title
`title_fr`	string	❌	Localized title
`items`	array	✅	Legend item definitions

Legend item:

jsonc

{
    "label": "Item Label",
    "label_fr": "Libellé",
    "color": "#ff0000",
    "icon": null, // Or icon identifier
    "description": "Optional description",
}

9. POI Configuration

Location: profiles/{profile-name}/data/poi.json
Required: No (POIs can be added programmatically)
Purpose: Initial POI data loaded on map initialization

Structure

json

{
    "version": "1.0",
    "lastUpdated": "2026-01-20",
    "count": 3,

    "pois": [
        {
            "id": "eiffel-tower",
            "latlng": [48.8584, 2.2945],
            "title": "Eiffel Tower",
            "description": "Iconic iron lattice tower",
            "category": "monument",
            "subcategory": "landmark",
            "properties": {
                "address": "Champ de Mars, 5 Avenue Anatole France, 75007 Paris",
                "phone": "+33 892 70 12 39",
                "website": "https://www.toureiffel.paris",
                "openingHours": "9:00-23:45",
                "ticketPrice": "26.80 EUR",
                "accessibility": "partial",
                "rating": 4.6
            }
        },
        {
            "id": "louvre",
            "latlng": [48.8606, 2.3376],
            "title": "Louvre Museum",
            "description": "World's largest art museum",
            "category": "museum",
            "subcategory": "art",
            "properties": {
                "address": "Rue de Rivoli, 75001 Paris",
                "phone": "+33 1 40 20 50 50",
                "website": "https://www.louvre.fr",
                "openingHours": "9:00-18:00",
                "closedDays": ["Tuesday"],
                "ticketPrice": "17 EUR",
                "accessibility": "full"
            }
        },
        {
            "id": "notre-dame",
            "latlng": [48.853, 2.3499],
            "title": "Notre-Dame Cathedral",
            "description": "Medieval Catholic cathedral (under restoration)",
            "category": "monument",
            "subcategory": "religious",
            "properties": {
                "address": "6 Parvis Notre-Dame, 75004 Paris",
                "website": "https://www.notredamedeparis.fr",
                "status": "restoration",
                "reopening": "2024-12-08"
            }
        }
    ]
}

Field Reference

Root fields:

Field	Type	Description
`version`	string	Data version
`lastUpdated`	string	ISO date of last update
`count`	number	Total POI count
`pois`	array	Array of POI objects

POI object (required fields):

Field	Type	Description
`id`	string	Unique POI identifier
`latlng`	[number, number]	Coordinates `[latitude, longitude]`
`title`	string	POI name/title
`category`	string	Category ID (must match taxonomy)

POI object (optional fields):

Field	Type	Description
`description`	string	POI description
`subcategory`	string	Subcategory ID (must match taxonomy)
`properties`	object	Custom properties (address, phone, etc.)

10. Route Configuration

Location: profiles/{profile-name}/data/routes.json
Required: No
Purpose: Define routes (paths, itineraries) with waypoints

Structure

json

{
    "version": "1.0",
    "routes": [
        {
            "id": "paris-tour",
            "name": "Paris Highlights Tour",
            "name_fr": "Tour des points forts de Paris",
            "description": "2-hour walking tour of major attractions",
            "type": "walking",
            "distance": 5200,
            "duration": 7200,
            "difficulty": "easy",

            "waypoints": [
                {
                    "id": "eiffel-tower",
                    "order": 1,
                    "latlng": [48.8584, 2.2945],
                    "title": "Eiffel Tower",
                    "stopDuration": 1800
                },
                {
                    "id": "trocadero",
                    "order": 2,
                    "latlng": [48.862, 2.2876],
                    "title": "Trocadéro",
                    "stopDuration": 600
                },
                {
                    "id": "arc-triomphe",
                    "order": 3,
                    "latlng": [48.8738, 2.295],
                    "title": "Arc de Triomphe",
                    "stopDuration": 900
                }
            ],

            "path": [
                [48.8584, 2.2945],
                [48.86, 2.29],
                [48.862, 2.2876],
                [48.865, 2.29],
                [48.8738, 2.295]
            ],

            "style": {
                "color": "#e74c3c",
                "weight": 4,
                "opacity": 0.7,
                "dashArray": null
            },

            "properties": {
                "accessibility": "wheelchair-friendly",
                "highlights": ["Eiffel Tower", "Arc de Triomphe"],
                "bestTime": "morning"
            }
        }
    ]
}

Field Reference

Route object:

Field	Type	Required	Description
`id`	string	✅	Unique route identifier
`name`	string	✅	Route name
`type`	string	✅	Route type: `"walking"`, `"cycling"`, `"driving"`, `"transit"`
`distance`	number	❌	Total distance in meters
`duration`	number	❌	Estimated duration in seconds
`difficulty`	string	❌	Difficulty: `"easy"`, `"moderate"`, `"hard"`
`waypoints`	array	✅	Array of waypoint objects
`path`	array	✅	Array of `[lat, lng]` coordinates defining the route path
`style`	object	❌	MapLibre GL JS paint options for line/polyline styling
`properties`	object	❌	Custom properties

Waypoint object:

Field	Type	Required	Description
`id`	string	✅	Waypoint identifier (can reference POI ID)
`order`	number	✅	Stop order (1, 2, 3, ...)
`latlng`	[number, number]	✅	Coordinates
`title`	string	✅	Waypoint name
`stopDuration`	number	❌	Recommended stop duration in seconds

11. POI Add Feature — showAddPoi vs poiAddConfig.enabled

The POI-add feature is governed by two complementary parameters that operate at different levels.

Difference in Usage

Parameter	Location in profile.json	Role
`ui.showAddPoi`	`ui` section	Controls button visibility in the toolbar
`poiAddConfig.enabled`	`poiAddConfig` section	Enables/disables the AddPOI plugin behavior

Priority Order

ui.showAddPoi is evaluated first. If false, the AddPOI control is not created and poiAddConfig is never read.

javascript

// control-poi-add.ts
if (!config?.ui?.showAddPoi) return; // primary gate — control not created

// poiAddConfig is only read after the gate passes
const defaultPosition = config?.poiAddConfig?.defaultPosition || "placement-mode";

JSON Examples

Show the add-POI button (minimum config):

json

{
    "ui": {
        "showAddPoi": true
    }
}

Full configuration with plugin behavior:

json

{
    "ui": {
        "showAddPoi": true
    },
    "poiAddConfig": {
        "enabled": true,
        "defaultPosition": "placement-mode"
    }
}

Disable the button without changing plugin config:

json

{
    "ui": {
        "showAddPoi": false
    }
}

Recommendation

To show or hide the button: use ui.showAddPoi only.
To configure behavior: use poiAddConfig (defaultPosition, enabled).
If ui.showAddPoi is false, poiAddConfig.enabled has no effect — the control is never built.
The AddPOI plugin must be loaded for the feature to be operational. If showAddPoi: true but the plugin is not loaded, a warning is emitted: ⚠️ Config has showAddPoi=true but AddPOI plugin is not loaded.

See also: Identifiant utilisateur pour l'édition POI

12. geocodingConfig — Address Search

Localisation : Clé geocodingConfig dans geoleaf.config.json ou dans profile.json
Requis : Non (désactivé par défaut) **Façade publique :**GeoLeaf.Geocoding`

Configure le contrôle de recherche d’adresse intégré à la carte. Basé sur un widget de saisie avec suggestions en temps réel. 4 providers supportés — aucune clé API requise pour les providers open-data.

Référence des champs

Champ	Type	Défaut	Description
`enabled`	boolean	`false`	Active le contrôle de recherche sur la carte
`provider`	string	`"addok"`	Provider de géocodage (voir tableau ci-dessous)
`position`	string	`"top-right"`	Position du contrôle : `"top-left"`, `"top-right"`, `"bottom-left"`, `"bottom-right"`
`placeholder`	string	`"Rechercher une adresse…"`	Texte du champ de saisie
`minChars`	number	`3`	Nombre min. de caractères avant déclenchement de la recherche
`resultLimit`	number	`5`	Nombre max. de résultats affichés
`debounceMs`	number	`300`	Délai en ms entre la saisie et le déclenchement de la requête
`flyToZoom`	number	`15`	Niveau de zoom lors du survol vers un résultat ponctuel

Providers disponibles

Clé `provider`	Service	Zone	Clé API
`"addok"`	BAN — Base Adresse Nationale	France	Aucune
`"nominatim"`	OpenStreetMap Nominatim	Mondial	Aucune
`"photon"`	Photon par Komoot	Mondial	Aucune
URL HTTPS custom	Endpoint retournant GeoJSON FC	Au choix	Selon l’API

Provider custom : passez une URL HTTPS complète comme valeur de provider. L’URL doit accepter un paramètre q={query} et retourner un GeoJSON FeatureCollection.

Exemples de configuration

Activer avec le provider par défaut (France) :

json

{
    "geocodingConfig": {
        "enabled": true
    }
}

Recherche mondiale via Nominatim :

json

{
    "geocodingConfig": {
        "enabled": true,
        "provider": "nominatim",
        "position": "top-left",
        "placeholder": "Search an address…",
        "resultLimit": 8,
        "flyToZoom": 14
    }
}

Provider custom :

json

{
    "geocodingConfig": {
        "enabled": true,
        "provider": "https://api.my-service.com/geocode",
        "minChars": 2,
        "resultLimit": 10
    }
}

Événement émis

Lors de la sélection d’un résultat par l’utilisateur :

document.addEventListener("geoleaf:geocoding:result", (e) => {
    const { label, lat, lng, bounds } = e.detail;
    console.log(`Adresse sélectionnée : ${label} (${lat}, ${lng})`);
});
// ou via GeoLeaf.Events:
GeoLeaf.Events.on("geoleaf:geocoding:result", (e) => {
    console.log(e.detail.label);
});

Note : La recherche Nominatim est soumise aux conditions d’utilisation d’OSM. Pour un usage intensif, hébergez votre propre instance ou utilisez un provider commercial.

Configuration Best Practices

1. File Organization

profiles/
  tourism/
    profile.json              ← Main config (single source of truth)
    taxonomy.json             ← Categories
    themes.json               ← Themes
    mapping.json              ← Data mapping (optional)
    layers/
      climate/
        config.json           ← Layer config
        data.geojson          ← GeoJSON data
        styles/
          default.json        ← Default style
          detailed.json       ← Alternative style
      cities/
        ... (same structure)
    data/
      poi.json                ← Initial POIs
      routes.json             ← Routes

2. Validation

Always validate JSON before deploying (use JSONLint, VS Code, or npm run validate)
Use JSON Schema validation for strict type checking
Test with debug mode enabled: { "debug": { "enabled": true } }

3. Performance

Minimize file sizes - Use minified GeoJSON, compress with gzip
Lazy load layers - Don't load all layers on init, load on-demand
Use CDN for static files when possible
Enable clustering for 100+ POIs

4. Maintainability

Use descriptive IDs - "hotel-eiffel" not "h1"
Add descriptions - Future maintainers will thank you
Version your configs - Include version field in all files
Document custom properties - Add comments in separate README

5. Internationalization

Use name_{lang} pattern for translations
Support fallback - If name_fr missing, use name
Separate UI strings from config when possible

Migration Notes

Structure historique des labels (v2.0.0)

⚠️ BREAKING CHANGE: Label visibleByDefault moved from layer config to style files.

Ancienne structure (label dans la config couche) :

jsonc

// layers/cities/config.json
{
    "id": "cities",
    "labels": {
        "enabled": true,
        "visibleByDefault": false,
    },
}

Structure actuelle (label dans le fichier de style) :

jsonc

// layers/cities/styles/default.json
{
  "id": "default",
  "label": {
    "enabled": true,
    "visibleByDefault": false  ← Moved here
  }
}

See Labels documentation for full migration instructions.

Identifiant utilisateur pour l'édition POI

GeoLeaf.AddPOI attribue les créations/modifications au champ modifiedBy, résolu dans cet ordre de priorité :

Champ de config user.id dans le profil JSON actif
sessionStorage clé gl-user-id (positionné par votre application hôte)
Fallback anonyme anonymous-<timestamp> (cohérent sur la session)

Exemple d'intégration :

html

<script>
    sessionStorage.setItem("gl-user-id", currentUser.email);
</script>
<script type="module" src="dist/geoleaf.esm.js"></script>

Ou via le profil JSON :

json

{
    "user": {
        "id": "admin@example.com"
    }
}

Next Steps

Profiles Guide - Create custom profiles
User Guide - Learn how to use configured features
API Reference - Programmatic configuration APIs
Schema Documentation - JSON Schema definitions

Questions? Check FAQ or open an issue

GeoLeaf Configuration Guide ​

Table of Contents ​

1. Overview ​

Configuration File Hierarchy ​

Load Order ​

Configuration Principles ​

2. geoleaf.config.json - Main Configuration ​

Complete Structure ​

Field Reference ​

debug (boolean, optional) ​

branding (object, optional) ​

security (object, optional) ​

data (object, required) ​

performance (object, optional) ​

3. profile.json - Profile Configuration ​

Complete Structure ​

Field Reference ​

ui (object, optional) ​

basemaps (array, required) ​

Files (object, required) ​

Directory (object, optional) ​

poiAddConfig (object, optional) ​

search (object, optional) ​

defaultSettings (object, optional) ​

basemaps.json ​

ui.json ​

searchConfig (objet, optionnel) ​

tableConfig (objet, optionnel) ​

scaleConfig (objet, optionnel) ​

4. taxonomy.json - Categories and Icons ​

Complete Structure ​

Field Reference ​

icons (object, required) ​

defaults (object, optional) ​

categories (object, required) ​

subcategories (object, optional) ​

5. themes.json - Layer Visibility Presets ​

Complete Structure ​

Field Reference ​

config (object, optional) ​

themes (array, required) ​

Layer References ​

Dynamic Theme Creation ​

6. layers.json - Layer Definitions ​

Complete Structure ​

Field Reference ​

layers.json — Fichier d'index ​

Config individuelle {layerId}_config.json ​

Multi-Layer Configuration File ​

7. mapping.json - Data Normalization ​

Complete Structure ​

Field Reference ​

8. Style Files - Layer Styling ​

Complete Structure ​

Field Reference ​

label (object, required) ​

layerScale (object, optional) ​

labelScale (object, optional) ​

style (object, required) ​

styleRules (array, optional) ​

legend (object, optional) ​

9. POI Configuration ​

Structure ​

Field Reference ​

10. Route Configuration ​

Structure ​

Field Reference ​

11. POI Add Feature — showAddPoi vs poiAddConfig.enabled ​

Difference in Usage ​

Priority Order ​

JSON Examples ​

Recommendation ​

12. geocodingConfig — Address Search ​

Référence des champs ​

Providers disponibles ​

Exemples de configuration ​

Événement émis ​

Configuration Best Practices ​

1. File Organization ​

2. Validation ​

GeoLeaf Configuration Guide

Table of Contents

1. Overview

Configuration File Hierarchy

Load Order

Configuration Principles

2. geoleaf.config.json - Main Configuration

Complete Structure

Field Reference

`debug` (boolean, optional)

`branding` (object, optional)

`security` (object, optional)

`data` (object, required)

`performance` (object, optional)

3. profile.json - Profile Configuration

Complete Structure

Field Reference

`ui` (object, optional)

`basemaps` (array, required)

`Files` (object, required)

`Directory` (object, optional)

`poiAddConfig` (object, optional)

`search` (object, optional)

`defaultSettings` (object, optional)

basemaps.json

ui.json

searchConfig (objet, optionnel)

tableConfig (objet, optionnel)

scaleConfig (objet, optionnel)

4. taxonomy.json - Categories and Icons

Complete Structure

Field Reference

`icons` (object, required)

`defaults` (object, optional)

`categories` (object, required)

`subcategories` (object, optional)

5. themes.json - Layer Visibility Presets

Complete Structure

Field Reference

`config` (object, optional)

`themes` (array, required)

Layer References

Dynamic Theme Creation

6. layers.json - Layer Definitions

Complete Structure

Field Reference

`layers.json` — Fichier d'index

Config individuelle `{layerId}_config.json`

Multi-Layer Configuration File

7. mapping.json - Data Normalization

Complete Structure

Field Reference

8. Style Files - Layer Styling

Complete Structure

Field Reference

`label` (object, required)

`layerScale` (object, optional)

`labelScale` (object, optional)

`style` (object, required)

`styleRules` (array, optional)

`legend` (object, optional)

9. POI Configuration

Structure

Field Reference

10. Route Configuration

Structure

Field Reference

11. POI Add Feature — showAddPoi vs poiAddConfig.enabled

Difference in Usage

Priority Order

JSON Examples

Recommendation

12. geocodingConfig — Address Search

Référence des champs

Providers disponibles

Exemples de configuration

Événement émis

Configuration Best Practices

1. File Organization

2. Validation