Corridor - Add Point Codes to Code Set Style
Last updated: 2024-07-08
Overview
The command reads all the point codes in a selected corridor or assembly and compares them to the assigned code set style contents. The following steps occur if a point code is not found in the assigned code set style:
- It will look at all the possible point code matches in the assigned code set style and pick the code that matches the most characters of the missing point code. The new custom code must start with a code set code in order for that code set code to be considered a match. The styles associated with the closest matching point code are added to the missing point code.
- If there are no apparent matches, the missing point code may be added to the code set style and assigned the default styles.
Usage
WisDOT Design tab > Design panel > Corridor dropdown > Add Point Codes to Code Set Style
The tool can also be accessed from the command line: DOTAddPointCodesToCodeSet
- Select Corridor or Assembly:
- Create copy of Code Set Style and assign [Y N]:
- Yes: A copy of the currently assigned code set style will be saved in the drawing and assigned to the assembly or corridor that was selected.
- No: The currently assigned code set style will be modified. If the code set style if a referenced style, the modification is only for the current session of the drawing.
- Add codes with no apparent match in code set style? [Y N]:
- Yes: Point codes without a match are added to the code set style and assigned the default styles.
- No: Point codes without a match are not added to the code set style.
- Enter new style name < Code Set Style Name >:
- If the user has chosen to create a copy of the assigned code set style:
- The default is to add a counter (example: 1) at the end of the currently assigned code set style.
A new name for the copy of the code set style may also be typed in the command line.
- If the user has chosen to create a copy of the assigned code set style:
Info: The command will only find the codes that are actually being used in the subassembly branch of logic. For example, if a lane subassembly has custom codes for an extended base, but the base never gets extended, those codes are not added.