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

Polyline

Required string. Encoded polyline using the Google polyline algorithm.

Precision

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

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

Decode a Google encoded-polyline string into [latitude, longitude] coordinate pairs at the given decimal precision. Inputs are interpreted exactly in the displayed units and the calculation returns the following fields without presentation rounding.

Coordinates

Returned list. Decoded coordinates as [latitude, longitude] pairs.

• 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 Decoder

  Decode a geohash string into its cell centre latitude/longitude plus the bounding box of the cell.

• Unsigned Varint Decoder

  Decode one unsigned LEB128 varint from a hexadecimal byte string, returning the exact integer as decimal text. Rejects trailing bytes and encodings beyond 64 bits.

• Bacon Cipher Decoder

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