Pavement Marking Line Styles

What is the current guidance on the line styles associated with the Pavement Marking Feature Definitions?  For instance, drawing a line with the Feature Definition PM_P_Center Line Double Solid, 6" places a line with a line style of Center Line Double Solid.  This line style is a double line with essentially no thickness to either line. Is this the correct line style for plan production?  There is also a line style Center Line Double Solid, 6".  This also displays the double line; however, both lines appear to be a filled shape 6” thick.  Is this only intended for exhibits, or should we be overriding the line style for plan production?

  • The assumption here is that you're referring to ODOT standards...this was a defect in the standards a few releases ago.  It has been updated in the current standards so new files wont have the issue, and I believe JD made a tool in the ODOT toobar to fix existing dgn files seeing the problem.  

  • Brian,

    I am referring to ODOT's Connect OpenRoads Designer OHDOT standards.  Please clarify the intent of the two sets of line styles.  For plan production, should we be using the pavement marking line styles that show the striping as a line, or as a filled shape?  For what it is worth, ODOT's sample plan sheet SP 1314-3 dated 10/2006, shows the striping as filled shapes.

    I do see a tool OHDOT Fix Line Styles.  Is the tool to which you are referring?  Using this tool seems to leave linestyles as lines.  Is this the expected behavior?

  • Yes, there are two sets of linestyles...the with physical widths are not intended for plan production, they are used for renders, models and passing to LumenRT.  For plan production, you should be using the symbology that comes with ByLevel settings (like we did in SS4).

    There was a problem some time last year inside the OHDOT seed files that caused the linestyles to not display properly.  It sounds like you are using a drawing that was created with a bad seed file.  If your standards were updated recently, you should be able to create a new file, ensuring to pull the new seed file from the c:\connect\....\standards folder (not the existing project standards folder), and get good line styles/weights.  If you still have the issue, I would bet your seeds are still old.

    If you cannot get the Fix Linestyles button to fix your file, but you can create a new working file (as described above), just create a new file, then ref your bad file to it and merge the contents in.  The lines should come in to the active file settings. Once you confirm that, you can overwrite the old file and continue on.

    Good luck.

  • So in SS4 a couple years ago we introduced the custom linestyles that show the actual physical width. the main reason we did this was for LumenRT. When you create a 3D model and export it to LumenRT linestyles that don't have a width will not show up. So we added these custom line styles.

    We left the old ones (non width ones) for plan production as many uses do not like the way the new width ones look on a plan sheet  especially at larger scales.

    the feature definitions are set up to show the non width linestyles for the plan view and the width ones for the 3d view.

    the issue Brian is talking about is we had some linestyles get messed up in our cadd standards. in CONNECT we changed the way we use custom linestyles. In SS4 the custom linestyles were read directly from a rsc file. whn tis I done the linestyles are not copied into the file so if you open that file without the cadd standards then it wont show the custom linestyles. So in CONNECT we changed to importing the custom line styles into a dgnlib.Now as the custom linestyles are used they are copied into the file so now the dgn can be opened without the cadd standards and the linestyles will still display.

    but this change does come at a cost. Since the linestyle is copied into the file when you use it. If we (OHDOT) change/fix a linestyle that a file already used then that file will not see the update. Which is the problem Brian is talking about. The lnestyles that we had a problem with were with the pavement markings. So I put a button in the ribbon called fix OHDOT linestyles (its the far right button). Open the problem file and hit that button and it will fix up the bad linestyles for you. but again that's only if you used a bad pavement marking linestyle in that file before we pushed the fixed it the last fix we pushed out for custom linestyles was on February 7th 2020. As always you can see or revision doc here, ftp://ftp.dot.state.oh.us/pub/CADD/CADDSync/OHDOT/Standards/OHDOT_RunningUpdates.pdf

    hopefully that clarifies everything if not let me know.  

    Answer Verified By: SScheid