Deals with most of the functionality under the Data menu
Creating Lane Segments from Lane Configurations
|
Fritz Jooste Administrator Posts: 81
10/18/2015
|
Fritz JoosteAdministrator Posts: 81
If you want to create a FWP that is LANE SPECIFIC - that is, one that has different segments for different lanes - then you need to first define all the Lane Segments on your network. This data is kept in tblLanes and can be directly managed via the Lane Segments page under the Data menu. However, in many instances, you may not know exactly where each lane segment starts and ends.
Typically, network managers may only know where the lane configuration changes from one type to another but knowing the location of each Lane Segment is more complex.
If you do not already know what the difference is between Lane Configuration Types and Lane Segments, please look at this post before you read further.
JunoViewer Web can help you create a set of Lane Segments if you know where the Lane Configuration Types change on each segment. In this case, you can prepare an Excel template with the Lane Configuration data, and then use the Lane Configs page (under the Data menu) to automatically check and process this data to create a set of Lane Segments for you. The image below shows what this process involves.
(please look at the list of notices below the figure)
It is vital that the definition of lane segments is accurate and consistent with your network definition. If your lane segments cover only a part of the true network area, then you may grossly underestimate the budget required to maintain the network.
For this reason, the Lane Config import process as shown in the image above has certain built-in checks to ensure that any inconsistencies are highlighted and corrected.
Thus, very often, during the import of Lane Configuration data, you will be notified of errors in your data, these errors can be of the following types:
§ If your lane config data has start and end locations that fall outside of the limits of the Section Definitions (as defined on the Sections page under the Data menu), you will be notified of the error, and this must be corrected before the process will run.
§ If your lane config data has too many changes in lane configuration, e.g. every 10 meters a new lane configuration type is declared, this indicates an inconsistency that needs to be corrected.
§ If your lane config data declares a Lane Configuration Type that is not found in the Lane Configuration Types table (tblLaneConfigTypes), then you will be notified of the error and this needs to be corrected before the process can proceed.
§ If your lane config data has gaps between rows on a section, then this will need to be corrected first. For example, if your laneConfig template shows that from 0m to 2000m you have a Type 1 road, and then from 2200m to 2900m you have a Type 2 road, then as you can see there is an inconsistency (gap) between 2000m and 2200m. Any such errors in your configuration data will be picked up and reported, and then needs to be fixed before you can proceed.
edited by Rashel on 10/1/2022
|
|
|
0
link
|
