From d9ad7eba87bcf6b337ae9b6f5c90ca423a95aab8 Mon Sep 17 00:00:00 2001 From: Gabor Szarnyas Date: Sat, 7 Dec 2024 11:11:32 +0100 Subject: [PATCH] Remove repeated words --- README.md | 2 +- docs/functions.md | 2 +- spatial/src/spatial/core/functions/scalar/st_quadkey.cpp | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 004e2982..dbe2ba84 100644 --- a/README.md +++ b/README.md @@ -15,7 +15,7 @@ - [Limitations and Roadmap](#limitations-and-roadmap) # What is this? -This is a prototype of a geospatial extension for DuckDB that adds support for working with spatial data and functions in the form of a `GEOMETRY` type based on the the "Simple Features" geometry model, as well as non-standard specialized columnar DuckDB native geometry types that provide better compression and faster execution in exchange for flexibility. +This is a prototype of a geospatial extension for DuckDB that adds support for working with spatial data and functions in the form of a `GEOMETRY` type based on the "Simple Features" geometry model, as well as non-standard specialized columnar DuckDB native geometry types that provide better compression and faster execution in exchange for flexibility. Please note that this extension is still in a very early stage of development, and the internal storage format for the geometry types may change indiscriminately between commits. We are actively working on it, and we welcome both contributions and feedback. Please see the [function table](docs/functions.md) or the [roadmap entries](https://github.com/duckdblabs/duckdb_spatial/labels/roadmap) for the current implementation status. diff --git a/docs/functions.md b/docs/functions.md index 80e4cc1b..9261f46c 100644 --- a/docs/functions.md +++ b/docs/functions.md @@ -1785,7 +1785,7 @@ VARCHAR ST_QuadKey (point GEOMETRY, level INTEGER) #### Description Compute the [quadkey](https://learn.microsoft.com/en-us/bingmaps/articles/bing-maps-tile-system) for a given lon/lat point at a given level. -Note that the the parameter order is __longitude__, __latitude__. +Note that the parameter order is __longitude__, __latitude__. `level` has to be between 1 and 23, inclusive. diff --git a/spatial/src/spatial/core/functions/scalar/st_quadkey.cpp b/spatial/src/spatial/core/functions/scalar/st_quadkey.cpp index 59b33722..cd14b85b 100644 --- a/spatial/src/spatial/core/functions/scalar/st_quadkey.cpp +++ b/spatial/src/spatial/core/functions/scalar/st_quadkey.cpp @@ -93,7 +93,7 @@ static void GeometryQuadKeyFunction(DataChunk &args, ExpressionState &state, Vec static constexpr const char *DOC_DESCRIPTION = R"( Compute the [quadkey](https://learn.microsoft.com/en-us/bingmaps/articles/bing-maps-tile-system) for a given lon/lat point at a given level. -Note that the the parameter order is __longitude__, __latitude__. +Note that the parameter order is __longitude__, __latitude__. `level` has to be between 1 and 23, inclusive.