We need a simplified, step by step explanation of how to setup some basic elements that make up the DGNLIB's needed to implement Open Roads.
Please don't tell me to look at the sample workspaces. I manage a network with about 7 or 8 different client standards that function in Ss2. I have enough work keeping those running and updated when the client releases new versions.
Reverse engineering dgnlibs in yet another set of standards, for the sole purpose of understanding what I need to do to implement Ss4 in my current standards would be more work that writing a PHD thesis.
I don't even know what items would need to be in a basic list of the things that are required for Open Roads.
I've watched a number of the learning paths videos, but when I try to implement one or two of these in a live product, by the time I get to my third dialog box and fifth step, I am lost and things that I thought I understood reveal to me my hubris as fields I want to select are grayed out, or drop down lists are displaying some items but not others and I cannot find any difference between them in all of their separate properties.
The starting point of any project is an existing ground surface. I can create one and I can even fumble through its display. But what is needed is a step by step manual that shows the minimum needed to have a surface with all of its settings already created from the various locations in DGNLIB's or linked native or wherever it comes from so that once created, it is easily assigned a display and if referenced into another file, the methodology of using an override display that is also available from the same sources that that were setup in its containing DGN.
Next, a similar tome on Survey, explaining linked native, new coding vs old coding, survey features - linear (open and closed) & point. Feature types, basically, all the things that the native software did with a cross reference to the Open Roads equivalents.
The same is needed for Geometry, and non-corridor modeling .What is the minimum settings needed to accomplish what we have been doing since the feature based DTM was introduced in InRoads as well as the Site Modeler.
I am working on a live project in a PW managed workspace as an end user - I have very limited access to modify the settings and am having serious productivity issues. The PW administrator is very open to my input, but I can make suggestions when I clearly do not have a deep enough grasp of the task at hand.
The problem with videos is its really hard to work with them at the same time you try it live. Especially when the process involves five or more steps in their own videos. The learning path videos interface is severely flawed when one tries to move around between the multiple videos as it is constantly updating screens making it hard to get beck to the same path and one of its prior or following video.
A pdf is much better and can be printed if that is how you work best.
I hope someone has some simple suggestions that can be shared.