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

Coordinates

Required list. Coordinates as [latitude, longitude] pairs in route order.

Precision

Optional integer. Decimal places encoded per coordinate (default Google precision is 5).

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

Encode [latitude, longitude] pairs into a Google encoded-polyline string using the standard delta and varint scheme. Inputs are interpreted exactly in the displayed units and the calculation returns the following fields without presentation rounding.

Polyline

Returned string. Encoded polyline string.

• Unicode normalization, locale, grapheme clusters, malformed input, ambiguous syntax, and implementation-specific conventions can change text-processing results.
• Precision must be at least 0.
• Precision must be no greater than 11.
• 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.

• Geohash Encoder

  Encode a latitude/longitude pair into a geohash string of the requested base32 length.

• Bacon Cipher Encoder

  Encode letters A–Z into five-symbol Bacon cipher groups.

• Base32 Encoder

  Encode UTF-8 text as RFC 4648 base32 using letters A-Z and digits 2-7 with padding.