Applies To Product(s): gINT Logs, gINT Professional, gINT Professional Plus Version(s): N/A Environment: N/A Area: Export Data Subarea: Original Author: Kathleen Holcomb, Bentley Technical Support Group Data Modeling Data modeling is taking information and looking at it in different ways. A report is a form of data modeling, because it is a representation of data that can take on various output styles. Data modeling extrapolates data, meaning that in addition to displaying the data, it makes an “interpretation” of some kind. One form of modeling is taking your data points and creating contoured surfaces. If you have a series of discrete points on your site, you can compile the data and try to read the patterns in between the data points. gINT has some basic modeling capabilities which we will review later, but it is not a modeling program. However, it can interface with programs that are. Contouring and Modeling Data using gINT and Rockworks® RockWorks® is a modeling and contouring program that offers tools for visualizing and modeling surface and sub-surface data. Rockworks uses a highly specialized input file format to import data from programs such as gINT. In particular, Rockworks employs certain tables and fields that do not have direct analogs in gINT, and employs concepts of “point” data (data at specific depths such as CPT data) and “interval” data (data corresponding to a range of depths such as sample and lithology data). Performing this conversion requires the creation of a fairly complex correspondence file, but once created, does not need to be modified. Consult the Rockworks documentation for instructions on how to import and manipulate the data. We will only briefly describe some of the capabilities. (For more information about Rockworks, please visit RockWare’s Web site at www.rockware.com .) After import, the data looks as follows in the RockWorks Borehole Manager: Notice the tabs for various data tables corresponding to the structure we created in the export file. The following screen capture shows a model of chemical concentrations from PID data. Increasing concentration is represented with colors further from the purple and closer to the red end of the spectrum. Notice the site map and borehole numbers overlaid at the top. By modeling specific PID ranges only, a clearer view of the high concentration areas is revealed: See Also For a complete discussion of the requirements of Rockworks input file format, and how to use DATA DESIGN- Correspondence Files to create a correspondence file for RockWorks export, see Help- Index- Exporting to a RockWorks File .
↧
Wiki Page: Contouring and Modeling Data Using gINT and Rockworks
↧
Wiki Page: Variable Graphic Log Report Legend
Applies To Product(s): gINT Logs, gINT Professional, gINT Professional Plus Version(s): N/A Environment: N/A Area: Report-Log Subarea: Original Author: Kathleen Holcomb, Bentley Technical Support Group A variable legend entity creates a legend displaying the material, sampler, well or other symbols in use in a single log. This is a useful visual aid on a report. The legend is called variable because the set of symbol boxes that appears will vary from log to log depending on which symbols are in use. Note: This exercise requires the use of training.GPJ project and training.GLB library available from: download.aspx . Instructions for unzipping and setting up these files is on: using gint downloaded examples.aspx . Variable Graphic Log Report Legend First we create the log, which will have a legend for sampler graphics. Ensure that the current library is training.glb . Go to REPORT DESIGN- Logs . In the object selector select SIMPLE LOG (or FINAL SIMPLE LOG if SIMPLE LOG is missing or incomplete). Select File- Copy Page . Enter the following, then click OK : Field Value Page Name to Copy To SIMPLE LOG WITH LEGEND Set Current Page To First in Copy To List We need to create a footer for the legend, and shorten the body height (where column entities reside) to make room for the footer. Click the Properties icon, then select the Report Structure tab. Enter the following: Field Value Page 1 Body Height 7.5 Page 1 Footer Height 0.5 We only make these changes for Page 1. On subsequent pages the legend will not appear. Select the Columns and Lines tab. Check the Bottom of Body checkbox. Click OK to close the Properties window. Select Log- Variable Legend . The VARIABLE LEGEND PROPERTIES window appears. Enter the following in the Main tab: Field Value Comments Field with Data SAMPLE.Type The field containing symbol names. Its values determine which symbol graphics print. Use the Data Tool. Symbol Type Sampler Graphics Determines which kind of symbol is displayed in the legend. Number of Rows 1 One row of symbols will appear in the legend (we have limited vertical space, and there will be few sample graphics per log). Row Spacing 0.1 Ignored in a 1-row legend. No. of Columns 5 Maximum number of columns of symbols displayed. Note that num_of_columns x column_spacing should be the width of the report body, 6" in this case. Column Spacing 1.2 Distance from the start of one symbol to the start of the next. Can also be thought of as column width. Rectangle Height 0.4 Rectangle height of each symbol. Rectangle Width 0.15 Gap Between Descriptions and Rectangles 0.05 Distance from the right edge of each rectangle to the left edge of its description. Text Height 0.08 Character size of description text. X 0.05 X coordinate of legend alignment point (which is at upper left corner of legend) Y 0.45 Y coordinate of alignment point. Go to the Configuration tab. Enter the following: Field Value Comments Output Condition Pg =1 Restricts display of the legend entity to page 1. Use the Data Tool (right half) to paste the Pg system data item. Go to the Symbol Descriptions tab. Enter the following: Field Value Comments Name and/or Description Description Specifies what (from the Symbol record) will appear next to each symbol. Click OK . The variable legend entity is added to the report. Go to OUTPUT , select training.gpj and preview the report. Notice the legend at the bottom. Close the preview. See Also
↧
↧
Wiki Page: Variable Graphic Fence Report Legend
in progress Applies To Product(s): gINT Professional, gINT Professional Plus Version(s): N/A Environment: N/A Area: Report-Fence Subarea: Original Author: Kathleen Holcomb, Bentley Technical Support Group A variable legend entity creates a legend displaying the material, sampler, well or other symbols in use all the boreholes on a fence report. This is a useful visual aid on a report. The legend is called variable because the set of symbol boxes that appears will vary from fence to fence, depending on which symbols are in use. Note: This exercise requires the use of training.GPJ project and training.GLB library available from: download.aspx . Instructions for unzipping and setting up these files is on: using gint downloaded examples.aspx . Variable Graphic Fence Report Legend We will create a material graphic legend for a fence report. In a fence report, a legend displays all symbols used of the specified type (material in this case) in all boreholes of the report. Do the following: Go to REPORT DESIGN- Fences . In the object selector select SIMPLE FENCE (or FINAL SIMPLE FENCE if SIMPLE FENCE is missing or incomplete). Select File- Copy Page . Enter the following, then click OK : Field Value Page Name to Copy To SIMPLE FENCE WITH LEGEND Set Current Page To First in Copy To List Some modifications are required to the data frame layout. Click the Properties icon. The FENCE REPORT PROPERTIES window appears. In the Data Frame tab, enter the following settings: Field Value Comments Frame Y 0.95 Elevates the frame bottom by .45" to make room for the legend. Frame Height 5.25 Shortens the frame by .25" so it doesn't run into the header. Click OK to save the property changes. Double-click on the ‘Distance Along Baseline (ft)’ entity. The TEXT PROPERTIES window opens. In the Main tab, enter the following, then click OK : Field Value Comments Y 0.7 Elevates the text entity by .6" to keep it just beneath the elevated data frame. Select Fence- Variable Legend . The VARIABLE LEGEND dialog box appears. Enter the following values: Field Value Comments Field with Data LITHOLOGY.Graphics The data source will be the Graphic field in the LITHOLOGY table. Use the Data Tool. Symbol Type Material Graphics The legend will collect all material symbols used in the fence report. Number of Rows 1 We use a single-row legend to avoid having to compress the data frame too much. Row Spacing 0.4 Ignored in a single-row legend. Number of Columns 10 A maximum of 10 symbols can be displayed. To increase this we would have to narrow the column spacing or add a row. Column Spacing 1 Distance from the start of one symbol to the start of the next. Can also be thought of as column width. Rectangle Height 0.4 Rectangle height of each symbol. Rectangle Width 0.2 Gap between Descriptions and Rectangles 0.05 Distance from the right edge of each rectangle to the left edge of its description. Text Height 0.08 Character size of description text. X 0.05 Alignment point is .05" to right of the report border. Y 0.5 Alignment point is .5" above the report border. This allows room for the .4" high graphic rectangles and a reasonable amount of text. Click OK to save the legend properties. Go to OUTPUT- Fences , select training.gpj and preview the report. (Cancel the User Report Variables window if desired.) The report appears as shown: Close the preview. See Also Variable Graphic Log Report Legend: (Please visit the site to view this file)
↧
Forum Post: RE: Set decimal separator
Dear David, Thank you for your reply. Unfortunately, I do not have this option, which is interesting. Would you know the cause for this? Thank you! Tina
↧
Forum Post: AGS PTIM export
Hi all. I have just finished exporting quite a large gINT project to AGS (all fine, no errors picked up by the AGS checker) Upon opening the AGS file to do a quick visual chec, I came acros the PTIM table and noticed that the PTIM_DATE and PTIM_TIME columns have incorrect units assigned to them. PTIM_DATE units should be dd/mm/yyyy and PTIM_TIME units should be hhmm, yet in my exported AGS file they are both dd/mm/yyyy hhmmss:- "**PTIM" "*HOLE_ID","*PTIM_DATE","*PTIM_TIME","*PTIM_DEP","*PTIM_CAS","*PTIM_WAT","*PTIM_REM" " UNITS ","dd/mm/yyyy hhmmss","dd/mm/yyyy hhmmss","m","m","m","" This is wrong on a number of counts... Firstly, in the target File in my correspondence file the PTIM table looks like this:- "**PTIM" "*HOLE_ID","*PTIM_DATE","*PTIM_TIME","*PTIM_DEP","*PTIM_CAS","*PTIM_WAT","*PTIM_REM" " UNITS ","dd/mm/yyyy","hhmm","m","m","m","" As you can see, the 2 fields have the correct units, so why is gINT changing (or disregarding) these units when compiling the AGS file? I have formatted the individual field entries in the correspondence file ( Format( PTIM.DateTime ,dd/mm/yyyy) & Format( PTIM.DateTime ,hhmm) ) so gINT is exporting the data correctly so that part isn't a problem. It appears that gINT is using the Source File units (as it has to take the 2 target field contents from the same source field) to "unit" the 2 Target fields, as in my Target file, the PTIM_DateTime field has units of dd/mm/yyyy hhmmss. Any idea as to why gINT is doing this? Also, why isn't this being picked up by the AGS checker as the units aren't right for the AGS structure? Miles
↧
↧
Forum Post: Output doesn't seem to be using system resources correctly
Hi all (again). This is an issue I've had for a number of years, and I just haven't bothered to report it, but the large job I'm working on now has meant that this has become a real pain.. We have a Core photo log, 2 landscape photos per page to output the core photography from a table holding BItmap field types, also a Trial Pit log with 2 photos per page on "extra" pages (max of 4 photos / 2 extra pages) These both work fine, untill you try to output a whole run of core photos, or all the trial pits in one go, at which point gINT gets so far and then just sits there with the Exporting window saying "Building BH#### (log # of #)" and does nothing else untill you have to Ctrl+Alt+Dle and end process on gINT8.exe to close gINT or it comes up with the following type error message:- "Unable to output Cannot open database ". It may not be a database that your application recognizes, or the file may be corrupt. Entity type Text, X=130.2875, Y=254.5588 (OutputAppLog.OutOneLog OutputAppLog.OutputLogCurr OutputAppLog.OutputHeadreFooter OutputGraphicsPass2.OutputPass2 OutputGraphicsPass2.TextEntityEval GIDSave.SaveEntity: DAO.Recordset) OK" Usually it just sits there and sulks. What I'm having to do is to output just a few BH worth of core photos at a time to a PDF and then keep appending to it, till I've managed to output them. Interestingly if you watch Task Manger whilst gINT is outputting, its memory usage doesn't go much over 270MB and CPU usage doesn't go much over 5%. The same happens with outputting the TP logs with photos. Our engineers can manage to output approx 10 - 14 logs (with just 2 photos on the Additional pages) on their normal PCs, and I can manage maybe 20 on my twin Xeon, 16GB Ram workstation??? It does output the PDF to the last complete BHs woth of photos. Miles
↧
Forum Post: RE: Output doesn't seem to be using system resources correctly
Hi Miles, I see that you also submitted a service request through Bentley Technical Support. I will handle the issue through the Service request and contact you privately for more details, files and pictures. Once the issue has a resolution I will post that in the forum. Thanks, Kirk Johnson
↧
Forum Post: RE: AGS PTIM export
Hello Miles, Is this for AGS 3.1. or AGS 4?
↧
Wiki Page: Report-Graphic Text Doc - gINT Professional
↧
↧
Wiki Page: Variable Graphic Legend Showing All Material and Sampler Graphics Used in a Project
Applies To Product(s): gINT Professional Version(s): N/A Environment: N/A Area: Report-Graphic Text Doc Subarea: Original Author: Kathleen Holcomb, Bentley Technical Support Group A variable legend entity creates a legend displaying the material, sampler, well or other symbols in use in a single log, all boreholes on a fence report, or throughout a project (displayed in a graphic text doc). This is a useful visual aid on a report. The legend is called variable because the set of symbol boxes that appears will vary from log to log or fence to fence, depending on which symbols are in use. To show the symbols in use in a project we will create two Graphic Text Doc reports, one in landscape and one in portrait orientation. Each will include two legends, one for material and one for sampler graphics. Then we will demonstrate how to specify the order of symbols. Note: This exercise requires the use of training.GPJ project and training.GLB library available from: download.aspx . Instructions for unzipping and setting up these files is on: using gint downloaded examples.aspx . Variable Graphic Legend Showing All Material and Sampler Graphics Used in a Project Go to File- Change Library . Select training.glb and click Open . In REPORT DESIGN , select the Graphic Text Docs tab. Click the New icon or select File- New . The ‘New...’ dialog box appears. In the General tab, click Reset , then enter the following: Field Value Comments Name SIMPLE LEGEND Name that appears in the report object selector Description Legend of material and sampler graphics used Left Margin 0.6 Bottom Margin 0.425 Page Size Letter Orientation Portrait Template data entry.gdt Key Set Project Specifies the level at which data is consolidated Click OK . The empty report is created. We will use the TITLE PORTRAIT block from the Drawing Library to create borderlines and header text. Select Blocks- Insert Block . In the BLOCK PROPERTIES dialog box, click Reset then enter the following: Field Value Comments Block Source Dwglib!title portrait Click the Browse icon, select a Type of ‘DWGLIB’ and a Block of ‘TITLE PORTRAIT’. Design Mode Color Very Light Red Color in REPORT DESIGN for the block insert and contents. X -2 X coordinate of alignment point for block insert. No effect on output. Y 8.5 See X. Click OK . The report needs a title. Select Draw- Text- Text or click the Text icon, click Reset , then enter the following: Field Value Comments Text Expression PROJECT SYMBOL LEGEND Height 0.14 Character size of description text. Horizontal Alignment Right Vertical Alignment Top X 7.5 Y 10.1 Click OK . We need a centered title above the first legend, which is for Material graphics. Select Draw- Text- Text or click the Text icon, click Reset , then enter the following: Field Value Text Expression Material Graphics Height 0.14 Horizontal Alignment Center Vertical Alignment Top X 3.8 Y 8.85 Click OK . Next we create a variable legend for material graphics. Select Graphic Text- Variable Legend , click Reset , then enter the following: Field Value Comments Field with Data LITHOLOGY.Graphic Source field for symbols. Use the Data Tool. Symbol Type Material Graphics Type of symbol to display. Number of Rows 4 Four rows of symbols. Row Spacing 0.6 Row height. Needs to exceed rectangle height by some small distance for spacing. Number of Columns 6 Six columns of symbols. Column Spacing 1.25 Width of each column. Fill Order By Row Symbols populate the legend from left to right. Rectangle Height 0.4 Symbol rectangle height. Rectangle Width 0.4 Symbol rectangle width. Gap Between Descriptions and Rectangles 0.04 Text Height 0.08 X 0.06 Y 8.6 Go to the Symbol Descriptions tab and specify the following: Field Value Comments Name and/or Description Name: Description Specifies whether the Name (symbol code), Description or both appear, and if both, in what format. We’re printing the code first, then a colon, then the description. Click OK. To add a centered title above the sampler graphics legend, select Draw- Text- Text or click the Text icon, click Reset , then enter the following: Field Value Text Expression Sampler Graphics Height 0.14 Horizontal Alignment Center Vertical Alignment Top X 3.8 Y 6.0 Click OK . To create a variable legend for sampler graphics, select Graphic Text- Variable Legend , click Reset , then enter the following in the Main tab: Field Value Field with Data SAMPLE.Graphic Symbol Type Sampler Graphics Number of Rows 2 Row Spacing 0.6 Number of Columns 6 Column Spacing 1.25 Fill Order By Row Rectangle Height 0.4 Rectangle Width 0.4 Gap Between Descriptions and Rectangles 0.04 Text Height 0.08 X 0.06 Y 5.75 Go to the Symbol Descriptions tab and specify the following: Field Value Name and/or Description Name: Description Click OK. Go to OUTPUT- Graphic Text Docs and preview the result. Close the preview. Portrait Orientation A useful variant is the vertical project symbol report. To create this, do the following: Go to REPORT DESIGN- Graphic Text Docs . Select File- Copy Page . Name the copy ‘SIMPLE VERTICAL LEGEND’. Double-click the ‘Material Graphics’ text entity, change the following values, then click OK : Field Value Horizontal Alignment Left X 0.06 Double-click the ‘Sampler Graphics’ text entity, change the following values, then click OK : Field Value Horizontal Alignment Left X 3.8 Y 8.85 Double-click the material graphics variable legend entity, change the following values, then click OK : Field Value Number of Rows 14 Number of Columns 2 Column Spacing 1.5 Fill Order By Column X 3.8 Y 8.6 Go to Output- Graphic Text Docs and preview the report. Close the preview. Symbol Legend Positions The Variable Legend entity in logs, fences, and graphic text documents, by default, prints the symbols in the order that they were encountered in the output. You can override this default behavior for sampler, material, well and/or general symbols using the Symbol Legend Positions feature in SYMBOL DESIGN , which enables you to assign rankings to symbols for display in legends. For example, you might want to order material symbols to show gravel symbols first, followed by sand, silt, clay, rock, and all others. To do this you would assign an integer to all gravels you use, a higher integer for all sands, and so on. You can skip values. It is only the relative values that are important, that is, 5 will sort before 8 and it doesn't matter that there are no 6 or 7 values. Also, you can have multiple symbols with the same legend position values, and symbols with unspecified values are placed at the end of the list. We’ll assign the following values to material symbols used in our project: Code Description Legend Position CL USCS Low Plasticity Clay 4 CLS USCS Low Plasticity Sandy Clay 4 GW-GC USCS Well-graded Gravel with Clay 1 ML USCS Silt 3 SANDSTONE Sandstone 5 SC USCS Claey Sand 2 SILTSTONE Siltstone 5 SM USCS Silty Sand 2 SP USCS Poorly-graded Sand 2 To demonstrate the feature, do the following: Go to SYMBOL DESIGN and select the Material tab. Select File- Symbol Legend Positions . The Symbol Legend Positions dialog box appears. Enter the legend position values in the corresponding rows from the list above, then click OK . Go to OUTPUT- Graphic Text Docs . Preview the output. The material symbols are now in gravel-sand-silt-clay-rock-other order. Close the preview. See Also Variable Graphic Log Report Legend: 12406.variable graphic log report legend.aspx Variable Graphic Legend Showing All Material Graphics Used on a Fence: 12407.variable graphic legend showing all material graphics used on a fence.aspx
↧
Forum Post: RE: AGS PTIM export
Sorry Kathleen, should have stated in my post. It's 3.1
↧
Forum Post: RE: AGS PTIM export
Hi Miles Your gcx needs to use the FieldUnits function. This is an excerpt from the Datgel DGD gINT Files PTIM,PROGRESS HOLE_ID, PROGRESS.PointID PTIM_DATE," Format( PROGRESS.DateTime ,dd/mm/yyyy) FieldUnits(""dd/mm/yyyy"") " PTIM_TIME," Format( PROGRESS.DateTime ,hhmm) FieldUnits(""hhmm"") " PTIM_DEP," Format( PROGRESS.Hole_Depth ,0.00) " PTIM_CAS," Format( PROGRESS.Casing_Depth ,0.00) " PTIM_WAT," Format( PROGRESS.Water_Depth ,0.00) " PTIM_REM, PROGRESS.Remark
↧
Forum Post: RE: AGS PTIM export
gINT can't simply always use the units in the AGS Format 3.1 UK document, because some users wish to use different units.
↧
↧
Forum Post: RE: Set decimal separator
You must be using an older version of gINT. Ensure windows is configured to use "." as the decimal place and "," for thousands.
↧
Forum Post: RE: Output doesn't seem to be using system resources correctly
I found the temp gdw file can get too big and make an error. If you have one very deep borehole then try the option on the output screen to define the page range, and break up the output in to batches.
↧
Wiki Page: How To Make A Copy Of An Existing Report Template
How To Make A Copy Of An Existing Report Template Launch gINT using the appropriate project and library file. Go to the Report Design tab. From the yellow Template selector, select the desired Report template of which you want to make a copy of. Go to File Menu. Select Copy Page . A Copy page property dialogue box opens up. In the yellow box, type in the desired name of the copy page report template what it would be named as. The ‘Set Current Page To’ filed must be set to ‘First in Copy to List’. Click OK. You will see the new copy page name in the yellow report selector. The original report template would also be listed in the drop down menu . You can create copies of the report templates for gINT Logs, Fences, Graphs, Histograms, Graphic Tables, Text Tables, Graphic Text Docs, Text Docs and Site Maps.
↧
Forum Post: RE: Set decimal separator
Hi Tina, If you would like to contact me privately we could look at your Bentley account to see what version of gINT you are eligible to use and the current version of gINT you have installed. The Input feature I described was added quite some time ago. Please e-mail me at kirk.johnson@bentley.com Thanks, Kirk Johnson Technical Support Bentley Systems, Incorporated
↧
↧
Wiki Page: Geotechnical - Wiki
This Wiki is a resource for examples, articles, videos and FAQs for Bentley Geotechnical products, principally gINT. Downloads: Free Reports and Examples includes: [[AGENCY REPORTS]] [[General Purpose Report Examples]] [[gINT Rules Samples]] [[gINT Standard Lab Testing Reports]] [[Specialty Applications for gINT]] [[Symbol Libraries for gINT]] AGS Support : [[gINT AGS 4 Files]] [[gINT AGS Version 3 Support]] AGS Toolkit for AGS 4 and AGS 3.1 gINT Civil Tools [[gINT Civil Tools Disclaimer]] Introducing_gINT_Civil_Tools.pdf gINT Civil Tools recording gINT Civil Tools dataset gINT Civil Tools free download Live and OnDemand eSeminars Additional Resources : [[How-To FAQs]] [[Troubleshooting]] [[Videos on gINT Topics]] Technical [[gINT White Papers|White Papers]] Brief descriptions of [[Things You Can Do in gINT]]
↧
Forum Post: RE: AGS PTIM export
Phil, Many thanks for that, I didn't know that the FieldUnits function existed! In my opinion, that's not good behavior of gINT. If you are exporting to a target file format, gINT should keep target field units unless told to do otherwise, or at least alert you to the fact that it isn't going to honor the field units of the target... maybe that's just me :-) Anyway, thanks again
↧
Forum Post: RE: Output doesn't seem to be using system resources correctly
Phil, that's the point of my post (and submission to tech support) 2 reasons. 1. Maximum file size under NTFS file system is 16TB, there's no way gINT is generating a 16TB temp file... I've got a paltry 250GB free on my C drive, plenty of space for creating a temp file way larger than gINT would generate outputting thousands of photo logs. 2. I'm not sure it's to do with temp file size, as I think that gINT dumps the temp file to PDF (I PDF all output and print from that, if paper output is required at all) after the successful completion of each Points worth of data. I say this because gINT still manages to generate all the photo logs in the specified PDF, up to the hole where I get the error message or gINT just goes into a sulk. It would make no programming sense to generate a massive temp file, create content from it periodically but keep that content in the temp file? gINT is only using a tiny amount of memory (270MB ish) and very little processor power (5%) whilst generating the logs and I'm intrigued to know why it's falling over using such a small amount of resources when I've got 12 GB ram free and another 15 processor cores it's not using at all! I do indeed get around this by appending to the PDF with 5 or so holes worth of core photos, it's just a pain to have to do this when my PC is more than capable of outputting all of them in one go :-(
↧