Skip to content

Commit

Permalink
Clarify that geopoint is number-based (#14)
Browse files Browse the repository at this point in the history
  • Loading branch information
roll committed Jan 6, 2024
1 parent 5093435 commit dfee092
Showing 1 changed file with 3 additions and 4 deletions.
7 changes: 3 additions & 4 deletions content/docs/specifications/table-schema.md
Original file line number Diff line number Diff line change
Expand Up @@ -327,11 +327,10 @@ The field contains data describing a geographic point.

`format`:

- **default**: A string of the pattern "lon, lat", where `lon` is the longitude
and `lat` is the latitude (note the space is optional after the `,`). E.g. `"90, 45"`.
- **default**: A string of the pattern "lon, lat", where each value is a number, and `lon` is the longitude and `lat` is the latitude (note the space is optional after the `,`). E.g. `"90.50, 45.50"`.
- **array**: A JSON array, or a string parsable as a JSON array, of exactly two items, where each item is a number, and the first item is `lon` and the second
item is `lat` e.g. `[90, 45]`
- **object**: A JSON object with exactly two keys, `lat` and `lon` and each value is a number e.g. `{"lon": 90, "lat": 45}`
item is `lat` e.g. `[90.50, 45.50]`
- **object**: A JSON object with exactly two keys, `lat` and `lon` and each value is a number e.g. `{"lon": 90.50, "lat": 45.50}`

#### geojson

Expand Down

0 comments on commit dfee092

Please sign in to comment.