<aside> 💡 A checkpoint marks the entrance to a counting zone within the shopping center and counts the number of people entering this area.
</aside>
When a checkpoint is selected on the map, a side panel appears. Below is a diagram illustrating this panel, along with a table providing descriptions of its various elements:
| Panel section | Key | Example | Description |
|---|---|---|---|
| Title section | Checkpoint name | CT1-41-1 | Name assigned to the checkpoint. |
| Wall Icon | Checkpoint icon | Icon indicating the wall type (checkpoint). | |
| Floor | Floor 1 | Floor on which the checkpoint is located. | |
| Backlinks | 1 | Number of map elements linked to the checkpoint. | |
| Database ID | Wall ID | 30318 | Unique identifier of the checkpoint in the Digeiz database. |
| External ID | ext30318 | Identifier of the checkpoint in the customer’s database. | |
| Billing | Coverage | Covered | Indicates whether the checkpoint is included in the project scope. Checkpoints outside the initial quote may be marked as optional. |
| Licence | No | Indicates whether a license has been issued for the checkpoint. | |
| Data Delivery | No | Indicates whether the checkpoint is currently generating data accessible via the API. | |
| Priority | Low | Calibration priority assigned by the Digeiz Operations team for counting stations linked to the checkpoint. | |
| Counting Stations | CT1-41-1 | In | Counting stations connected to the checkpoint. |
| Visibility | Obstructive | No | Indicates whether the checkpoint is obstructive or permeable with respect to the visibility of surrounding elements. |
| Comment | No comment | - | Free-text field for operational notes added by the Digeiz Operations team. |