From c00a18803106913e36e8cdde44e171559a3caaf5 Mon Sep 17 00:00:00 2001 From: edzer Date: Fri, 22 Nov 2024 22:58:38 +0100 Subject: [PATCH] links --- .Rbuildignore | 1 + R/wkt.R | 4 ++-- man/geos_unary.Rd | 12 +++++++++--- man/st_as_sfc.Rd | 2 +- man/st_as_text.Rd | 2 +- vignettes/sf1.Rmd | 4 ++-- 6 files changed, 16 insertions(+), 9 deletions(-) diff --git a/.Rbuildignore b/.Rbuildignore index 336ab726e..d18654298 100644 --- a/.Rbuildignore +++ b/.Rbuildignore @@ -28,3 +28,4 @@ changes1.txt changes2.txt changes3.txt changes.txt +aware.patch diff --git a/R/wkt.R b/R/wkt.R index 14407a2b0..70dfa080b 100644 --- a/R/wkt.R +++ b/R/wkt.R @@ -82,7 +82,7 @@ prnt.GEOMETRYCOLLECTION = function(x, ..., EWKT = TRUE) { #' @param ... modifiers; in particular \code{digits} can be passed to control the number of digits used #' @name st_as_text #' @details The returned WKT representation of simple feature geometry conforms to the -#' \href{https://www.ogc.org/standard/sfa/}{simple features access} specification and extensions +#' \href{https://www.ogc.org/publications/standard/sfa/}{simple features access} specification and extensions #' (known as EWKT, supported by PostGIS and other simple features implementations for addition of #' a SRID to a WKT string). #' @note To improve conversion performance, the lwgeom package can be used (it must be installed @@ -144,7 +144,7 @@ st_as_text.sfc = function(x, ..., EWKT = FALSE) { #' @rdname st_as_sfc #' @md #' @details If `x` is a character vector, it should be a vector containing -#' [well-known-text](https://www.ogc.org/standard/wkt-crs/), or +#' [well-known-text](https://www.ogc.org/publications/standard/wkt-crs/), or #' Postgis EWKT or GeoJSON representations of a single geometry for each vector element. #' @param crs integer or character; coordinate reference system for the #' @param GeoJSON logical; if \code{TRUE}, try to read geometries from GeoJSON text strings diff --git a/man/geos_unary.Rd b/man/geos_unary.Rd index ee90936d0..5505e0ffe 100644 --- a/man/geos_unary.Rd +++ b/man/geos_unary.Rd @@ -49,7 +49,13 @@ st_inscribed_circle(x, dTolerance, ...) st_minimum_rotated_rectangle(x, ...) -st_voronoi(x, envelope, dTolerance = 0, bOnlyEdges = FALSE, point_order = FALSE) +st_voronoi( + x, + envelope, + dTolerance = 0, + bOnlyEdges = FALSE, + point_order = FALSE +) st_polygonize(x) @@ -115,13 +121,13 @@ meters.} \item{envelope}{object of class \code{sfc} or \code{sfg} containing a \code{POLYGON} with the envelope for a voronoi diagram; this only takes effect when it is larger than the default envelope, chosen when \code{envelope} is an empty polygon} +\item{point_order}{logical; preserve point order if TRUE and GEOS version >= 3.12; overrides bOnlyEdges} + \item{directed}{logical; if \code{TRUE}, lines with opposite directions will not be merged} \item{of_largest_polygon}{logical; for \code{st_centroid}: if \code{TRUE}, return centroid of the largest (sub)polygon of a \code{MULTIPOLYGON} rather than of the whole \code{MULTIPOLYGON}} \item{dfMaxLength}{maximum length of a line segment. If \code{x} has geographical coordinates (long/lat), \code{dfMaxLength} is either a numeric expressed in meter, or an object of class \code{units} with length units \code{rad} or \code{degree}; segmentation in the long/lat case takes place along the great circle, using \link[lwgeom:geod]{st_geod_segmentize}.} - -\item{point_order}{logical; preserve point order if TRUE and GEOS version >= 3.12; overrides bOnlyEdges} } \value{ an object of the same class of \code{x}, with manipulated geometry. diff --git a/man/st_as_sfc.Rd b/man/st_as_sfc.Rd index 6b71a53b3..95d5304b0 100644 --- a/man/st_as_sfc.Rd +++ b/man/st_as_sfc.Rd @@ -100,7 +100,7 @@ Convert foreign geometry object to an sfc object When converting from WKB, the object \code{x} is either a character vector such as typically obtained from PostGIS (either with leading "0x" or without), or a list with raw vectors representing the features in binary (raw) form. If \code{x} is a character vector, it should be a vector containing -\href{https://www.ogc.org/standard/wkt-crs/}{well-known-text}, or +\href{https://www.ogc.org/publications/standard/wkt-crs/}{well-known-text}, or Postgis EWKT or GeoJSON representations of a single geometry for each vector element. If \code{x} is a \code{factor}, it is converted to \code{character}. diff --git a/man/st_as_text.Rd b/man/st_as_text.Rd index a87a9e2f1..43c3fc2a5 100644 --- a/man/st_as_text.Rd +++ b/man/st_as_text.Rd @@ -31,7 +31,7 @@ Return Well-known Text representation of simple feature geometry or coordinate r } \details{ The returned WKT representation of simple feature geometry conforms to the -\href{https://www.ogc.org/standard/sfa/}{simple features access} specification and extensions +\href{https://www.ogc.org/publications/standard/sfa/}{simple features access} specification and extensions (known as EWKT, supported by PostGIS and other simple features implementations for addition of a SRID to a WKT string). } diff --git a/vignettes/sf1.Rmd b/vignettes/sf1.Rmd index fb1c36ebf..b622784ec 100644 --- a/vignettes/sf1.Rmd +++ b/vignettes/sf1.Rmd @@ -20,7 +20,7 @@ if (file.exists("nc.shp")) file.remove("nc.shp", "nc.dbf", "nc.shx") ``` -[Simple features](https://en.wikipedia.org/wiki/Simple_Features) or [_simple feature access_](https://www.ogc.org/standard/sfa/) refers to a formal standard (ISO 19125-1:2004) that describes how objects in the real world can be represented in computers, with emphasis on the _spatial_ geometry of these objects. It also describes how such objects can be stored in and retrieved from databases, and which geometrical operations should be defined for them. +[Simple features](https://en.wikipedia.org/wiki/Simple_Features) or [_simple feature access_](https://www.ogc.org/publications/standard/sfa/) refers to a formal standard (ISO 19125-1:2004) that describes how objects in the real world can be represented in computers, with emphasis on the _spatial_ geometry of these objects. It also describes how such objects can be stored in and retrieved from databases, and which geometrical operations should be defined for them. The standard is widely implemented in spatial databases (such as [PostGIS](https://postgis.net/)), commercial GIS (e.g., [ESRI @@ -72,7 +72,7 @@ features are based on 2D geometry with linear interpolation between vertices._" We will see soon that the same standard will extend its coverage beyond 2D and beyond linear interpolation. Here, we take simple features as the data structures and operations described -in the [standard](https://www.ogc.org/standard/sfa/). +in the [standard](https://www.ogc.org/publications/standard/sfa/). ## Dimensions