On the Paths section, you can create the Paths of your building. These paths are used by Situm to compute the shortest route from point A to point B. You can see more info here.
Paths are a set of nodes and links, where the links represent that there is a passable path between two nodes. In order to insert a new node, just click on the map wherever you want to create it. To create a link between two nodes, just click in one of them, and then, click on the other one.
Creating floor transitions
You can easily link the paths of two different floors. First, select one of the nodes (e.g. floor 0 in the left image) and then select the target link floor (e.g. floor 1). After that, click on the node of the target floor and the link will be created. It will be represented by the icon: 
By clicking on the
icon, you will be able to see the floor to which it connects.
Creating these transitions is important in order to:
- Providing wayfinding & indications when a route involves several floors.
- Speed up floor changes if you are using any of the floor change accelerators.
Marking paths as "not accessible" for people with reduced mobility
You can also configure a links as “not accessible” (e.g. for people in wheelchairs) by clicking on the link and unchecking the “accessible” option. The link line will become discontinuous.
Marking a path as one-way only
You can also indicate that a link is one-way only. This is useful, por example, if you want to indicate that users can only go up using a certain escalator, but not going down (or viceversa). This can be done by selecting the link and then changing the “Direction” (bottom-left red square). The direction of the link will be shown with an arrow.
Free attributes
Situm allows to associate each link with personalised attributes or tags. To this extent, click on the link and associate it with as many tags as you desire.
These can be used to filter the kind of routes that Situm will provide. For example, in the following figure, one might ask for "private routes only", "routes that avoid private tags only", "only routes that contain the private and priority tags", etc.
