Web Content Viewer
Actions

gINT Resources

The ODOT gINT Library, Data Template, and Example Project files are available in the gINT Downloads library.  gINT version 10.00.00.69 or greater is required to use these files.

  • The OH DOT.glb Library File contains data for calculations, data entry lists, and reports.
  • The OH DOT.gdt Template File contains the data base structure for cloning into new Project database files.
  • Example.gpj is an Example Project database file, filled out with an example of typical data.
  • Make a new Project database file, [name].gpj, for each project, and use a unique project identifier for [name].

These files are regularly updated.  When this occurs, we will send out notifications to the gINT email Subscription List.  If you wish to subscribe or unsubscribe to/from the list, please email Alexander Dettloff.

For those who do not have gINT version 10.00.00.69, or do not wish to use the ODOT gINT Library and Template, we are making available the Official ODOT Symbols and Tiles for use in gINT Reports.  These can be incorporated into any gINT Library.  The files under gINT Material Symbols (below) provide examples and definitions of the ODOT gINT Material Symbols.  The following CSV (Comma Separated Values) and DXF (Autodesk Drawing Exchange Format) files contain the exported ODOT gINT Tile definitions for use in constructing the Material Symbols.

gINT DIGGS Compliance

As part of the submission requirements listed in Section 701 of the ODOT Specifications for Geotechnical Explorations, final boring data is to be submitted in an electronic format that is compliant with the Data Interchange for Geotechnical and Geoenvironmental Specialists (DIGGS) standard.  Please note that gINT project files developed using ODOT’s gINT library are an acceptable format as they can be successfully converted to DIGGS format by ODOT.  For more information of DIGGS, visit the Geo-Institute website.

Frequently Asked Questions

The ODOT Office of Geotechnical Engineering made a decision to migrate to gINT software for the generation of Geotechnical Boring Logs in 2006. We had gINT perform a number of modifications to their standard template and perform numerous pieces of custom programming to tailor their software to meet the requirements of the ODOT Specifications for Geotechnical Exploration (SGE), specifically to classify soil and rock by the ODOT (modified AASHTO) method and to produce ODOT standard boring logs.

NOTE: Before checking below for answers to specific issues you may be experiencing, make sure you have the most current copy of the ODOT glNT File Template and Library.

NOTE: gINT version 8.2.004 or greater is required to use these files.  For those who wish to update their gINT version 8 software to version 8.2.004, the gINT version 8 update is available on the gINT Software website.

Alternative split sieve size, rather than standard #10 split sieve, used for Hydrometer

Summary

The standard Hydrometer method per AASHTO T-88 and ASTM D422 is to split at the #10 sieve. There are several alternative methods in T-88, one of which is to split at the #40 sieve. If you choose to use this alternative method, you will have to change the field SIEVE.Size_Split_Sieve from 2 (mm) to 0.425 (mm), and then report the amount passing the #40 sieve and retained for the hydrometer test in the SIEVE.Wt_Passing_Split_Sieve field. You may also wish to change the caption for the SIEVE.Wt_Passing_ Split_Sieve field to make it more user-friendly.

Specific Directions

gINT screenshotGo to the SIEVE table. Assuming you use a #40 split sieve for the hydrometer test, change the value of the Size_Split_Sieve field from 2 to 0.425 for every sample you have split at the #40 sieve. This is the only change to the project database that you need to make. There are no changes to the library required.

When you input data in the SIEVE table Wt_Passing_Split_Sieve field for these samples, instead of reporting the amount passing the #10 sieve and retained for the hydrometer test, report the amount passing the #40 sieve and retained for the hydrometer test. If you want to make it look more user friendly, you could change the caption of the Wt_Passing_Split_Sieve field from "Dry Weight Passing #10" to "Dry Weight Passing #40," or to something else you prefer.

If you want to use the #40 sieve as the split sieve all of the time, you would do best to create a new glNT template file off of your changed project file. In this case, it would be best to change the default value of the SIEVE.Size_Split_Sieve to 0.425, and the caption to the SIEVE.Wt_Passing_Split_Sieve field should be changed to reflect the difference.

NOTE: ODOT does not use the Coarse/Medium/Fine sand as specified for reporting in ASTM D422, but we report Coarse and Fine sand as specified for reporting in AASHTO T-88 (ASTM Coarse Sand equates to AASHTO Fine Gravel, and ASTM Medium Sand equates to AASHTO Coarse Sand.

Gradation for soil sample from Legacy boring log, with no raw Sieve or Hydrometer data

Summary

It is sometimes desirable to re-enter legacy soil data from historic boring logs into gINT, so that a current boring log can be generated in the same format as the other project boring logs. Archived raw laboratory data for sieve and hydrometer readings may not be available for soil samples shown on such historic boring logs. Nevertheless, it is possible to enter the legacy gradation data into gINT, knowing only the final soil particle percentages by weight for Gravel (%GR), Coarse Sand (%CS), Fine Sand (%FS), Silt (%SI), and Clay (%CL).

Specific Directions

gINT screenshotThe percent passing values for the corresponding sieve sizes to Gravel (GR), Coarse Sand (CS), Fine Sand (FS), Silt (SI), and Clay (CL) will have to be calculated from the final soil particle percentages by weight. These are as follows:

  • GR:    2-inch (50 mm) sieve:    percent passing (P2”) = 100%
  • CS:    #10 (2 mm) sieve:    percent passing (P10) = %CL + %SI + %FS + %CS
  • FS:    #40 (0.425 mm) sieve:    percent passing (P40) = %CL + %SI + %FS
  • SI:    #200 (0.075 mm) sieve:    percent passing (P200) = %CL + %SI
  • CL:    5-micron (0.005 mm) sieve:    percent passing (P5μ) = %CL

A new line will need to be entered in the SV_READINGS table, with “0.005” entered under SV_READINGS. Reading, and “5- micron” entered under SV_READINGS. Name. The calculated values for percent passing should then be entered in the field SV_READINGS.Percent_Passing, for the lines labeled 50, 3” to 2” for P2”; 2, #4 to #10 for P10; 0.425, Retained #40 for P40; 0.075, #40 to #200 for P200; and 0.005, 5-micron for P respectively. Nothing should be entered in the field SV_READINGS.Soil_ Tare. Also, nothing is entered in the SIEVE table, the HYDROMETER table, or the HYD_READINGS table.

How do I enter roadway stationing in a gINT Project file?

Summary

Roadway Station for each boring location in the gINT project file is entered in the field <POINT.Station>. This data must be entered in single-precision decimal number format.

Specific Directions

You must enter your stationing in decimal feet format. Fractions of feet are still in tenths, hundredths, etc. to the right of the decimal point. Essentially, you just omit the "+" (plus sign). For example:

Station 100+00 would be entered as 10000
Station 11+18.23 would be entered as 1118.23

How do I put gINT Boring Logs on Plan Sheets?

Summary

The old method of placing Boring Logs on a MicroStation plan sheet was to laboriously draw the entire boring log in MicroStation CADD. We now export our Boring Logs by using the gINT PDF export facility, and then referencing the PDF logs into our sheets with the MicroStation Raster Manager. The ODOT CADD Standards people have arrived at allowing this as a compromise, since the Boring Log is technically a report rather than a drawing.

Specific Directions

In gINT, go to Output, Logs, and select the gINT PDF export facility by clicking on the PDF icon, shown by the red arrow in the image below.

gINT screenshot

gINT will open a dialogue, in which you should navigate to the location where you will store the PDF log files. You may assign a “dummy” name to the log file(s) (such as “boring logs.pdf” in the below example), as the name(s) will change later during export process.

gINT screenshot

The Output pane on the right side of the screen will change to reflect the PDF export. Choose the option “Each dataset to individual file” to put each boring log in an individual PDF file.

gINT screenshot

gINT will then generate each boring log and output it to an individual PDF with a default name the same as the Exploration ID <POINT.PointID>, unless you use a File name expression to name the PDF files.

gINT screenshot

Each PDF log should look similar to the below example.

gINT screenshot

Create a blank sheet in MicroStation CADD.

gINT screenshot

Choose the layer “RS_Raster1” for the import of the first PDF file.

gINT screenshot

Open Raster Manager.

gINT screenshot

Below is an example of the Raster Manager dialogue.

gINT screenshot

Choose “Attach” to attach a raster (PDF) file.

gINT screenshot

Navigate to the file location where the PDF boring logs are stored.

gINT screenshot

Use the cursor to snap to the upper right corner of the sheet border.

gINT screenshot

Drag to place the raster (PDF) file.

gINT screenshot

The PDF boring log (8½” x 11”) should take up half the available width of the sheet.

gINT screenshot

Below is an example of the sheet with one PDF boring log attached.

gINT screenshot

Choose the layer “RS_Raster2” for the import of a second PDF Boring Log file. There is also a layer “RS_Raster3” for if a sheet contains a third raster file.

gINT screenshot

How do I integrate new versions of the ODOT gINT Data Template file with my custom Data Template?

Summary

ODOT will rarely make changes to our gINT Data Template file, but when we do, you will need to download the new version of the Template, and use it for the creation of all new gINT Projects for ODOT. However, we understand that some user-specific information is stored in the Data Template file, in the Project Lookups tables. Conversely, we store ODOT specific information in the Data Template file, in the Project Lookups tables, which may be of no interest to you. The concern is that if you use the new ODOT gINT Data Template file, you will lose all of your user-specific customized information. However, it is possible to merge an old copy of the Data Template file with the newest version of the ODOT gINT Data Template file without losing any user-specific customized information; the merge will merely append new ODOT specific information to the Project Lookups tables. To perform a merge of an old copy of the Data Template file with the newest version of the ODOT gINT Data Template file, follow the steps outlined below under Specific Directions.

Specific Directions

  1. Download the new oh dot.gdt Data Template, and save it to a known location.
  2. Copy your most recent gINT Project File to a second location as a back up.
  3. Open your most recent Project File in gINT.
  4. Go to Utilities, Convert Projects:
  5. Choose the new oh dot.gdt for Data Template and the most recent gINT Project File for Convert Files; you may leave Correspondence File empty.
  6. Press the Execute button. You may get several error messages; ignore these and click OK on the message boxes (or hit Enter on the keyboard). The reason that these error messages occur is that in some of the Lab Testing tables there are required fields which are empty if you have not tested every specimen.
  7. When the Convert Projects completes, a Conversion Complete report will display. Click OK to close the report.
  8. The Convert Projects will create a backup copy of the Project File (prior to conversion to the new template) in the same folder as the *.gpj project file, and with the same name, but a different *.org file extension.
  9. The Convert Projects will append the Project Lookups data from the oh dot.gdt Data Template to your Project File. You may delete this Project Lookups data or keep it, as you prefer.
  10. Go to Data Design, Project Database, and open the Current Project
  11. Go to File>New Data Template>Clone from Current...
  12. Save the new Data Template to your Templates folder, and give it whatever name you prefer (this will be your new Data Template for starting new ODOT projects).

Soil sample sieved through #200 sieve, with no Hydrometer run for classification

Summary

Hydrometer testing is necessary to classify soil samples as ODOT Class A-4a or A-4b, but is not strictly necessary to classify other ODOT Classes. For other ODOT Classes, there is not a requirement for percent by weight silt- or clay-sized particles, but only a requirement for maximum or minimum percent by weight passing the #200 sieve (P200). If you do not run a hydrometer, you will need to sieve down through the #200 sieve to classify the soil sample.

Specific Directions

gINT screenshotIf classifying without the Hydrometer test, and using only P200 instead, do one of the following:

  1. Add the #40 sieve and #200 sieve to the sieve stack, and sieve the entire soil specimen down through the #200 sieve. Enter the weight of soil (in grams) retained on the #40 sieve and the #200 sieve in the field SV_READINGS.Soil_Tare for the lines labeled 0.425, Retained #40 and 0.075, #40 to #200, respectively. Do not enter anything in the SIEVE.Wt_Fines_ Tested or SIEVE.Size_Split_Sieve fields. Without a split sieve size defined, the SIEVE.Wt_Passing_Split_Sieve field will show the amount passing the smallest sieve in the stack (#200 in this case), so if you want to make it look more user friendly, you could change the caption of the Wt_Passing_Split_Sieve field from "Dry Weight Passing #10" to "Dry Weight Passing #200," or to something else you prefer.
  2. gINT screenshotSplit the sieving at the #10 sieve, and measure out a smaller sample (around 100 grams) as if for the Hydrometer test from the material passing the #10 sieve (P10). Sieve the smaller sample through the #40 sieve and #200 sieve. In the SIEVE.Wt_Fines_Tested field, enter the total weight of the smaller sample (in grams). In the SIEVE.Size_Split_Sieve field, enter 2, as in “2 mm,” which is the size in openings of the #10 split sieve. Enter the weight of soil (in grams) retained on the #40 sieve and the #200 sieve in the field SV_READINGS.Soil_Tare for the lines labeled 0.425, Retained #40 and 0.075, #40 to #200, respectively.
  3. If you split the sieving at a different sieve size, you will have to modify the procedure under B. (above). See also the Frequently Asked Question “Alternative split sieve size, rather than standard #10 split sieve, used for Hydrometer” for details on how to change the Split Sieve Size.

The gINT code is capable of calculating the P200 value from the above inputs without running the Hydrometer test. In any of the above cases, do not enter any information for the soil specimen in the HYDROMETER table or in the HYD_READINGS table. The P200 value will be output on the STANDARD ODOT SOIL BORING LOG (8.5 X 11) or STANDARD ODOT SOIL BORING LOG (11 X 17) in-between the columns for GRADATION (%) SI and GRADATION (%) CL, with dashes (-) on both sides to indicate that the specific percents of silt and clay are not known.

What are the ODOT gINT reports used for?

Summary

When the gINT Software package was delivered to ODOT, we contracted with gINT Software to modify the standard features of the gINT library and project database, and to create a certain number of new report forms which were not included in the original gINT Software package, in order to meet the needs of ODOT. Subsequent to this, developers at ODOT have created several additional new reports. Several existing reports (not currently used by ODOT) have been left in the ODOT gINT library, pending future review, and evaluation of their usefulness to the needs of ODOT.

Specific Directions

The following ODOT gINT reports are approved to be used for ODOT projects:

Logs, STANDARD ODOT SOIL BORING LOG (8.5 X 11)
This is the standard ODOT boring log sized for an 8½”x11” (Letter-sized) sheet of paper, suitable for binding in a Report of Geotechnical Exploration, Findings, and Recommendations, per Specifications for Geotechnical Explorations (SGE) Section 705 (Geotechnical report), or for insertion into sheets for a Structure Foundation Exploration (SFE) or GeoHazard Exploration for borings of around 30 feet or less in depth.

Logs, STANDARD ODOT SOIL BORING LOG (11 X 17)
This is the standard ODOT boring log sized for an 11”x17” sheet of paper, suitable for binding in a Geotechnical report, per SGE Section 705, or for insertion into sheets for a SFE or GeoHazard Exploration for borings of greater than 30 feet in depth.

Text Tables, GEOPAK REPORT
This report creates a comma delimited file for generating borehole data in MicroStation Geopak.

Text Tables, SUMMARY OF SOIL TEST DATA
This report creates a text table that can be exported to a Microsoft Excel spreadsheet, which can then be inserted into the cover sheet or following sheets of a Soil Profile, per SGE Section 702, as a Summary of Soil Test Data, with slight modifications: the Explor. ID, Station, Offset, Lat/North, and Long/East fields are repeated for every sample in each boring, but should only appear once per boring; these should also be reconfigured into four lines of data to the left of each boring in the Summary of Soil Test Data. The Lat/North and Long/East fields contain either latitude-longitude or northing-easting boring location data, and should be renamed appropriately. See SGE Appendix D for an example of the correct formatting of the Summary of Soil Test Data in a Soil Profile.

Text Tables, WET NON-PLASTIC
This report creates a text table formatted in the same way as the SUMMARY OF SOIL TEST DATA report. Each line of this report identifies a sample from the Summary of Soil Test Data which satisfies the requirements of SGE Section 702.6.3.i, and should have the open circle with a horizontal line placed next to the soil sample in the Graphical Boring Logs.
 
Text Tables, WET PLASTIC
This report creates a text table formatted in the same way as the SUMMARY OF SOIL TEST DATA report. Each line of this report identifies a sample from the Summary of Soil Test Data which satisfies the requirements of SGE Section 702.6.3.h, and should have the solid black circle placed next to the soil sample in the Graphical Boring Logs.

Text Tables, WET VISUAL NON-PLASTIC
This report creates a text table formatted in the same way as the SUMMARY OF SOIL TEST DATA report. Each line of this report identifies a sample from the Summary of Soil Test Data (which has ONLY been VISUALLY classified) which is estimated to satisfy the requirements of SGE Section 702.6.3.i. The report does this by comparing the water contents of the visually classified samples which may be non-plastic (A-1-a, A-1-b, A-2-4, A-3, A-3a, A-4a, or A-4b), with requirements of SGE Section 702.6.3.i. There may be some overlap in this report with the WET VISUAL PLASTIC report for visually classified A-1-a, A-1-b, A-3a, A-2-4, A-4a, and A- 4b samples, which could be either plastic or non-plastic. The user will have to use engineering judgment to determine if the visually classified samples are similar to other mechanically classified samples, and decide whether the samples should be considered plastic or non-plastic for the purposes of satisfying the requirements of SGE Section 702.6.3.h and 702.6.3.i.

Text Tables, WET VISUAL PLASTIC
This report creates a text table formatted in the same way as the SUMMARY OF SOIL TEST DATA report. Each line of this report identifies a sample from the Summary of Soil Test Data (which has ONLY been VISUALLY classified) which is estimated to satisfy the requirements of SGE Section 702.6.3.h. The report does this by comparing the water contents of the visually classified samples which may be plastic with the AVERAGE LL of similar samples across the project, to estimate if the visually classified samples satisfy the requirements of SGE Section 702.6.3.h. There may be some overlap in this report with the WET VISUAL NON-PLASTIC report for visually classified A-1-a, A-1-b, A-3a, A-2-4, A-4a, and A-4b samples, which could be either plastic or non-plastic. The user will have to use engineering judgment to determine if the visually classified samples are similar to other mechanically classified samples, and decide whether the samples should be considered plastic or non-plastic for the purposes of satisfying the requirements of SGE Section
702.6.3.h and 702.6.3.i.

Text Docs, SOIL PROFILE LEGEND
This report creates a text table that can be exported to a Microsoft Excel spreadsheet, which automatically sums up the visually and mechanically classified samples in a gINT project file for inclusion in the Legend on the cover sheet of a Soil Profile report per SGE Section 702.3.2.c (this same Legend is used on the cover sheets of Structure Foundation Exploration and GeoHazard Exploration reports).   The report also calculates the average group index per ODOT Soil Class.

Other gINT Reports
No other reports in the ODOT gINT library should be included as part of Geotechnical deliverables for ODOT projects, although consultant users are free to use these report forms for their own purposes. See also the Frequently Asked Question “Why do some of the reports in the ODOT gINT library include USCS Classifications?” for more information about the existing unapproved reports.

Why do some of the reports in the ODOT gINT library include USCS Classifications?

Summary

ODOT does not use or accept USCS classification of soil specimens. ODOT requires classification of soil specimens by the ODOT (modified AASHTO) Soil Classification Method per the requirements of the ODOT Specifications for Geotechnical Explorations (SGE), Section 603.

When the gINT Software package was delivered to ODOT, it contained standard features and report forms used by many of gINT Software’s customers. The existing reports included USCS classification of soil specimens, as well as other features not applicable to ODOT practices. ODOT contracted with gINT Software to modify the standard features of the gINT library and project database to meet the needs of ODOT and to create a certain number of new report forms; however, we left many of the existing report forms in the library. We have not had time to evaluate all of the existing report forms, but plan to do so in the future. Once we evaluate the existing forms, we may generate similar new forms, incorporating ODOT (modified AASHTO) Class and features specific to ODOT practices; if we decide the existing report forms are not useful to the needs of ODOT, we may decide to delete these forms without replacing them; we are also likely to generate a number of other new report forms, or contract with gINT to generate them, as we continue to evaluate our needs.

For the time being, the existing gINT reports are being left in the ODOT gINT library; however, we do not advocate the use of these reports, nor do we approve of their use as part of Geotechnical deliverables for ODOT projects.

Specific Directions

The following are the ONLY reports in the ODOT gINT library that are approved to be used for ODOT projects:

  • Logs, STANDARD ODOT SOIL BORING LOG (8.5 X 11)
  • Logs, STANDARD ODOT SOIL BORING LOG (11 X 17)
  • Text Tables, GEOPAK REPORT
  • Text Tables, SUMMARY OF SOIL TEST DATA
  • Text Tables, WET NON-PLASTIC Text Tables, WET PLASTIC
  • Text Tables, WET VISUAL NON-PLASTIC Text Tables, WET VISUAL PLASTIC
  • Text Docs, SOIL PROFILE LEGEND

No other reports in the ODOT gINT library should be included as part of Geotechnical deliverables for ODOT projects, although consultant users are free to use these report forms for their own purposes.

If consultants generate their own report forms, these forms may be included as part of Geotechnical deliverables for ODOT projects, as long as these forms satisfy the requirements of the SGE.