Maps

A dashboard can show a map. Joripo draws maps itself, as a picture of its own: there are no map tiles and no map library, so no map service learns where anyone is, and maps work offline.

Points

Each record's GPS answer as a point over a boundary layer's outlines, coloured by a field you choose, or counted in squares of 1, 5 or 10 km with heat steps and their counts. A phone that had no fix (0 0) and a blank answer are counted apart rather than drawn in the sea.

Areas

An indicator per value of an area field (for example the share of households reached in each union), shaded on a boundary layer and matched by code or by name, with each area's name and value written on it, a legend of the steps, a table of the numbers, and value bands or the target as colours. Areas the data names but the layer does not have are listed.

Boundary layers

Upload the geography under Dashboards › Map layers: a GeoJSON file in degrees, up to 8 MB, 2,000 areas and 200,000 points, named by the property your data uses for the area. A layer stays while a map draws it, and travels with a copy or a template of the dashboard.

What a map does not show

• No background map. There are no roads or rivers: the boundary layer you upload is the geography.
• No protected GPS for those without identity access. A viewer without identity access gets no map of a GPS answer the workspace's Privacy page protects. An external client the dashboard is shared with sees the map as the team does, with its boundary shapes; a public link shows no GPS points at all.

For a single GPS question in a form, the maps and placement-map appearances show an OpenStreetMap map on the phone; that is separate from dashboard maps and needs a connection.