# `Geohash`

A geohash cell (geohash.org): 1 to 12 characters, in lower case: `gcpvj0duq`.

[Geospatial](types.md#geospatial); not ordered; since Jadpo 0.1.0.

## Make one

Build one from its text, `Geohash("g")`, which checks it: text that isn't one breaks `format`.

`text.parse(raw, as: Geohash)` reads one from its text; text that isn't one at all fails `malformed`, such as `gcpvja`, `GCPVJ` or `gcpvj0duq5x7z`.

## Text, JSON and storage

`text.from` writes its canonical text, the one form `text.parse` reads back. JSON sends its canonical text as a string.

| Text | JSON |
|---|---|
| `g` | `"g"` |
| `gcpvj0duq` | `"gcpvj0duq"` |
| `u09tvw0f6szy` | `"u09tvw0f6szy"` |

It is stored in one column named for the field, of type `text`. `gcpvj0duq` is stored as `'gcpvj0duq'`.

## Shown to people

`text.format(value, locale:)` shows it to people in their locale.

With `locale: Locale.en_gb`:

| Value | Shown |
|---|---|
| `g` | `g` |
| `gcpvj0duq` | `gcpvj0duq` |
| `u09tvw0f6szy` | `u09tvw0f6szy` |

## Operations

It has the contract's own operations: `text.parse`, `text.from`, `text.format`, `json.read`, `json.write` and `==`. It isn't ordered, so `<` and sorting don't take it. [Every standard type meets one contract](../topics/every-standard-type-meets-one-contract.md) says how they work.