Planet Surface Gravity Lookup

Independently verified planet/reference surface or pressure-level gravity convention. Exact independently verified context/edition key; not embedded or live reference data. Model only, not an ephemeris, measured stellar identity or observational guarantee.

Description

Planetary surface gravity depends on the reference surface and rotational convention.

Planetary surface gravity depends on the reference surface and rotational convention.1

A supplied notice retains those definitions rather than infer gravity from a planet name. Use Planet Surface Gravity Lookup to retrieve an exact caller-supplied reference entry.

When to use Planet Surface Gravity Lookup

Use Planet Surface Gravity Lookup to retrieve an exact caller-supplied reference entry. Choose an independently reviewed reference for the exact historical, cultural or technical context, then supply its keys and texts.

How to use Planet Surface Gravity Lookup and understand its results

  1. Choose an independently reviewed reference for the exact historical, cultural or technical context, then supply its keys and texts.
  2. Enter Caller verified planet gravity keys, Caller verified planet gravity notices, Query planet gravity key using the field table and validation rules below, then run the tool.
  3. Read Matched caller notice; interpret the units, signs, ordering and unknown-value placeholders described below.
  4. Correct reported input errors and rerun. Apply successful results according to their specific meanings and check the assumptions before using them in a decision.
Input fieldMeaningValue typeRequirement
callerVerifiedPlanetGravityKeysCaller verified planet gravity keysarray of stringRequired; constraints below
callerVerifiedPlanetGravityNoticesCaller verified planet gravity noticesarray of stringRequired; constraints below
queryPlanetGravityKeyQuery planet gravity keystringRequired; constraints below

Provide aligned, nonempty arrays of reference keys and independently verified notices, then enter the exact query key. Keys must be unique, nonblank and at most 128 UTF-16 code units long; notices must be nonblank. Matching is case sensitive and does not trim the query or returned text. The matching notice is returned unchanged; an unknown key is an input error. The reference contents and their applicability are supplied by the caller; the tool does not retrieve external records or verify source authority.

matched reference = suppliedTexts[indexOfExactQueryKey(suppliedKeys)]

Use the field order, units and branch conditions described above.

Output fieldMeaningValue type
matchedCallerNoticeExact caller-supplied notice, unchanged and unverified.string
json
{
  "input": {
    "callerVerifiedPlanetGravityKeys": [
      "context-a/edition-a",
      "context-a/edition-b"
    ],
    "callerVerifiedPlanetGravityNotices": [
      "independently verified reference a",
      "independently verified reference b"
    ],
    "queryPlanetGravityKey": "context-a/edition-b"
  },
  "output": {
    "matchedCallerNotice": "independently verified reference b"
  }
}

Limitations and assumptions

A supplied notice retains those definitions rather than infer gravity from a planet name. Apply the exact scope and assumptions explained above.

All listed fields require explicit values. Unexpected fields, incorrect types, nonfinite numbers and sparse arrays fail validation. Domain-specific bounds, alignments and supported tokens are explained above; extremely large inputs or outputs can also be rejected. Input errors differ from successful false results, empty match lists and unknown-evidence placeholders.

Alternative or Complementary methods

Use Planet Day Length Lookup for a related task: Planetary day length can mean different rotation or solar-day conventions.

Use Jupiter Mass to Earth Masses Converter for a related task: Jupiter and Earth mass units require explicit kilogram definitions for the intended precision.

References

  1. Planet Surface Gravity Lookup — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies