|
thomas.potgieter@lonrix.com Administrator Posts: 28
9/29/2022
|
thomas.potgieter@lonrix.comAdministrator Posts: 28
The following paragraphs provide key definitions which need to be understood by users of the system.
While some of these definitions may seem obvious, it is important to understand their meaning in the context of the software application, and therefore detailed explanations of all key concepts are provided.
The figure below illustrates some of the concepts explained in the paragraphs that follow:
Network - A network is defined as a logical group of network sections. Any logical group of sections can be defined as a network. For example, a network can consist of all roads within a suburb, a province, or a specific freeway. In JunoViewer Web, networks cannot share the same Forward Works Programme (FWP) and therefore networks typically have different treatment options, budgets, etc.
Section - As shown in the figure above, a section is defined as part of a network with a specific ID and a unique set of linear locations in each lane. In road networks, sections typically contain several lanes. All data measured and stored on that section needs to be referenced by the section ID. The ID of each section should be unique across all networks. Thus, you cannot have a section with ID = 13 in network 1 and in network 2.
JunoViewer Web does not automatically assign IDs to network sections. When you import your network section definitions, you need to provide an ID for each section, and this ID must be unique over all sections, regardless of which network the sections belong to. The ability to use user-defined IDs for road sections makes it easy to incorporate section definitions and data that was previously held in another Asset Management System or database. Click here to see how you can/should manage Section Definitions in JunoViewer Web.
Segment - A segment is defined as part of a section – typically defined for analysis or modelling purposes. As shown in the figure above, a segment could be the leftmost lane of a specific section, thereby forming part of a section. In some cases, a segment will cover the entire section.
Treatment Length - Within JunoViewer Web, a treatment length and a segment are the same, as defined above and in the figure above. The main difference between a segment and a treatment length lies in the use context. When a segment is discussed or analysed in the context of a FWP or in terms of a treatment planned for that segment, we will often refer to the segment as a Treatment Length. Thus segments which are defined within a FWP with assigned treatments, will be referred to as treatment lengths.
Modelling Segment - A modelling segment and a segment are the same, as defined above and in the figure above. As with a treatment length, the main difference between a segment and a modelling segment lies in the use context. When a segment is discussed or analysed in the context of a deterioration or forecast model, then the segment is generally referred to as a modelling segment.
Segment Group - As shown in the figure above, a segment group is defined as a grouping of segments to form a reporting or analysis unit on the network. For example, you can define a Segment Group which comprises all segments that received a rehabilitation in year 2013, and then label that group of segments as “Treated Segments 2013”. In network view, you can then conveniently obtain statistics or reports using data that fall within those segments.
Lane Segments - A “lane segment” is defined as a segment of a road that is specific to a single lane. In Figure 1 above, segments 1 and 3 are lane segments, while segment 2 is not a lane segment. Lane segments are optional information about a network, and are often used for:
- Modelling purposes, where treatments may vary depending on the lane codes.
- Plotting purposes, e.g. to show where a lane starts and ends.
You can define your lanes in any order in JunoViewer. One often used, but not mandatory, for the definition of lanes, is as shown below. Other configurations, for example having lanes "L1" and "R1" closest to the median, can also be used, or you can “simple code” your lanes with names like "slow", "middle1", "middle2", "fast" etc.
The key element to note from this figure is that lanes L1 and R1 are the slow lanes carrying heavy traffic. Note that the direction of traffic as shown in this figure can be reversed and this will not affect the features in JunoViewer Web. For example, in this figure, lanes L1 and L2 are lanes where the traffic is in the increasing reference direction, whereas R1 and R2 are in a decreasing reference direction. If this convention is reversed, as in countries where traffic drive on the right side of the road, then this will still be handled elegantly in JunoViewer Web.
Edited by Thomas on 9/29/2022
edited by Rashel on 9/29/2022
|