Use of SS4 Feature Definitions in ORD

Hi all,

As a lot of us have quite a number of established feature definitions in our SS4 workspaces, can these feature definitions be used or migrated to ORD without recreating the whole lot?

Understandably native styles will be gone but we already have all ours pointing to element templates in preparation for ORD.

Cheers,

Mark

Parents
  • Yes Mark you can upgrade your dgnlib containing FD's and element templates. There is obviously a manual aspect to this since we added capability for ORD that you will want to take advantage of. I would suggest you copy one of our workspaces/ rename etc (there is / will be a learn video to help on best practice here), then with FD's in place you can open to automatically update your template librabires as the path is now retained and helps to provides unique name.

    Regards
    Ian



    Answer Verified By: Mark Shamoun 

  • Hi Ian,

    I have upgraded my feature definitions and unfortunately the feature definitions do not seem to be retained in any template in the template library (ie. blank feature defs for both points and components).

    Is there a step im missing?

    All features seem to have upgraded successfully with element templates, feature symbologies and levels all present and defined in the features dgnlib. I see the features I want to use under Mesh or Linear depending on the element in the Template Editor but it looks like it is not matching the old feature to the new one.

    cheers,

    Mark

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

  • I should probably mention that the original component feature definitions got upgraded to Terrain features and I had to export to excel, recategorise them to Mesh and import them back in.

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

Reply Children
  • Mark, the way the upgrade for Surface Features works is as follows:

    1. If in SELECTseries 4, the Surface Feature uses an Element Template where the Element Template has enabled properties for a Terrain Model Display, then the Surface Feature will get converted to an OpenRoads Terrain Model Feature Definition.

    2. If in SELECTseries 4, the Surface Feature uses an Element Template where the Element Template does not enable properties for a Terrain Model Display, then the Surface Feature will get converted to an OpenRoads Mesh Feature Definition.

    Thanks,
    Chuck


    This is a test

  • Thanks Chuck,

    Unfortunately I don't see any terrain model display options in the original SS4 data (see below) - could it be anything else?

    SS4 Feature Definition:

    SS4 Element Template:



    ORD Feature Definition:



    ORD Element Template:


    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

  • Mark, please email me directly your SS4 dgnlib(s) so I can take a look.

    Thanks,
    Chuck

    chuck.lawson@bentley.com


    This is a test

  • Sent

    Regards,

    Mark


    OpenRoads Designer 2023  |  Microstation 2023.2  |  ProjectWise 2023

  • Here are my findings...

    1. In the file
    "C:\ProgramData\Bentley\OpenRoads Designer CONNECT 10.00.00\Configuration\WorkSpaces\Arcadis-NSW.cfg"
    The line number 35 should read like this:

    CIVIL_WORKSPACE_TEMPLATE_LIBRARY_NAME = W2B-Templates-B3.itl

    …as this is to only set the name and no path is needed.

    2. Your Feature Definitions Mesh settings do not include the pointer to their feature symbologies. You missed this column in your spreadsheet. This is why your templates are not showing correct.

    3. The slow down of the template editor is because you are including a DGNLib of Subsurface Utilities that has not been converted. It is seeing features in this file and trying to resolve but it can’t.
    "C:\ProgramData\Bentley\OpenRoads Designer CONNECT 10.00.00\Configuration\WorkSpaces\Arcadis-NSW\Standards\Dgnlib\Feature Definitions\RMS Subsurface Utilities Feature Definitions.dgnlib"

    If you rename that files extension to something like *.old, then the problem goes away. This DGNLib will need to be updated.

    4. In the file "C:\ProgramData\Bentley\OpenRoads Designer CONNECT 10.00.00\Configuration\WorkSpaces\Arcadis-NSW.cfg" line # 99 is wrong. It should read like this:

    MS_DGNLIBLIST > $(_USTN_WORKSPACESTANDARDS)Dgnlib/Feature Definitions/*.dgnlib

    5. When importing the symbologies and features, make sure to always start with a new dgnlib if you are going to do the bulk editing.


    This is a test