OpenRoads Point Controls

just a few thoughts how to make software better and more user friendly.

When adding point control to corridor new entiers are added in Corridor Object to point control list. There few two issues tha affect productivity badly and one can be critical to any project.

For point control reference objects we use corridor points, external terrain model features and additional civil geometry graphic stored in separate dgn file. Basicly most of point control features are stored in separate dgn files and are attached to active corridor as a reference (Microstation Reference Manager).

1) When an object used as point control is deleted the entry from Point Contol list in Corridor Object is deleted as well. User has no feedback that one or a few point controls are missing. They are vanished from the list with no notice. It happend that a reference path for a file that stored point contol lines was lost in reference manger. This way we lost half of point controls we created in our corridor. It happens that user acidentaly deatache external reference file or an objet used as point contorl is deleted. A lot of rework is needed to set all point controls over again. 

I am sure that when object used for controling points is missing the point control entry in Corridor Object shouldn't be deleted. We should get some kind of feedback. EG with red colour that sth is missing. It works that way in Inroads SS2.

That was the critical one.

2) At first glance it looks that Point Controls use object name to contol location of template point along corridor. In Corridor Object there is a list of linear objects that can be used as point controls in a given corridor. All featurized and named object that are in active file or in reference files are listed there. And here is the problem. Objects are listed by names. When there are few objects with the same name available for corridor (let ssay you have object EOP in reference A.DGNand object EOP in reference B.DGN) there is only one instance of EOP available on the list. Moreover you can not switch objects used for controling points by making graphical edits (no locate button to change linear object used as point contol feature) - graphical edits will not work here...

I think that linear objects used for contolling points shoul be listed sth like this: filename:featurename. Again it worked that way in Inroads SS2. It was easy to switch objects used as point controls even when this object was moced from one DTM or ALG to another. When object was deleted, the Point Control entry was still there and the collor of missing object's name was changed to red.

In SS3 it only looks that software use object name for contolin points. It uses element ID. so once object is deleted and than recreated with the same name given you will loose you point control definition. I do not bleive it is good approach. SS2 was superior to SS3 here.

3)No feedback on station conflict when one template point is controlled by several linear objects. 

Adam

Parents
  • I've had a check of the point control issue you describe above. I created a quick corridor and referenced in a file with two elements and set them as horizontal point controls.

    I changed the name of the reference file and opened the corridor file again, the elements aren't available as the reference file hasn't loaded. I checked the Points Controls and they are still listed however the Plan Element names are blank. Is this what is happening for you, is this what you would like to have highlighted in red?

    I opened References and updated the file path for the missing reference in the list. After it loaded I checked the points controls list again and the Plan Element names are showing up again.

    I didn't need to re-setup the Point Controls I just had to update the reference path to get it to show correctly again.

    As a second test I opened the horizontal point control file and changed the element names. When I opened the corridor file and checked the Point Controls the Plan Element names are updated so I'd be inclined to agree with you that it is based on the object name of the element.

    The reason for this is most likely to allow the use of native cad elements to be used for point controls, when using a native CAD element the Plan Element name is blank as it isn't a civil feature. If I change a native cad elements to a civil feature it will keep the Point Control and populate the assigned Feature name in the Plan Element name box.

    I've had a check with features with the same name in 2 references and as you have said I see just one Element of that name in the drop down list. Creating a new Point control and selecting the required element manually works OK to get round this. I'll log a Enhancement request to better distinguish the elements in different reference files.



  • Jason,

    when Reference Manager lost path to my dgn file (highlighted in red) where I keep elements used for controlling points, Point Controls entries disapeared from Corridor Object. It not about blank element fields. I had no Point controls listed at all.

    And there is no option to change element used to controll point by selecting new element from graphic. That would be needed if CAD graphic (with no names and features is used as point control elment)

    Best,

    Adam


    OpenRoads Designer 2023   |  OpenRail Designer 2023

                 

  • Jason,

    I have seen this same behavior Adam describes as well. In your test example, try processing the corridor after the reference file name is changed. I have seen many instances when an element is removed from a file, but it is still listed in the corridor objects list until the corridor is processed.

    I would also like to add to Adams list of enhancements this functionality:

    If point controls/corridor references were name specific it would save a large amount of rework when having to redefine point control geometry. For example, I have a complex element named EOP_R. For some reason I need to drop this complex element to make edits to the alignment. I then complex together the revised geometry and name it EOP_R. Even though the name is exactly the same the corridor that references this geometry does not recognize it.

    Marc
  • Have tried processing the corridor but the Point Controls entries stay listed in the Corridor Objects and the corridor reverts to it's standard template. When I update the reference file path and process the corridor again the Point Controls entries take effect again. Can you let me know the version number you have installed, it may be behaving differently in the release I am using.

    When dropping and recreating the complex element it is creating a new object ID for the element so that's why it is loosing the connection to the point control. An override function to have Feature Name take preference over object ID would be a good way to do this as it would keep the function working as it does now but for users that require it they could select Feature Name control override.



  • I am using Inroads version 722.

    Try to not rename the reference file but rather delete the geometry being used as the point control and see if you get a different result.

    I agree that an override or something would work. Anything to enable the functionality to use the geometry name rather than ID would be an extremely beneficial enhancement.
  • When I delete the element from the reference file I now see that the point control for that element has been removed from the list as you have described. I agree that it should stay in the list and give the user the opportunity to select an alternative element for that point control.



  • The Enhancements and Defects for the issues in this post have been logged as below.

    Enhancement 149616:Corridor Objects>Point Control: Highlight Conflicts

    Enhancement 157483:Corridor Objects>Point Control>Plan Element List

    Enhancement 158799:Corridor Objects>Point Control>Plan Element Name Override

    Defect 158791:Corridor Objects - Point Control Deleted from List



    Answer Verified By: Adam Wieczorek 

Reply Children
No Data