Does anyone know why the "Create terrain by text interpolation" tool in some cases badly generates point elevation?
I put the recording and a link to the file
Link to file:
https://1drv.ms/u/s!AoKLTsHic9oZiSrbGFuQ008cAoqt?e=5JwyNI
↧
OpenSite Designer - Create terrain by text interpolation - wrong elevation
↧
RWD Format
Hi,
We have a Leica TS15 total station that offers a Bentley RWD format to export the fieldbooks data.
What is this format ?
How to import it into OpenRoads Designer ?
Thanks,
Bernard.
↧
↧
Alpha Codes
How do I create a comprehensive list of Alpha Codes? I am transitioning to OpenRoads. The Alpha Codes that my surveyor currently uses in the field does not match the Alpha Codes set in my DOT delivered workspace. I would like to create a list with the description and corresponding Alpha Code such as this: EXISTING FL OF CONCRETE PIPE...………. EXFLRCP. Is there a way to do this?
↧
OpenRoads - Place Point is placing same cell differently
So I am using the Geometry - Place Point command in OpenRoads with a Feature Definition of REQD_P_RWRM and the cell that is placed is supposed to look like the one on the left. In some of my DGN files the point is placed with the cell looking like the one on the Right which is incorrect. I have looked at the properties to ensure the cell that is placed is the same cell and they are. I have also deleted the feature symbology and feature definition out of the active DGN file and re-stored the point so it would have to look at the DGNLIB's. Once thing I've noticed about the cell is there appears to be a 3D element to it and if I change the model from default to default-3D the cell looks correct. Not sure if this means anything or not. I've attached 2 DGN files hoping someone could look at this and expain to me what is going on.
communities.bentley.com/.../1234567MAIN.dgncommunities.bentley.com/.../GDOT-2d-ORD-Working-File.dgn
↧
[ORD 2019 R2 Refresh) Survey Feature Definitions vs Point & Linears Feature Definitions
Our Workspace originated from InRoads. When Open Roads was introduced as an extension to InRoads, there was a bifurcation of Survey Features vs non-survey Feature Definitions, where you had to link your XIN twice - once for regular features and a second time to get survey features. This was true even if you had one common XIN that was used for survey and design. At that time, you could chose to use element templates or "native style" for symbology for anything you wanted, except for Survey. It required many settings that only an XIN file could provide.
All of that is gone with ORD, but we still have a bifurcation and I am trying to determine if this is still required. In my DGNLIB, under Linear and Point Feature Definitions, we have a Survey category and under it, is a complete series of sub-categories. Additionally, under our Survey Feature Definitions, is a nearly identical series of sub-categories. Eventually, all of these point to the same Feature Symbologies.
Under certain workflows in the past, we would export some survey points and figures to an ALG, but in those days, one Feature Style could contain Geometry and Survey Features.
As we migrate to ORD if I wanted to transfer Survey points and figures to Civil Geometry points and figures, I am not sure how this would be best accomplished, but equally pressing is the question, "Do we need to keep the linear and point feature definitions for those Civil Geometry elements?"
I'd be interested in hearing anyones thoughts and ideas on this.
I know that had been some discussions on using a "dumbed down" version of a survey topo file that no longer contains the underlying fieldbook, that intelligence having been stripped off so it cannot be modified. Under such a scenario, are any of the graphics still recognized as features or are they just MicroStation elements at this point?
↧
↧
Coordinate issue in Power InRoads v8i
Power InRoads 8.11.07.615
One of my users is trying to use Horizontal Events to pull coordinates for some points in his DGN file. The coordinates that InRoads returns are different by several feet from the coordinates in the dgn (which I've confirmed by listing element characteristics, using the coordinate labeling tool in civtools, etc.). It's not an active depth issue (which I've seen do odd things before). Any idea why the coordinates in InRoads would differ from the selection of the same point in the DGN?
↧
[GPK SS4] Cutting semi-random sections through terrain - OpenRoads or Legacy tools?
It's been a few years since I worked with Geopak SS4, so my memory isn't sharp.
I need to cut some sections/profiles through my ground surface at a handful of random locations for some intersection sight distance illustrations. I know that prior to SS3/4 there was the Profile tool in the DTM tools that gave me just the results I'm looking for. I can see that is still available, but is there a better "OpenRoads"/SS4 tool I should be trying to use instead?
Thanks for your suggestions.
MaryB
↧
Problem creating a delta terrain
I'm having an issue with creating delta surface. I have a large project that is broken up into 7 main areas. I create delta surfaces all time to show where our cut and fills are since I'm typically using them from a drone created terrain surface to existing or design surface. I have clipped the large Final design terrain surface with the shapes of my report 7 report areas, this helps the computer when creating cut and fill volumes and delta surfaces since it can do it in chucks verse the whole thing. I have had no problem with 5 out of the 7 areas, everything created wonderfully and as expected. However, two of the areas will not create a delta terrain between the drone surface and the design surface. I have tried breaking those areas up smaller and still nothing, I have tried it in a completely fresh file and import only the three terrains and create a delta and still it won't happen. Through all my trial and errors I have discovered it always errors out when trying to create a delta to these two area's final design surfaces. It will not create a delta to anything other than a paln when using these design surfaces, but I have know idea as to why.
The work flow is to import or reference the design surfaces and the drone surface. Select Create Delta terrain (from the Create Terrain ribbon) select my design surface first, set the offset to 0 and then select my drone surface second and set offset to 0. It will think for a minute and then error out or just create nothing.
Below are the .tin's that I'm using, also a sheet that I create that is typical that is in a different part of the project, it is with the same process it worked fine.
/cfs-file/__key/communityserver-discussions-components-files/5922/Design-East_2D00_C-reduced.zip
↧
MX RENEW error (MX V8i SS2)
MXRENEW error message : Define Surface Wizard click Set string and click to Nex t : You will receive the enclosed error message.
Any idea ?
↧
↧
New DGN file with 3D seed is not opening in MX Roads
I am using MX Roads SS4 V8i.I am opening new DGN file with seed 3D-MX-Metric. I expect a fresh blank screen but instead, an error window pops up. The image is attached for reference.
↧
import export symbologies and feature definition fro ORD higher version to ORD lower version
Hi,
Is there any way to copy workspace from higher version of openroads designer connect edition (2019 Release 1 update 7 ) to lower version of Openroads designer connect edition (2018 Release 3 Update5).
I tried all possible ways to export feature definitions and symbologies to xlsx and xml from higher version and import it in the lowerversion of openroads designer connect edition. It get imported but with errors.
I will be much appreciated if any solution to bring the feature definitions and Symbologies from the higher version of Openroads Designer connect edition.
Regards
Ilyas
↧
PowerCivil SS4 (v8.11.9.714) keeps crashing when attempting to assess the sight distance along an alignment
I have been trying several times to assess the sight distance along an alignment with SS4 by exporting the alignment into a native IR alignment.
I activated the tool from the application add-ins in the explorer.
I used the tool available under "evaluation"
Unfortunately when hitting "Apply" the software shuts down.
Has anyone come across this issue before? Is there any other way to assess visibility with SS4?
Thank you
Kind regards
Gabriele
↧
Mxroad, sloped edge pavement /line mode/
My design model name is DESIGN,
center line string is MC00, left cway string CE00, right cway edge string CE0I,
road length is 1000m, start chainage is 0+000, but it is right for line mode to create sloped edge pavement? Like attached picture.
000 Pavement layer design
alia,design,d
desi,d
000 Left
110,mc00,,s100,4=-0.1,7=0.0,5=100,8=500
110,mc00,ce00,t101,4=-0.1,7=0.0,5=100,8=500
103,mc00,,s101,5=100,8=500
104,,s100,t101,7=-0.5
103,mc00,,s102,5=100,8=500
105,,s100,s101
105,,ce00,7=1
999
desi,d
000 Right
110,mc00,ce0i,t10i,4=-0.1,7=0.0,5=100,8=500
103,mc00,,s10i,5=100,8=500
104,,s100,t10i,7=+0.5
103,mc00,,s10j,5=100,8=500
105,,s100,s10i
105,,ce0i,7=-1
999
000 delete the temp strings
edit,d
031,t10
999
↧
↧
[ORD 2019 R2] Modifying horizontal complex without loosing vertical alingment
I've created horizontal geometry by using "Line Between Points" and placing arcs using "Arc Between Elements" tools. It looks like this:
It's a complex element with vertical alingment and many referenced elements, so I really don't want to drop this complex.
Now I need to rotate one line that it will behave like "Line To Element" ruled line. In other words: I want to rotate the tangent so that arc will extend and won't move.
The problem is that the line was defined as "Line Between Points" and it only rotates about these points. Is there a way change constraints of element in ORD?
Sorry if my question is silly, but I feel that I'm missing something simple as it was very easy thing to do in SS2.
Regards
Monika
↧
Creating Terrain Model from Ascii File Issues
I tried to create a terrain model from an ascii file, but my contours look very strange (see slanted lines). Was wondering if anyone can tell me what the issue is/ what I can do to fix it?
I can go more in-depth of exactly what I did, but here is a general overview of my steps: I downloaded the tin data from the website I normally do if I was doing this in MicroStation. I used the Create Terrain Model from Ascii File feature in ORD and uploaded the tin file. I opened the Create Text Import Settings File dialog box and went through the tabs on the left, and I made sure to specify my coordinate system. Then I closed that dialog box and clicked Import. I am not sure if there is something I am overlooking. Has anyone else had any similar issues?
↧
MXRoad benching slope excavation for existing road
Hi,
How to design earthworks that same as attached photo. Benching slope excavation for existing embankment. And quantity needs to define cutting and filling.
↧
imperial units used while creating this library (INROADS SERIES 2)
INROADS FAILED TO CREATE CORRIDOR WHEN YOU WANT TO SAVE IT SAYS "imperial units used while creating this library" And the corridor doesn't appear....Please help
Have already chosen the template all settings are in metric plus the units but still says "imperial units used while creating this library" and i want to use metric...
please help am stuck..............?
↧
↧
DWG > DGN ref. slowing down OpenRoads
Hi
I have recived a DWG ( Revit model converted to DWG) from an architect I work with. I have taken tis dwg and "merged " it in to a dgn to use as a reference.
I experienced my system to be extreme slow when working with this merged files... both directly or using them as a reference. Not the first when it comes Revit model / DWG.
Are there some guidelines when working with Revit models / DWG in a OpenRoads Designer environment?
Is it possible to "Clean" it up somehow?
regards
Sigfús
↧
Site Modeler, Roadway Pad Design
Hello,
I'm just trying to design a roadway pad in site modeler. But unfortunately i couldn't manage it. I have existing ground, Road1 design dtm, Road2 design dtm and Road3 design dtm. Could you please help me about designing a roadway pad into Site modeler. I want to see all roads at once and merged in one terrain model.
Thanks for your helps.
↧
Error using arc between arcs
I’m trying to fit two arcs between existing elements. The first element is a clockwise arc R=350m, the last element is a straight line. From this line I start a counter clockwise arc R=800m using “simple arc from element”.
Then when I try to close the alignment using “arc between arcs”, I configure it with a double spiral from the R=350 and a single spiral to the R=800, see image.
There is a solution, however the results are not correct.
the single spiral that fits between two arcs with the same direction has somehow become a spiral in the opposite direction, as shown in the attached image. It doesn’t matter whether I set it up as a compound or a reverse arc, the result is the same.
When correctly finished the alignment should look like this:
CW arc R=350
CW spiral A=120
CCW spiral A=100
CCW arc R=300
CCW spiral A=100
CCW arc R=800
straight
When I’m trying to build the alignment in the other direction, with the R=800 as the back element, there is no acceptable solution apart from some ridiculous loops.
I’m using ORD 10.6.0.38, but I get the same result using ORD 10.7.3.18.
Does anybody know if I’m doing something wrong?
↧