<?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/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Depths out of order when outputting.</title><link>https://communities.bentley.com/products/geotechnical1/f/geotechnical-forum/111483/depths-out-of-order-when-outputting</link><description>Hi All, 
 
 I&amp;#39;m having some trouble trying to create a soilbore profile which had a stockpile on top. The stockpile was .45m high AGL, below it was natural ground which was augered to 0.3m BGL. Ideally it&amp;#39;d look something similar to the table below: </description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Depths out of order when outputting.</title><link>https://communities.bentley.com/thread/342672?ContentTypeID=1</link><pubDate>Thu, 15 Oct 2015 02:39:59 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f6dc7cb5-986a-4e83-8110-ab3d053539e4</guid><dc:creator>szang</dc:creator><description>I have run into this problem before when dealing with Well Stickup above the ground surface entered as a negative depth.  gINT does not properly sort negative depth values when outputting to a graphic report and misplaces text that is associated with a negative depth as you describe.  To solve this problem, I used a crude hack that simply created another field in the table called depth1000.  this field is automatically populated using a gint rule as the depth + 1000 which gets rid of the negatives.  I then use formulas in the report to plot it and subtract the 1000 at output time. I can provide more specifics if this seems to answer your problem.&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Depths out of order when outputting.</title><link>https://communities.bentley.com/thread/340768?ContentTypeID=1</link><pubDate>Wed, 30 Sep 2015 04:25:27 GMT</pubDate><guid isPermaLink="false">6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:76d7c5f9-f135-453d-83c3-fc83a53ed01e</guid><dc:creator>Kirk Johnson</dc:creator><description>&lt;p&gt;Hi Andrew,&lt;/p&gt;
&lt;p&gt;It really depends on what type of report you are creating and your custom gINT files. Here is a basic example of a log report. There are two text vs depth columns. One for lithology Depth and one for Lithology Description (see example below) .. You can also set the report property&amp;nbsp; top depth expression to be the Min lithology depth (see below. There are endless possibilities (different report types, how your files are setup etc..)&lt;/p&gt;
&lt;p&gt;If you want something different than this contact me at &lt;a href="mailto:kirk.johnson@bentley.com"&gt;kirk.johnson@bentley.com&lt;/a&gt; and I can help you set up your customized files.&lt;/p&gt;
&lt;p&gt;Here is how I input the data&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/283906/Data-Input.png"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/283906/Data-Input.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/283906/text-vs-depth.png"&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/283906/text-vs-depth.png"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/283906/text-vs-depth.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/283906/Lith-Depth-COLUMN-_2D00_-TEXT-VS-DEPTH-PROPERTIES.png"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/283906/Lith-Depth-COLUMN-_2D00_-TEXT-VS-DEPTH-PROPERTIES.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/283906/Lith-Desc-COLUMN-_2D00_-TEXT-VS-DEPTH-PROPERTIES.png"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/283906/Lith-Desc-COLUMN-_2D00_-TEXT-VS-DEPTH-PROPERTIES.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/283906/report-property.png"&gt;&lt;img width="903" height="709" style="width:872px;height:695px;" src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/283906/report-property.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;This is the output&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;a href="/cfs-file/__key/communityserver-discussions-components-files/283906/output.png"&gt;&lt;img src="/resized-image/__size/940x0/__key/communityserver-discussions-components-files/283906/output.png" alt=" " /&gt;&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>