The general properties of the route are shown in the header under the navigation panel. They include:

-

-

* ** Type ** \\ The type of the route is defined by the type of transport. Unlike stops, a route can be assigned only one type. To change the route type, click on the route and select the required option from the drop-down list.

-

* ** Number ** \\ The number is an //​obligatory//​ parameter of the route. It should contain from 1 to 4 characters (digits and letters). An unlimited quantity of routes with the same number can exist in the system. Click on the route number at any time to edit it.

-

* ** Name ** \\ The name of the route is not editable. It is generated automatically based on the names of the initial and final stops of the route.

-

* ** Description ** \\ Optional property. The description can be set, for example, to distinguish a temporary route from a permanent one; a route in the forward direction — from a route in the opposite direction, etc. The description can be added or changed at any time.

-

-

On the right side of the route window header, there is a switch to turn the route on or off and the //Delete// button. On the left there is a button to return to the list of routes (left arrow).

-

-

{{: nimbus: route_properties.png?​ Nolink}}

-

-

===== Stops =====

-

-

The //Stops// tab contains the list of stops from which the route is formed, as well as the way between them (shown on the map). Initially, this route is mapped automatically,​ but it can be edited manually. It may be necessary, for example, to make changes related to the repair of the road. Editing is available on 4 the most detailed map scales. The principle of working with the line is similar to that used when creating [[nimbus/​user/​stops/​stopscreation#​creating_stops_manually| polygon stops]].

-

-

{{: nimbus: route_stops.png?​ nolink}}

-

-

The parts of the way corrected manually are used for the future creation of routed. Each segment from one stop to another is stored separately. ​

-

-

The order of the stops in the list can be changed by dragging them to the required position. In such a case, the route line on the map changes accordingly. When you hover over the stop, a button in the form of an ellipsis appears in the list, which allows you to call an additional menu of actions:

-

-

* **Replace** \\ This action allows you to replace one stop with another (of the same type) or specify a new stop instead of the deleted one. When you replace a stop, a schedule line is kept.

-

* **Insert** \\ A new stop is inserted after the current one. The same as with the replacement,​ the choice can only be made from the stops compliant with the type of route.

-

* **Remove** \\ The removal of a stop from the route is accompanied by the deletion of the entire line of its schedules. Therefore, if you plan to add another stop instead of the removed one, it is better to replace it. Removing a stop from the route //does not// result in removing it from the system.

-

-

These actions are also available in the pop-up menu that appears after clicking a stop on the map. ​

-

-

{{ :​nimbus:​stops_actions.png?​nolink }}

-

-

===== Schedules =====

-

-

On the second tab of the route properties, you can create a table of its schedules. The table contains all possible departures for the route with the time of the stops visits. Based on the timetables, rides are created automatically on scheduled days.

-

-

A separate schedule is a list that contains information about the time of each visit of the route. One route can have from one to several hundred schedules depending on how often it travels, and how many variations of schedules it has on different days of the week and seasons.

-

-

{{: nimbus: routes_schedules.png?​ nolink}}

-

-

If no schedules have been created for the route, click on the //Create first schedule// button. The first schedule is created automatically according to the following principles:

-

-

* The time of visiting the initial point is set to //00:00//. The time of visiting the rest points is calculated automatically according to the routing (by Gurtam Maps).

-

* If the data for the automatic routing is absent or invalid, a step of one minute is used to calculate the time of visiting each following point. ​

-

* If the request is not completed within 10 seconds, a step of one minute is used to calculate the time of visiting each following point. ​

-

* If as a result of calculation the route takes more than 48 hours, a step of one minute is used to calculate the time of visiting each following point. ​

-

-

It is possible to change the time of visiting stops by entering the necessary numerical value from the keyboard or use the //up// and //down// keys.

-

-

When creating schedules, the following **rules** apply:

-

-

* The time of visiting the initial and final stops of the route is required.

-

* The time of visiting the intermediate stops is not obligatory. You can clear it using the button of the same name in the list of options which opens after clicking the button in the form of three dots (the button is shown if the cursor is put in the field with the time of visiting the point). However, it is recommended to specify the time for each stop, because only in this case you can later track the delay and hurry at them.

-

* The time of each following stop should be later than the time of the previous visit.

-

* There cannot be two schedules with the same start time in the framework of one [[nimbus/​user/​schemes/​schemes|operation pattern]].

-

-

If schedules contain invalid data, the //Save// button for routes becomes inactive, the //​Schedules//​ tab is marked with a red asterisk, and all the invalid cells are highlighted in red.

-

-

The system gives a schedule an opportunity to go beyond 24 hours. In other words, the route can physically begin on one day, and end on the following. The time of the visit with the transition to the following day should be marked as running past midnight: for the first and last points this is regulated by the button with a crescent moon ({{: nimbus: icons: midnight.png?​ nolink}}); for the rest, you should select //Past midnight// in the menu under the elision marks. Visually, such cells have a pale purple highlight in the background. ​

-

-

Since often the schedules of one route differ from each other only by the start time, and the intervals between the stops remain unchanged, next schedules can be created based on the already existing ones. To do it, click the Add schedule button. The system will offer to create a copy of the existing schedule (if there are several, select the required one from the drop-down list) with a shift of 10 minutes. If necessary, edit the start time of the new schedule and click Apply. If you create two or more copies of a schedule sequentially using the same delta (shift) between them, this delta is suggested to determine the start time of the future schedules instead of 10 minutes by default. If the schedule should not be a copy of another, select the dash in the Copy from drop-down list. Next schedules can be created in the same way without closing the window for adding them.

-

-

{{ :​nimbus:​schedule_copy.png?​nolink }}

-

-

After you finish working with the schedule list, save the route.

-

-

When creating or editing a schedule, you can specify an operation pattern and a unit for it.

-

-

The operation pattern defines the days on which the schedule should be active. For example, one schedule should work only on weekends, the other — only in summer, etc. If no operation pattern is specified for a schedule, then it is executed daily, without restrictions.

-

-

In schedule properties, the pattern can only be specified. Creating and editing of operation patterns is conducted in a [[nimbus/​user/​schemes/​schemes##​operation_patterns_creation|separate interface]].

-

-

A schedule can be filtered by its affiliation to a particular operation pattern. To do it, use the drop-down filter above the stops list. The unit should be indicated only if it constantly goes on rides on this schedule. In this case, there is no need for the dispatcher to assign a unit manually each time — when the ride is activated, it will be assigned automatically.

-

-

In the table, the schedules are arranged in chronological order by the start time. One column corresponds to one schedule. Navigation using the keyboard is available for the table of schedules: //Tab// — move to the right horizontally,​ //​Shift//​+//​Tab//​ — move to the left horizontally,​ //Enter// — move down vertically, //​Shift//​+//​Enter//​ — move up vertically. The cursor is automatically put in the area of changing minutes.

-

-

Editing the time for visiting stops is done in the table itself. Additional properties of the schedules (operation patterns, units) are edited in the drop-down menu, which you can access by clicking on the {{:​nimbus:​icons:​edit.png?​nolink}} pencil above each of them. The button for deleting the schedule {{:​nimbus:​icons:​delete.png?​nolink}} is also located here.

-

-

-

-

-

=====Units=====

-

-

On the third tab of route properties, you can associate units with a route (by marking the required ones in the list). In this case, they will be primarily offered for rides and schedules assignment.

-

-

{{:​nimbus:​route_units.png?​nolink}}

-

-

Click //Select all/Reset selection// in the upper-right corner of the dialog to perform a corresponding action on all the elements at once.

-

-

While selecting units, the following key combinations can be also used:

-

-

* //Ctrl// + left click — select or deselect all the units. A click with the //Ctrl// key pressed on any unmarked unit selects all the units on the list; one on any marked one removes the selection. ​

-

* //Shift// + left click — select or deselect a range of units. The first click with the //Shift// key pressed marks the beginning of the range, the second one — its end. If the first click is made on an unmarked unit, all the units in the range are selected. If it's made on a marked one — viceversa.

-

-

It is not obligatory to associate units with the route. If no unit is associated with the route, then all available ones are considered equally suitable for executing rides on this route.

-

-

If you have a large vehicle fleet, the search for the unit may become more complicated and the chances of error may increase. To simplify and speed up the work of the dispatcher and reduce the risks, the list of units that usually follow a certain route can be specified directly in the route. More information about using this function is described [[nimbus/​user/​rides/​actions| below]].