Schema documentation for component diggs:LoadTransferRelation

A shaft (t-z) or tip (q-z) load-transfer relation for one geotechnical unit: the mobilization stiffness and limiting resistance that the shaft friction or tip bearing of a column develops against that unit, together with which unit it applies to and, optionally, the discretized curve behind the stated modulus. Generic design machinery, not specific to rigid inclusions: t-z and q-z load-transfer analysis is standard deep-foundation practice for driven piles, drilled shafts and micropiles. An initial modulus alone discards the shape of the curve: k_tau and k_q are the initial slopes of load-transfer curves, and in ASIRI practice they come from the Frank and Zhao formulation, which is trilinear (an initial slope, a break, a reduced slope and a plateau at the limiting value); the shape governs computed settlement, so give the curve where it matters. A relation is per layer, since a single site-wide k_tau is meaningless, and relationType and geoUnitRef are both required: a classification with no layer, or a layer with no statement of which mechanism it governs, is uninterpretable. Mind the sign convention when the object is used for the negative skin friction limit q_s: above the neutral plane it is the downdrag limit, the opposite sense from the positive shaft resistance below it, for the same physical interface. State which regime a given relation describes in remark or in the documentation of the referenced diggs:GeoUnitObservation, since limitValue alone does not disambiguate it.

<diggs:LoadTransferRelation 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> <diggs:relationType>{1,1}</diggs:relationType> <diggs:geoUnitRef xlink:href="" identifierRef="" nilReason="" owns="false">{1,1}</diggs:geoUnitRef> <diggs:formulation>{0,1}</diggs:formulation> <diggs:initialModulus howDetermined="" qualifier="" uom="">{0,1}</diggs:initialModulus> <diggs:limitValue howDetermined="" qualifier="" uom="">{0,1}</diggs:limitValue> <diggs:curve>{0,1}</diggs:curve> </diggs:LoadTransferRelation>

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="LoadTransferRelation" type="diggs:LoadTransferRelationType">
  <annotation>
    <documentation>A shaft (t-z) or tip (q-z) load-transfer relation for one geotechnical unit: the mobilization stiffness and limiting resistance that the shaft friction or tip bearing of a column develops against that unit, together with which unit it applies to and, optionally, the discretized curve behind the stated modulus. Generic design machinery, not specific to rigid inclusions: t-z and q-z load-transfer analysis is standard deep-foundation practice for driven piles, drilled shafts and micropiles. An initial modulus alone discards the shape of the curve: k_tau and k_q are the initial slopes of load-transfer curves, and in ASIRI practice they come from the Frank and Zhao formulation, which is trilinear (an initial slope, a break, a reduced slope and a plateau at the limiting value); the shape governs computed settlement, so give the curve where it matters. A relation is per layer, since a single site-wide k_tau is meaningless, and relationType and geoUnitRef are both required: a classification with no layer, or a layer with no statement of which mechanism it governs, is uninterpretable. Mind the sign convention when the object is used for the negative skin friction limit q_s: above the neutral plane it is the downdrag limit, the opposite sense from the positive shaft resistance below it, for the same physical interface. State which regime a given relation describes in remark or in the documentation of the referenced diggs:GeoUnitObservation, since limitValue alone does not disambiguate it.</documentation>
  </annotation>
</element>

Showing: