Skip to content

Main content

Gravity Latitude Correction Input

Apply a caller-supplied latitude correction under an explicit add/subtract convention without calculating a gravity model.

Loading tool…

Description

Apply a caller-supplied latitude-reference contribution to a gravity observation.

Geophysical observations depend on acquisition geometry, sample timing, component orientation, reference levels and calibration signs. Ideal travel-time depth and one-dimensional alias bounds describe supplied models rather than a complete subsurface inversion. A referenced signal or pseudodepth label needs its original physical convention.

Apply a caller-supplied latitude-reference contribution to a gravity observation.

When to use this tool

Use Gravity Latitude Correction Input when checking the stated local geophysical geometry, reference, sampling or calibration term.

How to use the tool and how it works

  1. Enter observedGravity, suppliedCorrection, addCorrection. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read correctedGravity. Use the output convention below.

Add suppliedCorrection to observedGravity when addCorrection=true, otherwise subtract it.1

Input fieldMeaning and unitsAccepted input
observedGravityObserved GravityRequired. Finite number.
suppliedCorrectionSupplied CorrectionRequired. Finite number.
addCorrectionAdd CorrectionRequired. Boolean.
Output fieldInterpretationReturned shape
correctedGravityCorrected GravityRequired. Finite number.
json
{
  "input": {
    "observedGravity": 980000,
    "suppliedCorrection": 12,
    "addCorrection": true
  },
  "output": {
    "correctedGravity": 980012
  }
}

Limitations and assumptions

  • The correction and sign policy are supplied; latitude, reference gravity, geographic position and an appropriate physical correction are not computed.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use calibrated acquisition records and an appropriate complete wavefield, geological or instrument model for physical inference and safe field operations.

References

  1. Calculation and input contract: geophysics/gravity-latitude-correction-input — tool.io

Similar or alternative tools