Practical Guidance

Point Load Test

Australian practice is for the logger to conduct Is(50) tests on rock core under field (not lab) conditions. The RPLT table is for Is(50) tests under lab conditions and it is cumbersome to create this data for field tests. So to make this better match Australian practice we created IPLT for Is(50) conducted under field conditions. IPLT has key headings LOCA_ID, IPLT_DPTH and IPLT_TESN.

Is a core run a sample?

Now we have created IPLT, the answer is much easier to give. A core run is not a sample. Create a SAMP record for sections of core that are sent to the lab, often these would be preserved and noted as such in SAMP_PREP.

What SAMP_TYPE should be used for samples from a SPT split spoon?

Most commonly it is D. It is very uncommon in Australia to use a liner, so SPTLS is unlikely.

Do we need to put a value in every heading on a row of a group?

Unless the Status of a heading is R, a heading can be empty. Generally there is no requirement to provide a value for every heading, and data receivers should not ask for such. Headings like LOCA_ID and Depth fields should normally be populated.

Do Headings or Groups that are not used need to be included in an AGS file?

Apart from a few required Groups and Headings, there is no need to include headings and groups that have no data.

Which Headings should be used for 3 interval SPTs?

Use 1, 3 and 5 headings.

Using abbreviations which conflict with those from the standard

The AGS file must use the abbreviations that are defined in AGS 4.1.1 AU if one exists for that thing. You can use new abbreviations if there isn't an existing code for that thing.

This is a data interchange format, so everyone needs to be talking the same language at the time of interchange. You can use other codes in your internal processes, just convert them when you export AGS format data.