Is there a plan in the future to be able to export OpenRoads file to IFC, currently to do that I have to open my dgn file in Aecosim and export it from there but I wont have all the paramenters of my elements in the dgn file.
thanks,
Amr
Is there a plan in the future to be able to export OpenRoads file to IFC, currently to do that I have to open my dgn file in Aecosim and export it from there but I wont have all the paramenters of my elements in the dgn file.
thanks,
Amr
Hi Amita,
Sorry for the confusion. It's bit hard to explain in writing. If you can give me a call at 206-440-4949, I can show you the difference.
Yes, I initially set to use same working units with 12,000 resolution for both Bentley imperial dataset& WSDOT dataset below.
I used catch basin named SQCB in Bentley dataset and used another catch basin named CB in WSDOT dataset. The reason that I used CB in WSDOT dataset was to link native WSDOT xin file in OpenRoads to display it correctly.
Findings:
When I displayed both catch basins in Microstation using place cell command, regardless what scale annotations that I used like 1 inch = 100 feet, both cells resized & measured correct size accordingly.
Only problem that I'm having is when I exported from survey data of CB in WSDOT dataset to dgn file. I re-confirmed that dataset mismatched with a 100 scale factor after exported to dgn.
Here are two additional screen shots that I made for Bentley's catch basin & WSDOT's catch basin. The distance don't matter. I need to further investigate where the mis-match with a 100 scale factor comes from. Thank you once again for your help.
James
Hi Purva,
I didn't mean to make you rush to find the answer. Here is additional information that I answered to Amita Shinde. I hope that this would help & Thank you~ =)
I initially set to use same working units with 12,000 resolution for both Bentley imperial dataset& WSDOT dataset below.
I used catch basin named SQCB in Bentley dataset and used another catch basin named CB in WSDOT dataset. The reason that I used CB in WSDOT dataset was to link native WSDOT xin file in OpenRoads to display it correctly.
Findings:
When I displayed both catch basins in Microstation using place cell command, regardless what scale annotations that I used like 1 inch = 100 feet, both cells resized & measured correct size accordingly.
Only problem that I'm having is when I exported from survey data of CB in WSDOT dataset to dgn file. I re-confirmed that dataset mismatched with a 100 scale factor after exported to dgn.
Here are two additional screen shots that I made for Bentley's catch basin & WSDOT's catch basin. The distance don't matter. I need to further investigate where the mis-match with a 100 scale factor comes from. Thank you once again for your help.
James
Hello,
In general, how does survey annotation scale works in OpenRoads? Where is the base size set at? Our cells are coming in at a scale of 1200 before the annotation scale is applied.
James
The XML Reports for Corridors sometimes contain values in metric units and need conversions within the reports. The units are specified in the reports, so creating and applying a conversion factor is certainly do-able. A number of the older reports would call out the units and even do some conversions.
I've noticed a number of items in the Corridor Reports are not searching for the correct attributes or nodes. They may report no Parametric Constraints, Point Controls or Secondary alignments when there are some of these in the reported upon corridor.
Hi
I have two questions
Does anyone know how to set the earthwork interface to cut only (100% cut) and one metre below existing ground (421421 slope) using an input file?
I am trying to code up a 1.5m footpath followed by a retaining wall to existing ground followed by a swail drain. Can anyone help me via the input file method? It just doesn't seem to be working, I'm not sure i'm using the right code.
Thank you
i am not getting source to learn how to use mx road in bentley student server when i search for mx learning material it ends on open roads so i want to knw that is the learning method for both the software are same? If not then please will someone provide me link for it.
Derek, I got debug report. what's next?
(Please visit the site to view this file)
When my XSEC are not 100% above the ex grade the labeler is labeling everything making for a laborious clean up. In the example below, I have a milling component that is seeking ex ground. When my proposed template is below ex ground the labeler is labeling the slopes of the milling component/ex ground which I don't want. I tried turning off the milling level and ex terrain before I annotated but it didn't work. There has to be a way of telling it to only label the top surface of the proposed template if not it should be incorporated. See image below.
I am unable to edit my feature definitions library.
Is there some sort of setting I am missing? I want to modify and create a number of feature definitions for use in SUDA but when in Project Explorer, right clicking literally does nothing except on existing Feature Definitions (which only offers to view the properties). I have full write access to the file but none of the Feature Definition creating/editing functionality is available to me.
See below: All of the Feature Definitions that are live in this .dgnlib file are colored dark-gray (as opposed to the referenced libraries which are a light-gray). They are actively in the file but if I want to rename, reorganize, create, or basically anything, I cannot. Every tutorial and video on the Feature Definition library assumes this supposedly easy task is available to all. I feel like I am missing something important yet very easy!
Judging from the write-up of your problem, it sounded to me like the file Microstation was reading wasn't the file you (or your workspace manager) were expecting. In light of that, it was worth working out exactly where the value of CIVIL_XIN_FILE is being defined.
Looking at it, I see that in line 808 CIVIL_XIN_FILE is defined at the application level.
In line 981, it is defined at the user level, and (in this case) at line 975 you have the name of the file that defines it.
At line 1365, the final value is reported. Of course CIVIL_XIN_FILE hadn't been redefined since then, so it's the same as the definition from line 981.
The only thing I was suggesting to look at is that final value, to confirm that it is the right file that you expect it to be. I hope that helps, though I don't necessarily expect it to. Beyond that, I can't help on this.
Edit: Having re-read your problem, it sounds like this may indeed be part of a workaround without necessarily being a solution. (When you redefine a variable, it should be saved, but apparently it's not. Therefore, you need a workaround.) Locating exactly where CIVIL_XIN_FILE is defined, you will be able to define it to whatever it needs to be in the source file where it is defined now.
Hi All,
Just wondering if anyone has ever had an issue opening a file within InRoads after first install.
When opening I'm presented with an initial error message that says.
Microsoft .NET Framework
Unhandled exception has occured in a component in your application. If you click Continue, the application will ignore this error and attempt to continue. Exception has been thrown by the target of an invocation.
There is also a details box with the error log which is attached.
A CMD box also appears with the below Text Windows
MD Loader: Could not load application c:\program files (86)\Common Files\Bentley Shared\Civil Platform\08.11.09\CivilDialogExt.ma
MDL Loader: Could not load application Bentley.Civil.Help.1.5.dll
MDL Loader: Could not load application Bentley.Civil.CoreCommands.1.5.dll
It then crashed and I have close the program and another line appears
MDL Loader: Could not load application Bentley.Civil.Model.IR.Commands.1.5
Any help will be much appreciated.