Schema documentation for component diggs:RapidLoadTest

An axial compressive force-pulse (rapid) load test applied directly to a deep foundation element, per ASTM D7383 or EN ISO 22477-10. The loading lasts tens to a few hundred milliseconds, between the seconds-to-minutes timescale of diggs:StaticLoadTest and the millisecond-or-shorter timescale of diggs:DynamicLoadTest, and the measured force pulse needs an inertial and damping correction (analysisMethod) to give a load-settlement response. EN ISO 22477-10 classifies a rapid test by purpose, as an investigation test (a sacrificial pile loaded to the ultimate limit state) or a control test (a working pile loaded to a specified load above the serviceability limit state); ASTM D7383 does not name the distinction, so give testCategory where it applies and leave it out otherwise. The two named analysis methods, the Unloading Point Method and its modified form, are used by the practitioner communities of both standards.

<diggs:RapidLoadTest gml:id="" xmlns:diggs="http://diggsml.org/schemas/3" xmlns:gml="http://www.opengis.net/gml/3.2">
  <gml:description xlink:href="" nilReason="">{0,1}</gml:description>
  <gml:identifier codeSpace="">{0,1}</gml:identifier>
  <gml:name codeSpace="">{0,unbounded}</gml:name>
  <diggs:internalIdentifier codeSpace="">{0,1}</diggs:internalIdentifier>
  <diggs:status codeSpace="">{0,1}</diggs:status>
  <diggs:implementationStatus codeSpace="">{0,1}</diggs:implementationStatus>
  <diggs:associatedFile xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:associatedFile>
  <diggs:role>{0,unbounded}</diggs:role>
  <diggs:remark>{0,unbounded}</diggs:remark>
  <diggs:testProcedureMethod xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:testProcedureMethod>
  <diggs:testProcedureEquipment xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:testProcedureEquipment>
  <diggs:testingEnvironment xlink:href="" nilReason="" owns="false">{0,unbounded}</diggs:testingEnvironment>
  <diggs:otherTestProperty>{0,unbounded}</diggs:otherTestProperty>
  <diggs:testEvent>{0,unbounded}</diggs:testEvent>
  <diggs:referenceSystem>{0,1}</diggs:referenceSystem>
  <diggs:maxTestLoad howDetermined="" qualifier="" uom="">{0,1}</diggs:maxTestLoad>
  <diggs:increment>{0,unbounded}</diggs:increment>
  <diggs:maxTestStress howDetermined="" qualifier="" uom="">{0,1}</diggs:maxTestStress>
  <diggs:deadLoad howDetermined="" qualifier="" uom="">{0,1}</diggs:deadLoad>
  <diggs:testCategory>{0,1}</diggs:testCategory>
  <diggs:pulseDuration howDetermined="" qualifier="" uom="">{0,1}</diggs:pulseDuration>
  <diggs:analysisMethod>{0,1}</diggs:analysisMethod>
</diggs:RapidLoadTest>

Database handle for the object. It is of XML type ID, so is constrained to be unique in the XML document within which it occurs. An external identifier for the object in the form of a URI may be constructed using standard XML and XPointer methods. This is done by concatenating the URI for the document, a fragment separator, and the value of the id attribute.

<element name="RapidLoadTest" type="diggs:RapidLoadTestType" abstract="false" substitutionGroup="diggs:AbstractLoadTestProcedure"> <annotation> <documentation>An axial compressive force-pulse (rapid) load test applied directly to a deep foundation element, per ASTM D7383 or EN ISO 22477-10. The loading lasts tens to a few hundred milliseconds, between the seconds-to-minutes timescale of diggs:StaticLoadTest and the millisecond-or-shorter timescale of diggs:DynamicLoadTest, and the measured force pulse needs an inertial and damping correction (analysisMethod) to give a load-settlement response. EN ISO 22477-10 classifies a rapid test by purpose, as an investigation test (a sacrificial pile loaded to the ultimate limit state) or a control test (a working pile loaded to a specified load above the serviceability limit state); ASTM D7383 does not name the distinction, so give testCategory where it applies and leave it out otherwise. The two named analysis methods, the Unloading Point Method and its modified form, are used by the practitioner communities of both standards.</documentation> </annotation> </element>

Showing: