Use this text operation when its stated character encoding, token boundaries, normalization, case handling, and output format match the surrounding workflow.

Latitude

Required number. Latitude in decimal degrees between -90 and 90.

Longitude

Required number. Longitude in decimal degrees between -180 and 180.

Precision

Optional integer. Number of base32 characters to emit.

The cited overview of Code supplies background for the terminology and domain context used by this tool.^[1]

Encode a latitude/longitude pair into a geohash string of the requested base32 length. Inputs are interpreted exactly in the displayed units and the calculation returns the following fields without presentation rounding.

Geohash

Returned string. Geohash using the base32 alphabet 0123456789bcdefghjkmnpqrstuvwxyz.

• Unicode normalization, locale, grapheme clusters, malformed input, ambiguous syntax, and implementation-specific conventions can change text-processing results.
• Latitude must be at least -90.
• Latitude must be no greater than 90.
• Longitude must be at least -180.
• Longitude must be no greater than 180.
• Use finite inputs in the displayed units, preserve source measurements and assumptions, and independently verify consequential decisions.

Preserve the original text, test representative non-ASCII and malformed cases, and use a standards-aware parser or serializer when interoperability matters.

• Google Encoded Polyline Encoder

  Encode [latitude, longitude] pairs into a Google encoded-polyline string using the standard delta and varint scheme.

• Run-Length Encoder

  Compress letter-only text into count-annotated runs such as a3b2c1.

• Tap Code Encoder

  Encode text into digit-pair tap groups. Classic POW tap-code grid omits K (use C).