A Mappia map is defined by a query: plain JavaScript that lists the layers to show, the tools its users get and the arithmetic that runs over the pixels. Start where your question is:
New to Mappia? Start with the tutorial → Ten short steps with a live map in each: layers and their names, sources and WMS servers, calculated maps, groups, globals, the ExtjsUtils helpers, saving and sharing, and MappiaIO. Build Tools Sliders, pickers, charts, drawing, split views - every tool a map can offer, each with a working example and its picture. See Examples Real maps built with Mappia, opened live - the features used at full scale. Learn Reference How the platform reads a query: evaluation, execution, the layer model, widgets, embedding, pitfalls. Look up API Every property, widget parameter and helper function, generated from the platform source.
Start here
- Publish your maps. Upload data and styles from QGIS - the publishing tutorial.
- Write your first query. It can be one line - the tutorial walks you through it, step by step; how a query is evaluated has the rules.
- Add tools. Pick one from Tools, copy its example, then adapt it - the widget markup language explains the rules.
- Calculate new maps. Combine published maps pixel by pixel - the execution model.
- Embed it. Put the map in your own site and talk to it - embedding a map. Stuck? Pitfalls, and properties that do nothing.
For scripts and AI assistants
The whole documentation is also published as plain text: llms.txt (the index), llms-full.txt (every reference chapter in one file), api.json (the generated API), and each chapter as markdown under /assets/reference/.