From ad3fb0a818b347dc7b94fb1f39cfdd702e6a3e4b Mon Sep 17 00:00:00 2001 From: Jap8nted Date: Wed, 17 Jan 2024 20:27:25 +0100 Subject: [PATCH] fix typo on geoparquet.md --- format-specs/geoparquet.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/format-specs/geoparquet.md b/format-specs/geoparquet.md index 4782e57..207fabf 100644 --- a/format-specs/geoparquet.md +++ b/format-specs/geoparquet.md @@ -79,7 +79,7 @@ The value of this key may be explicitly set to `null` to indicate that there is In a dynamic CRS, coordinates of a point on the surface of the Earth may change with time. To be unambiguous, the coordinates must always be qualified with the epoch at which they are valid. -The optional `epoch` field allows to specify this in case the `crs` field defines a a dynamic CRS. The coordinate epoch is expressed as a decimal year (e.g. `2021.47`). Currently, this specification only supports an epoch per column (and not per geometry). +The optional `epoch` field allows to specify this in case the `crs` field defines a dynamic CRS. The coordinate epoch is expressed as a decimal year (e.g. `2021.47`). Currently, this specification only supports an epoch per column (and not per geometry). #### encoding