Quantcast
Channel: OpenRoads | OpenSite Forum - Recent Threads
Viewing all 15087 articles
Browse latest View live
↧

RE: 3d Linestyle issues with ORD

April 13, 2017, 7:55 am
$
0
0

ok I seem to have found the issue...

It seems that placing the rsc in the \WorkSpaces\xxxx\Standards\Symb in ORD adds the linestyles to the linestyle list but results in them not being displayed correctly (eg. solid line in 2d, invisible in 3d). If I put the rsc file in \Organization\Symb then it works perfectly.

The workspaces symb location has been defined in the cfg (MS_SYMBRSRC) and seeing as it is being added to the linestyle list and previews correctly in the editor I don't understand why this isn't working. I have tried putting the rsc in the workspaces location for Microstation Connect and it works fine.

↧
Search

RE: 3d Linestyle issues with ORD

April 13, 2017, 8:09 am
$
0
0

ok I seem to have found the issue...

It seems that placing the rsc in the \WorkSpaces\xxxx\Standards\Symb in ORD adds the linestyles to the linestyle list but results in them not being displayed correctly (eg. solid line in 2d, invisible in 3d). If I put the rsc file in \Organization\Symb then it works perfectly.

The workspaces symb location has been defined in the cfg (MS_SYMBRSRC) and seeing as it is being added to the linestyle list and previews correctly in the editor I don't understand why this isn't working. I have tried putting the rsc in the workspaces location for Microstation Connect and it works fine.

↧
↧

RE: 3d Linestyle issues in ORD

April 13, 2017, 8:49 am
$
0
0

Great investigation but wouldn't it be better to open a TR Ticket to get that solved in a future release?

↧

RE: Unable to edit VPI on profile imported to OpenRoads

April 13, 2017, 9:02 am
$
0
0
It's been two years since you said "an upcoming release." Surely this has been released by now. Please let me know where it is.
↧

RE: Unable to edit VPI on profile imported to OpenRoads

April 13, 2017, 9:06 am
$
0
0
You can find new versions at the Software Fulfillment Centler. You can access them from your personal portal at https://connect.bentley.com/ Just log in and go to the Software Downloads section. Then search for OpenRoads Designer. That is the latest version.
↧
↧

Unable to edit VPI on profile imported to OpenRoads

May 6, 2015, 1:42 pm
$
0
0

When I import alignments from native (gpk) to Openroads (SS3 and SS4), the resulting profile does not display the VPI's for editing. When I click on a vertical curve, the PC's and PT's display and can be edited, as can the curve length, but this makes for an awkward way to modify the profile. It would be much easier if the VPI's would display. I've tried to bring the profile in without rules, drop the profile, and create civil rule features but the result is the same. I've added a screenshot showing a vertical curve selected, only the curve length and VC parameter can be changed, not the VPI. Is there any way to fix this?

↧

RE: Hand-editing Cross Sections and pushing changes back to Design?

April 13, 2017, 4:05 pm
$
0
0
In this version, I believe it reads the surface elements. As such, only insert vertex, delete vertex, modify, extent to intersection are available as tools. If you create new elements that are not recognized by InRoads as coming from a surface, it will ignore them. The same goes for components. I had a project where every now and then, a component would be missed on a section. I could draw one in, or even copy one from an adjacent section, but InRoads would ignore it.
There used to be a tool that allowed you to identify elements as being Surface elements and then you could use Surface from Sections to make a surface.
If End Condition Exceptions can be used, that's a better option. Or use the feature tools to develop a 3D feature to follow in that area and adding it as a H&V point control. Lastly you could use those same tools to modify the breaklines of your corridor and regenerate a surface from it. I believe if you modify all features used by a component, you might even be able to redisplay a new version of the component. And if that seems to work, refresh the ross sections and try running the volumes again.
↧

Hand-editing Cross Sections and pushing changes back to Design?

April 13, 2017, 12:08 pm
$
0
0

I have a number of manual changes to make to my cross sections. These are isolated, one-off items that are driven by Engineer's opinion than by reproducible programmatic logic. Things like "why don't we just tie to existing ground at that one section" or "we don't need a ditch, but could you show some grading so it will drain right in there".

As small as these items are, I want these changes reflected in my construction limits (proposed surface boundary) and, if possible, in my proposed surface. Is there a way to "push" hand edits back to my design surface?

Also, I need to run end area/volumes for my earthwork computations. Do those run by cross sections, or are they from model to model? Will they calculate along the top of my design, or will it find my components and include/exclude those volumes as appropriate? All the more reason to make sure that my hand-edits can be pushed back to design...

Thank you.

↧
Search

RE: GDOT customization for Power InRoads

April 13, 2017, 4:33 pm
$
0
0
I would like to have some more information from you ClayCo. Can you email me?
↧
↧

GDOT customization for Power InRoads

June 17, 2015, 2:03 pm
$
0
0

Hello.  First of all, I am using version Power Inroads v8i ss2 08.11.07.615.  I am trying to set up all of GDOTs customization tools for power inroads.  After running the seperate executable files for microstation and inroads that I got from GDOT, and a couple of other minor changes, I have been able to use power inroads platform with the GDOT preferences up until now.  Now when I go to use the GDOT Root Menu when setting up sheet files, many commands doesn't work.  I have gotten little to no help from GDOT and Bentley doesn't support these customization tools that the DOTs add to microstation.  Has anyone else experienced this and possibly knows how to fix it?

↧

RE: 3d Linestyle issues in ORD

April 13, 2017, 9:00 pm
$
0
0

Thanks Frank, Yep good point, will do but isn't the whole point of the communities site to ask the question before resorting to putting a ticket in.

Doesn't this forum give everyone a heads up to potential issues they may get doing certain things?

↧

3d Linestyle issues in ORD

April 13, 2017, 7:31 am
$
0
0

Hi all,

I have some 3d linestyles that include mesh components that don't seem to display at all in ORD - they work fine in SS4 and Microstation Connect (update 4). Other 3d linestyles that just include shapes/lines etc. come in okay. They have always been stored in RSC files, but I have even tried putting them in a dgnlib with no luck.

Has anyone else experienced this issue? I have attached a resource file with the linestyles in question.

I need to use meshes for the components of the 3d linestyle for Navisworks (or any Autodesk) solid compatibility, ie. drop the linestyle and export otherwise I get thousands of shapes and lines, etc.

[View:/cfs-file/__key/communityserver-discussions-components-files/5922/3D_2D00_Wire_2D00_Rope_5F00_EXTRA.rsc:100:0]

Regards,

Mark

↧

RE: OpenRoads Designer: The unit issue of Analyze Volume tool

April 14, 2017, 1:39 am
$
0
0
Hi Mark, as I indicated what about the unit issue, could you plase try this ?
↧
↧

OpenRoads Designer: The unit issue of Analyze Volume tool

April 11, 2017, 3:31 am
$
0
0

Hi,

The unit of Analyze Volume tool may have a little bit issue.

 

The following is a test model:

It is a rectangular site in which every length is 20m, and its elevation is 180.0m, from the below picture, the elevation of existing ground is 174.00m, so it is about 6 meters high.


Firstly, the Apply Linear Templatetool is used to generate the slope model, and then create design terrain from slope model to calculate the cut and fill volume.

The Analyze Volume toolwill be used to calculate volume:
Method: Terrain model to terrain model volume
Local from terrain model: the existing ground terrain is selected
Local to terrain model: design terrain


From the result, it is obviously wrong.

But with the other tool: Create cut fill volumes, the result is right.


 

From the 2 results, the unit issue of the software should be found.


Another question:

 



Normally, the Element Selection tool will be always on, but, in OpenRoads designer, sometime the tool is suddenly off, even if restarting computer.


How to turn on this important tool?

 

Thanks!

 

Chen zhengpeng

11/04/2017

↧

OpenRoads Designer not detecting Workset .itl

April 14, 2017, 2:05 am
$
0
0

Hi

I am trying to let OpenRoads designer detect workset .itl in project folder.

I have created a workset where the "Standard" folder is located in the project folder.

I have activated the variable in the workset .cfg, but it dont work and ORD keep detecting the .itl from "Organization" folder.

 What can I be missing here?

# Template for an OpenRoads Designer WorkSet
#============================================================================

#============================================================================
# WorkSet (PW=Project) Template Library and Seed File
#============================================================================
# WorkSet (PW=Project) specific template library and/or seed file can be loaded
# by defining the variables below with the template library or seed file name.
#
# If an itl file or seed file with the specified name is not found, the
# template library or seed file specified by the WorkSpace (PW=Site) or
# Organization (PW=Customer) standard is loaded.
#
# <<<< Make Changes Here >>>>
# Uncomment the following lines and define the appropriate file names.
#CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME = Replace with WorkSet Template Library File Name.itl
CIVIL_WORKSET_TEMPLATE_LIBRARY_NAME = SM_Templates_Metric.itl
#CIVIL_WORKSET_DESIGNSEED = Replace with WorkSet Seed File Name.dgn

---------------------------------------------------------------------------------------------------------------------------------

regards

Sigfus

↧
Search

RE: Has anybody used the Attributes in Openroads, not Inroads?

April 14, 2017, 6:38 am
$
0
0
I'm not sure I understand what you are asking. Are you talking about Survey Attributes with Open Roads Survey?
The success of this requires some specific modifications to variables and more if you want to try and use traditional InRoads Survey Codes. A few are not supported and a number of new/replacement codes have been added. Also, Attributes often rely on a TIW file with specific settings. Open Roads might not be looking in the same location for TIW files as InRoads. Also, there is a GEOPAK TDS format and an InRoads TIW driven TDS format.
We have also seen newer releases of the data collector software sometimes changes how the attributes at accessed or stored in the raw file. In most cases, you have to either export the file on the data collector, or use an after-the-fact conversion tool to take the XML survey file and transform it to another format. This conversion tool is actually very similar to the InRoads XML Reports - using XML style sheets (XSL) to read and transform one file type to another. They provide a TDS Style sheet, but it writes Attributes in yet another format from the original TDS format. With my skill set from customizing InRoads XML reports, I was able to create a version that wrote out attributes in the manner we have always used.
Also, InRoads supports a dot notation for attributes, using a Note field. The method is very simple add a new not to a shot and type a period (dot) as the first character. Follow this immediately with the attribute name, a space and the attribute value. Initially, this could only read single word attributes, but later releases were able to read at least three word attribute values.
We edited the TDS TIW file to make a comma an acceptable delimiter, so our crews could type the period and the attribute name followed by a comma and then, they could write a book, as long as they did not use any commas.
↧

RE: Has anybody used the Attributes in Openroads, not Inroads?

April 14, 2017, 7:09 am
$
0
0
Hi Chuck,
How are you? This is Bill from SHA.
 
Our email was updated and I lost a bunch of contacts, I noticed you are also testing Openroads files on ProjectWise with Mark Van Wert and James Shiu.
 
I’ve noticed that there are different codes that come as a default with Openroads, I have changed a few so that they work with importing a .RW5 file but I cannot get the Attribute lines to import correctly.
 
Right now the code is;
 
AT,TNTY,TVMAC
 
But I want to be able to use the default codes:
AN* = attribute name
AV* = attribute value
AA* = attribute array
 
I’m just getting stumped every time I try something different.
 
FYI – I am not sure if SHA will be using Power Inroads or Openroads Survey in future, I have not been able to get a direct answer, but I know eventually that Inroads will be phased out of Bentley products.
 
Thank you
Bill
 
 
↧
↧

MXRoad template creation.

April 14, 2017, 9:12 am
$
0
0 
Hello mxroad designers.
Is it possible to create cross s ection template following attached image. Its urban road type template.
↧

RE: Unable to load/create dialog...

April 14, 2017, 10:24 am
$
0
0
Blowing away the upf fixed the issue. Funny how that silly UPF has been an issue for nearly 30 years!
↧

RE: Has anybody used the Attributes in Openroads, not Inroads?

April 14, 2017, 1:00 pm
$
0
0

I thought it was you. The example you posted is the traditional TDS RAW Attribute AT,TNTY,TVMAC. All TDS Records use 2 character codes for almost everything in the file, with commas between fields. I've pasted a link to a PDF of the full TDS Raw Data Spec. 

So the AT defines that this is an Attribute record. It accepts two String values - TN designates the first field will be the Attribute Name. Every character between the TN and the comma is the Attribute Name. Then there is the TV which designates that the  next field is the Attribute Value. Everything following the TV is read as its value, up to the end of line.

If the crews use a collector with an Attribute File loaded, it will write the record based upon what the crew enters in the various dialog boxes that the TDS software provides from the supplied attribute file.

I am not sure how Carlson does Attributes - sometimes they have extended the TDS Specs to meet their needs.

The main issue. is when the crew is shooting topo, they can either enter attributes using this menu driven approach, of they can use the Dot notation method I mentioned in my first post. There is no mechanism for them to create custom records ion the TDS file.

So the AN* AV* AA* syntax would require manual edit of raw file after the fact. Unless there is some toggle or data collector out there that creates its attributes in that manner. 

Here is that link: http://www.microsurvey.com/support/fieldgenius/documentation/TDSRawDataSpec.pdf

And here is a link for Stylesheets that could be used to create a custom version of a RAW file: http://www.trimble.com/globalTRLTAB.asp?nav=Collection-32914

Here is more info on that: 

Trimble ASCII File Generator UtilityDownload this utility program to apply style sheets to Trimble Access/Trimble Survey Controller JobXML or job files in order to create custom export formats or reports on your office computer.

  • Trimble ASCII File generator InstallationWhen you install the Trimble ASCII File Generator a new ASCII File Generator program shortcut will be added to the Start Programs Menu under Trimble Office|Utilities.

    Use the ASCII File Generator utility program to apply custom export style sheets to Trimble Access or Trimble Survey Controller JobXML or job files that you have download from your device. This utility is useful for creating export files or reports for Trimble Access/Trimble Survey Controller jobs that are too large to be processed on the Trimble Access/Trimble Survey Controller TCU, TSC2 or TSC3 devices (the Windows CE and Windows Mobile operating systems have limited memory available for carrying out style sheet transformations).

    As part of this installation a selection of style sheets is installed in the \Trimble Style Sheets\Custom ASCII Files folder on the installation drive.

    See the help information available with the utility program for further details.

    Updated to program version 1.0.26 on 19th October 2016 (modified so that 'Trimble JobXML' can be specified as the 'style sheet' to be applied on the program command line in order to have the program used to convert a Trimble Access job file to a JobXML file).

This used to be pretty simple. Why did they have to add these extra levels of complexity.

↧
Viewing all 15087 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>