The UX metaphore behind CRS4 MapWall is the sailor's chart table, where the map is on the desk and you move your tools, such as a compass or a protractor, over it.

The core of CRS4 MapWall is a predefined (though customizable) interaction flow: when the user clicks on a geographic feature on the map, a popup, called watcher, by default opens up. While open, the watcher remains strictly linked to its feature.
When using CRS4 MapWall you have to write code only for getting data from your source backend and for filling the watchers content.

The framework facilitates this task by exposing API and helpers for simplifying complex but common operations. Useful UI widgets will ease the building process of your map-based dashboards.

The CRS4 MapWall's first idea was to build a tool to support developers involved in the Cagliari2020 project at CRS4

Geo Monitoring

Using watchers you can keep track and query the state of the objects on the map, such as sensors, roads, IoT things, parkings etc.

Big Touch Displays

CRS4 MapWall performs best on large touch surfaces, like those used in control rooms. Draggable watchers and a toolbar that follows the user make really easy to organize your dashboard

Maps Comparison

CRS4 MapWall's Multi-Map feature is a powerful tool for comparing different georeferenced scenarios

Watchers

Popups monitoring features on the map. Customizable layout and content. By using dedicated API methods you can hide unwatched features or update the content of open watchers

Multi Map

Multiple maps on the same dashboard, with independent or shared interaction

Fully configurable

Most CRS4 Mapwall behaviours are configurable through a JSON file

Layers and Features by id

API methods for direct access to map features and layers using their id or name

Openlayers full support

CRS4 MapWall always grants access to Openlayers Map object and functions