OpenRoads Designer
When creating sheets from named boundaries the software automatically creates a drawing model then a sheet model from the named boundary. This workflow seems to work well and is pretty straight forward. The problem I have ran into is the fact the drawing model references are rotated and sometimes moved. So the world coordinates in the drawing model don't match the design model. If I where to identify a coordinate value or bearing without using the "OpenRoads label tools" they would be incorrect. Where do we label or annotate world coordinates and bearings? I would prefer to do it in the drawing model. Is there a setting or workflow to keep the drawing model references scale 1:1 , xy=0,0 and rotation 0 degrees?
when were labeling with plan labeler in ORD I can not place the text at different angles. the text is always horizontal 0 or 360. is there a way to place the text at different angles like the GeoPak Labeler?
Garry
Mary,
I agree. Creating and modifying sheets should be a simple process. This is what AutoCAD has going for it. This new sheet creation process with OpenRoads Designer (and Connect Edition) is complicated and confusing. As a user I still have many questions. Which model do I annotate or identify coordinate data in? If I move the named boundary will the drawing model references move and rotate? Why can't live nested references in the same file update without a forced reload? In my opinion, Bentley needs to use their software on a real world project and hash some of this out. I actually love where they are going with the civil design software, but they haven't quite figured out the plan production aspect yet.
Solution: All we need for a plan view is a named boundary that when moved, scaled or rotated, updates the sheet view. And a drawing model that is 1:1 with references that don't move or rotate. Also, live nested references that update automatically when contained in the same file.
That is my two cents worth.
And the issue goes beyond annotation. We have engineers here who like to get into drawings and get the information for themselves. While these are very smart, capable individuals, they are not trained in CAD and some of them aren't even trained in the civil software. We can tell them all we want to NOT use certain files, but invariably they will, then come to us demanding to know why the information in said drawing isn't "right".
MaryB
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Holly,
Thanks for filing the defect. In response to your annotation suggestion. Respectfully, I have to add that you really can’t annotate lines, line stings and shapes using element fields. The software doesn’t let the user identify which vertice or segment to target.
Also, annotating the coordinates and bearings in the design model is a workflow I would like to avoid. But it may be the only viable option. Half the annotation would end up in a drawing model and half in a design model. What do you do when you have separate sheet files?
For now I may just avoid using drawing models all together for plan views. It just seems risky to advise users to annotate coordinates and bearings in a drawing model that may not have references in the correct location.
Hopefully this can get fixed.
Thanks for your time.
Thank you Holly,
I really like new tools for annotations.If only we could manage text favs somehow - I know development is working on such capability. And you are 100% right that it is good to have annotation updated with design changes.Also annotations groups speed up drafting works... providing you have them well developed. You have no idea how warm welcome XS annotations tools are in my team - with points filtering - we were missing that in S3/4.
Drawing models are often annotated by cad drafters who are not really familiar with Civil Tools - that would be another reason to have drawing models 1:1 with design model. And we still can use labels with text favs and cels, or annotation gorups, when drawing model is kept in design model scale and orientation.
again thanks for loging defect,..and for understanding!
Best,
Adam
OpenRoads Designer 2022 (10.12) | OpenRail Designer 2022 (10.12)