Hi Janet,

The easiest way is to use the built in AASHTO functions on you graph report. There are many ways to implement. Assuming you are using the standard gINT US lab database and library you can use this.

goto report design and pick your grainsize report in the yellow dropdown at the top. Then goto file ..copy page create a new report called Grain size AASHTO (or whatever you feel is appropriate). In the new report double click on the classification entity and open up the text expression box .. Remove what is there and replace it with the following

<<Let(Symbol = _
      <<AASHTO_Symbol(<<SV READINGS.Reading>><<#>>,_
                    <<SV READINGS.Percent_Finer>>,_
                    <<ATTERBERG.Plastic_Limit>>,_
                    <<ATTERBERG.Liquid_Limit>>,_
                    <<ATTERBERG.Organic>>_
      )>>_
)>>_
<<Let(Class = _
        <<AASHTO_Group_Index95(<<SV READINGS.Reading>><<#>>,_
                    <<SV READINGS.Percent_Finer>>,_
                    <<ATTERBERG.Plastic_Limit>>,_
                    <<ATTERBERG.Liquid_Limit>>,_
                    <<ATTERBERG.Organic>>_
        )>>_
)>>_
<<FirstData(<<Lookup(<<LAB SPECIMEN.Description>>,_
                     <<DataSetKey(<<#>>)>>_
            )>>,_
            <<DelimitData("(",<<Get(Symbol)>>,")"<<Get(Class)>>)>>_
)>>

This is just one way! IE you could make another user system data item reference both the ASTM and ASSHTO code in the same expression and trigger it from an input field to pick what classification to use etc...

There are some Agency reports that use AASHTO, IL dot , USDA, OH DOT classification function etc.....

They can be found here

For a complete list of classification systems gINT has functions for in gINT goto Help menu Search Classification of soils

Classification of Soils (lab testing)

Currently gINT supports the following classifications of soils:

• AASHTO

• BSI

• ILDOH

• MNDOT

• OHDOT

• ASTM

• USDA

All the classification functions require expressions for extracting the gradation and Atterberg Limits data.

Generically the function syntax is:

<<Class_Func(
  <<Table.Size (mm) Field>>,_
  <<Table.% Passing Field>>,_
  <<Table.PL>>,_
  <<Table.LL>>_
)>>

The gradation size and percent passing parameters can only be field references:

usually

<<SV READINGS.Reading>> and <<SV READINGS.Percent_Finer>>

or Union functions if used:

usually

<<Union(<<SV READINGS.Reading>>,<<HYD READINGS.Particle_Size>>)>>

and

<<Union(<<SV READINGS.Percent_Finer>>,<<HYD READINGS.Percent_Finer>>)>>

The remaining parameters are usually <<TABLE.Field>> such as:

<<ATTERBERG.Plastic_Limit>> and <<ATTERBERG.Liquid_Limit>>

but can be expressions.

When the classification function is in a repeating text entity on a graph, the syntax is:

<<Class_Func(
  <<Table.Size (mm) Field>><<#>>,_
  <<Table.% Passing Field>>,_
  <<Table.PL>>,_
  <<Table.LL>>,_
  <<other parameters; depending on function>>_
)>>

Note the "<<#>>" after the size parameter.  The repeating text entity converts this to 1, 2, etc.  This tells the program to use the data for the first, second, etc. records associated with the current graph.  When using just <<TABLE.Field>> for the parameters after the size and % passing fields, there is nothing more you need to do.  If you have expressions in these positions, you must tell the function to use the appropriate data for the fields.

For example, you can use one of the following functions for ASTM classifications:

The function syntax for all the above is:

<<ASTM_xxxx(<<TABLE.Size (mm) Field>>,_
  <<TABLE.% Passing Field>>,_
  <<TABLE.PL>>,_
  <<TABLE.LL>>[,_
  <<Organic True/False Expression>>]_
)>>

The Organic True/False expression is optional (indicated by the surrounding [...]). If included and the expression evaluates to True, the soil will be classified as organic, if appropriate according to ASTM D2487.

If the standard Lab Testing tables and fields are used:

<<ASTM_xxxx(<<SV READINGS.Reading>>,_
  <<SV READINGS.Percent_Finer>>,_
  <<ATTERBERG.Plastic_Limit>>,_
  <<ATTERBERG.Liquid_Limit>>,_
  <<ATTERBERG.Organic>>_
)>>

Hello Kirk,

I have a question regarding the following statement:

"IE you could make another user system data item reference both the ASTM and ASSHTO code in the same expression and trigger it from an input field to pick what classification to use etc..."

How can I do this? Can you please help?

Thank you.

Naziur 

Hi Naziur,

For example, you could put a field in your Project table that uses a Lookup List for the Classification method. Lookup list options could be ASTM or AASHTO. 

Then in your classification expression, you could have something along the lines of:

<<(IIf(_

  <<Project.ClassificationMethod>>=AASHTO,

  AASHTO Classification expression goes here...,_

  ASTM Classification expression goes here...._

)>>

(That approach basically makes ASTM the default classification unless AASHTO is selected. If you wanted to include more than 2 classification options, I'd recommend looking into the Case() function.)

Hi Naziur,

For example, you could put a field in your Project table that uses a Lookup List for the Classification method. Lookup list options could be ASTM or AASHTO. 

Then in your classification expression, you could have something along the lines of:

<<(IIf(_

  <<Project.ClassificationMethod>>=AASHTO,

  AASHTO Classification expression goes here...,_

  ASTM Classification expression goes here...._

)>>

(That approach basically makes ASTM the default classification unless AASHTO is selected. If you wanted to include more than 2 classification options, I'd recommend looking into the Case() function.)