<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://communities.bentley.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Cameron Tomkins's Activities</title><link>https://communities.bentley.com/members/0ca9b3cd_2d00_963b_2d00_454f_2d00_beec_2d00_03b653da80af</link><description>Cameron Tomkins's recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Elevation Axis displaying incorrectly.</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/109456/elevation-axis-displaying-incorrectly</link><pubDate>Mon, 03 Aug 2015 19:30:09 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:a44acd4c-10ef-4162-83ac-6f040d2d8255</guid><dc:creator>Cameron Tomkins</dc:creator><description>&lt;p&gt;When opening a profile view, cross-section view, and or any view that bring ups a X and Y Axis (normally X being stationing and Y being elevation) the Y Axis is defaulting to showing only &amp;quot;&lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;ZZZ&lt;/strong&gt;&lt;/span&gt;&amp;quot;. I believe this to be caused by the resolution of my monitors. I&amp;#39;m currently using two 29&amp;quot; ACER monitors running at 2560 X 1440. See the image below showcasing the problem. As a side note it seems that some windows also have a tendency to be be &amp;quot;hidden&amp;quot; behind other windows from time to time such as the element selection box, normally this isn&amp;#39;t to much of a problem but can be frustrating at times.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/7853.Capture.JPG"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/5922/7853.Capture.JPG" alt=" " /&gt;&lt;/a&gt;&lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;&lt;br /&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Inroads to Trimble Business Center RXL creation corruption.</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/110218/inroads-to-trimble-business-center-rxl-creation-corruption</link><pubDate>Wed, 26 Aug 2015 13:51:05 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:c448594e-6236-4a04-b6ce-45d0446db047</guid><dc:creator>Cameron Tomkins</dc:creator><description>&lt;p&gt;I&amp;#39;m modeling a corridor in InRoads and need to make a RXL for this. The only way that I know how is to export a XML from InRoads bring that into Trimble Business center and export from there. However when I create the RXL and bring it back in there are area&amp;#39;s that get skewed away from the original XML and are causing chatter along the surface. I believe this to be caused by features that make up the terrain model that are not either part of the corridor and/or not at the same interval the corridors vertex&amp;#39;s are at.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;The screen below shows the XML of the terrain:&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/xml.JPG"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/xml.JPG"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/xml.JPG"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/xml.JPG"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/xml.JPG"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/5922/xml.JPG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This screen shot shows the RXL:&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/rxl.JPG"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/5922/rxl.JPG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Inroads SS3 Corridor Feature Surface XML</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/108228/inroads-ss3-corridor-feature-surface-xml</link><pubDate>Thu, 25 Jun 2015 17:55:08 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:add7ed81-a070-4f1b-843b-d2774902fbca</guid><dc:creator>SaltyTP</dc:creator><description>&lt;p&gt;We are currently creating DTM surfaces based from corridor features.&amp;nbsp; When we export out an XML for TBC to export to an RXL it is missing breaklines.&amp;nbsp; The breaklines missing are the features that are created in multiple locations along the corridor.&amp;nbsp; If we have add a second lane, drop a second lane and then add it again, the second time it is added it will not carry the features into the XML.&amp;nbsp; This feature is created as one element because it has the same point name.&amp;nbsp; Bentley handles it fine, but it does not appear that anyone else does.&amp;nbsp; This would mean that we would need to make a new&amp;nbsp;template with different name every time we have a curb&amp;nbsp;drop or lane add, etc.&amp;nbsp; We need those features for layout in the feild. Please see attached images of a demo corridor and the XML when imported into TBC and Civil 3d.&amp;nbsp; Does anyone have a work around for getting these coded/named features into TBC?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Scott&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/Corridor-feature.PNG"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/5922/Corridor-feature.PNG" alt=" " /&gt;&lt;/a&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/XML-Feature-Based-Surface.PNG"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/5922/XML-Feature-Based-Surface.PNG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>