<?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>Adam Ryan's Activities</title><link>https://communities.bentley.com/members/50d9aa9e_2d00_eb12_2d00_4738_2d00_9a25_2d00_bfec89420ea1</link><description>Adam Ryan's recent activity</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>Open Roads - Field Book Survey File Import - Points Codes With Comments</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/170825/open-roads---field-book-survey-file-import---points-codes-with-comments</link><pubDate>Tue, 13 Nov 2018 15:33:12 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:fbcdf637-5939-4137-a58b-29054237b557</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;Hello, my survey department is starting to move away from using the Geopak/GPK method of importing survey data into our basemaps. Almost always, our text files from the field crews have comments associated with the codes for each point. such as descriptions of control points, or sizes of trees, etc. separated by a dash &amp;quot; - &amp;quot;... (See below)&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;EXAMPLE&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;&lt;strong&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/pastedimage1542122771694v1.png" alt=" " /&gt;&lt;/strong&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span style="text-decoration:underline;"&gt;&lt;/span&gt;When we import this into our Project Explorer-Field Book, it creates new points for almost every word in the comment. (EX: BM1 - &amp;quot;BM&amp;quot;, BM1_1 - &amp;quot;-&amp;quot;, BM1_2 - &amp;quot;NORTH&amp;quot;, BM1_3 - &amp;quot;BOLT&amp;quot;, and so on.&lt;/p&gt;
&lt;p&gt;Is there a way when using the &amp;quot;Text Import Wizard&amp;quot; to specify that the dash &amp;quot; - &amp;quot; specifies a comment associated with the point?&amp;nbsp; to basically have its own column for the comments? (see images below)&lt;/p&gt;
&lt;p&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/pastedimage1542123126018v3.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/pastedimage1542123100459v2.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;We are currently using Power GEOPAK V8i with Open Roads (SS4)&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Adam Ryan&lt;/p&gt;
&lt;p&gt;Survey CAD Tech.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Microstation Forcing Vertical Curves/Splines into Curved Survey Feature</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/133213/microstation-forcing-vertical-curves-splines-into-curved-survey-feature</link><pubDate>Wed, 22 Mar 2017 20:36:41 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:9c42da54-9d7a-4b54-9020-a4c91855511f</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;I created a new field book and imported a text file with survey points. after importing and cleaning the linework and points i noticed that any curves that were drawn have a vertical curve/spline forced into them.&lt;/p&gt;
&lt;p&gt;instead of holding the elevations of the points in the feature, the curve dips above and below where it is supposed to be. (see picture below)&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/vertical-curve-in-curb.JPG"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/5922/vertical-curve-in-curb.JPG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;it is supposed to be a curved top back of curb feature line. is there a setting in microstation that will stop this from happening?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;CURRENTLY USING &amp;nbsp;&amp;quot;cadd Power GEOPAK V8i (SS4) with openroads.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;thanks,&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>&amp;quot;InRoads digital terrain model (DTM)&amp;quot; vs .TIN</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/142715/inroads-digital-terrain-model-dtm-vs-tin</link><pubDate>Wed, 01 Nov 2017 18:19:29 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:387cfeb0-ff4b-4565-ba59-cf1bfb9db09d</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;A client wants us to provide them with an InRoads digital terrain model (DTM) for a project we are doing. However, we are only used to creating &amp;quot;.tin&amp;quot; files using the build DTM tool in our &amp;quot;ODOT cadd Power GEOPAK SS4&amp;quot; version of microstation.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;is there a difference between a DTM and a TIN? or are they the same thing just named differently?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;how can we convert a TIN to a DTM if they are different?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Adam&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>OVERWRITING CALC POINTS WHEN IMPORT SURVEY ASCII FILE</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/140362/overwriting-calc-points-when-import-survey-ascii-file</link><pubDate>Thu, 31 Aug 2017 12:10:27 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:dec9964f-c8eb-4395-9e3b-14d1e0062863</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;The following text describes the issue that we are running into when trying to import a new ASCII text file into a survey basemap drawing.&lt;/p&gt;
&lt;p&gt;PROGRAM BEING USED::::: ODOT cadd Power GEOPAK SS4 - Version 08.11.09.878&lt;/p&gt;
&lt;p&gt;Using the Survey Menu; create a new dataset, specify the text file to import, once import has started a box pops up warning us we are about to overwrite a point (ie: CALC1002), this point did not exist in the GPK prior to importing this new text file.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/image-1.JPG"&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/image-1.JPG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;We select the option to add a prefix to the point number that is being overwritten (ie: ARCALC1002) and hit apply&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/image-2.JPG"&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/image-2.JPG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;After applying, it continues to warn us that we are overwriting more points that did not exist in the GPK prior to this import (ie: CALC1004, CALC1005&amp;hellip;.) and it keeps wanting to overwrite the same CALC point over and over again (2 or 3 times per point), adding 1% to the total import every time.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/image-3.JPG"&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/image-3.JPG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;SUMMARY: it keeps wanting to overwrite points that are being created from the same DATASET that I am trying to import, even though these CALC points did not exist before selecting the new text file.&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/5922/image-4.JPG"&gt;&lt;img src="/resized-image/__size/320x240/__key/communityserver-discussions-components-files/5922/image-4.JPG" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;what are solutions to fix this? We cant import any other text files without it trying to overwrite points that didnt exist until this import&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Crashing while building DTM using Feature Table(SMD)</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/139216/crashing-while-building-dtm-using-feature-table-smd</link><pubDate>Tue, 01 Aug 2017 18:10:46 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:6761403a-9d80-412e-ac81-d1f0adfc8085</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;Currently trying to build an existing topo surface (.tin) using an ODOT style Feature Table (SMD) to determine which points are included in the surface. Crashes every time without creating any (.tin) files. it only works when we change the &amp;quot;Determine DTM Inclusion from:&amp;quot; option to &amp;quot;All Points/Chains included&amp;quot;. this has happened on every job we have recently surveyed and basemapped and it adds alot of time when trying to individually remove trees and utilities from the surface triangles.&lt;/p&gt;
&lt;p&gt;Is there a fix for this?&lt;/p&gt;
&lt;p&gt;We are using Microstaion - Power GEOPARK V8i (ss4)&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;thanks,&lt;/p&gt;
&lt;p&gt;Adam Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Ask A Question I</title><link>https://communities.bentley.com/achievements/460ac7df-7ccc-4c42-a204-9e05eef3be09</link><pubDate>Tue, 01 Aug 2017 18:10:47 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:bc4ab1e6-fe41-4b45-83b3-ac6042e8b6ba</guid><dc:creator /><description>Ask a question in a forum.</description></item><item><title>What is the correct procedure to create and edit and export a Terrain Model?</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/133484/what-is-the-correct-procedure-to-create-and-edit-and-export-a-terrain-model</link><pubDate>Wed, 29 Mar 2017 17:36:19 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:8d28492c-f484-4ccb-af4b-7776c281e87a</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;What are the correct steps to create a terrain model from field book data?&lt;/p&gt;
&lt;p&gt;i created the terrain from the field book. deactivated surveying processing rules in order to make the model editable. cleaned up triangles/swapped edges and so on. extracted boundary and added it to terrain model to maintain my current edits. noticed a curb feature was out of place, fixed curb feature, deleted bad points from terrain model. went to add newly updated curb feature into the terrain. and all looked fine.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;went to re-activate survey processing rules to allow the model to be updated automatically if points/feature lines are modified. as soon as i did that, i noticed several survey figures get removed from the terrain model (that had never been touched) and the figure that i modified stayed but the bad points from the original location of the line get added back into the model, even though i had deleted them from the model and updated the survey figure.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;SO HOW CAN I GET THE SURFACE TO CREATE, MAKE EDITS TO IT, ADJUST THINGS THAT NEED FIXED, AND RE-ACTIVATE PROCESSING RULES SO THAT THE SURFACE IS EXACTLY HOW I INTENDED IT TO BE AND IS ABLE TO BE UPDATED IF SOMETHING IS MOVED?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Adam Ryan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>Complex Terrain Model - Break_Line Issue/Surveying Processing Rules</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/131589/complex-terrain-model---break_line-issue-surveying-processing-rules</link><pubDate>Fri, 10 Feb 2017 00:32:32 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:1c2d0d77-1565-48cc-9f68-1c66ae08b477</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;Current Program: ODOT cadd Power GEOPAK V8i SS4 with OpenRoads&lt;/p&gt;
&lt;p&gt;Project Description: Using OpenRoads version of microstation to connect intersections &amp;nbsp;that were previously base-mapped with V8istd version of microstation with the new surveyed main road.&lt;/p&gt;
&lt;p&gt;After cleaning up points and line-work i created a new terrain model from field book data, and created 7 other terrain models (from file) using individual .TIN files that were created using &amp;quot;ODOT V8Istd Power GEOPAK SS4&amp;quot;. Created a complex terrain model using the &amp;quot;field book&amp;quot; terrain as my primary surface, and the other 7 terrains as to be merged. I then Deactivated the Surveying Process Rules under the survey tab of the project explorer in order to edit the Complex Terrain.&lt;/p&gt;
&lt;p&gt;When i went to add features (top of bank/toe of slope) that were removed during the merge process, many other features were excluded from the terrain after the new features were added. &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;ie: added the top of bank feature to the terrain and it deleted triangles from several curb, edge of pavement, and sidewalk lines.&lt;/p&gt;
&lt;p&gt;Why did this happen? and what is the correct procedure for activating and deactivating Terrain Rules in order for the terrain to keep edits made to it?&lt;/p&gt;
&lt;p&gt;Occasionally i was still unable to edit the terrain model even though i deactivated the processing rules in the survey tab. i then would have to switch to the civil model tab in the project explorer and lock or unlock the rules for the terrain models.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Really appreciate any help, i cant move forward with the project until i get this resolved.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;thanks,&lt;/p&gt;
&lt;p&gt;Adam Ryan&lt;/p&gt;
&lt;p&gt;Survey Cadd Tech.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>shot markers created from graphics not showing up</title><link>https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/131248/shot-markers-created-from-graphics-not-showing-up</link><pubDate>Wed, 01 Feb 2017 16:03:41 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:d7d291e7-9825-4ea8-96af-21310a015a83</guid><dc:creator>Adam Ryan</dc:creator><description>&lt;p&gt;While working with 2 separate field books, one being data created from microstation graphics, and the other being all new raw survey data, the shot markers from the field book created from graphics keep disappearing from the drawing after i began editing the new raw data. they are still in the field book but i cannot see the physical yellow cross/marker.&lt;/p&gt;
&lt;p&gt;how do i re-visualize the markers back into my drawing from the fieldbook?&lt;/p&gt;
&lt;p&gt;i am using Power GEOPAK V8i (SS4) with open roads&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>