What the colours mean
Each prism on a map is coloured by what its measurements show, compared with the tolerance levels set for the site:
Green (Within): movement is inside tolerance.
Amber (Warning): movement has reached the warning level.
Red (Exceeded): movement has exceeded tolerance.
Blue (Planned): the prism is planned but not yet in use.
Grey (Damaged): the prism has been marked as damaged.
Colours are calculated automatically
Prism colours are recalculated every time a map is opened, using the same calculation as the trend report, so the map and the report always agree. You don't need to refresh or re-run anything. When a new processing run is complete, or the site's tolerance levels change, the updated colours appear the next time anyone opens the map.
Maps show the prism's current status
A prism's status belongs to the physical prism, not to an individual map or capture. Every map shows the prism's current status, including maps from earlier captures. For example, if a prism moved into Warning in the latest processing run, it will show amber on older maps too.
Setting a status manually
You can set a status for a point from the point inspector. How it behaves depends on whether the point has been measured:
Planned and Damaged always apply. These describe the physical state of the prism, so they override the measured colour.
For measured prisms, the measurement decides. Setting a prism that is red or amber back to "Active" won't turn it green. The dropdown only shows statuses the point can actually have. Choosing the one that matches its measurement clears your manual flag and returns the prism to its measured colour.
Manual status is shown when nothing has measured the point. This applies to GCPs, which are never measured, and to prisms before their first processing run.
Status is the same on every map
Because status belongs to the physical prism, a change you make on one map appears on every map showing that prism. Adding a prism set to a new map brings the prisms in with their existing statuses and colours. Nothing is reset.
Coordinates are the exception
Each map keeps the coordinates from the survey version it was built with. If a newer survey version is added later, points won't move on maps that already exist.