33# ' @param bbox Either (i) four numeric values specifying the maximal and minimal
44# ' longitudes and latitudes, in the form \code{c(xmin, ymin, xmax, ymax)}
55# ' or (ii) a character string in the form \code{xmin,ymin,xmax,ymax}. These
6- # ' will be passed to \link{ getbb} to be converted to a numerical bounding
6+ # ' will be passed to [ getbb()] to be converted to a numerical bounding
77# ' box. Can also be (iii) a matrix representing a bounding polygon as
88# ' returned from `getbb(..., format_out = "polygon")`. To search in an
99# ' area, (iv) a character string with a relation or a (closed) way id in
1010# ' the format `"way(id:1)"`, `"relation(id:1, 2)"` or `"relation(id:1, 2,
1111# ' 3); way(id:2)"` as returned by `getbb(..., format_out = "osm_type_id")`
12- # ' or \link{ bbox_to_string} with a `data.frame` from `getbb(..., format_out
12+ # ' or [ bbox_to_string()] with a `data.frame` from `getbb(..., format_out
1313# ' = "data.frame")` to select all areas combined (relations and ways).
1414# ' @param nodes_only WARNING: this parameter is equivalent to
1515# ' `osm_types = "node"` and is DEPRECATED. If `TRUE`, query OSM nodes
2020# ' `highway = "traffic_signals"` are represented by nodes only. Queries are
2121# ' built by default to return all nodes, ways, and relation, but this can
2222# ' be very inefficient for node-only queries. Setting this value to `"node"`
23- # ' for such cases makes queries more efficient and, in [` osmdata_sf()` ], the
23+ # ' for such cases makes queries more efficient and, in [osmdata_sf()], the
2424# ' data will be returned in the `osm_points` list item only.
2525# ' @param out The level of verbosity of the overpass result: `body` (geometries
2626# ' and tags, the default), `tags` (tags without geometry), `meta` (like
4949# ' @return An `overpass_query` object
5050# '
5151# ' @details The `out` statement for `tags`, `tags center`and `id`, do not return
52- # ' geometries. Neither `out = "meta"` nor `adiff = TRUE` options are implemented
53- # ' for all `osmdata_*` functions yet. Use [osmdata_xml] or [osmdata_data_frame]
54- # ' to get the result of these queries. See the documentation of the [out
52+ # ' geometries. `adiff = TRUE` option is not implemented for all `osmdata_*` functions yet.
53+ # ' Use [osmdata_xml] or [osmdata_data_frame] to get the result of these queries. See the
54+ # ' documentation of the [out
5555# ' statement](https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#out)
5656# ' and [augmented
5757# ' difference](https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#Augmented-difference_between_two_dates_(adiff))
@@ -263,24 +263,24 @@ paste_features <- function (key, value, key_pre = "", bind = "=",
263263# ' not sensitive to case
264264# ' @param bbox optional bounding box for the feature query; must be set if no
265265# ' opq query bbox has been set
266- # ' @return \link{ opq} object
266+ # ' @return An [ opq] object.
267267# '
268268# ' @note `key_exact` should generally be `TRUE`, because OSM uses a
269269# ' reasonably well defined set of possible keys, as returned by
270- # ' \link{ available_features} . Setting `key_exact = FALSE` allows matching
270+ # ' [ available_features()] . Setting `key_exact = FALSE` allows matching
271271# ' of regular expressions on OSM keys, as described in Section 6.1.5 of
272272# ' <https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL>. The actual
273273# ' query submitted to the overpass API can be obtained from
274- # ' \link{ opq_string} .
274+ # ' [ opq_string()] .
275275# '
276276# ' @references <https://wiki.openstreetmap.org/wiki/Map_Features>
277- # ' @seealso [add_osm_features]
277+ # ' @seealso [add_osm_features() ]
278278# '
279279# ' @section `add_osm_feature` vs `add_osm_features`:
280- # ' Features defined within an [add_osm_features] call are combined with a
280+ # ' Features defined within an [add_osm_features() ] call are combined with a
281281# ' logical OR.
282282# '
283- # ' Chained calls to either [ add_osm_feature] or ` add_osm_features()` combines
283+ # ' Chained calls to either ` add_osm_feature()` or [ add_osm_features()] combines
284284# ' features from these calls in a logical AND; this is analagous to chaining
285285# ' `dplyr::filter()` on a data frame.
286286# '
@@ -478,7 +478,7 @@ check_bind_key_pre <- function (bind = "=", key_pre = "") {
478478
479479# ' Add multiple features to an Overpass query
480480# '
481- # ' Alternative version of \link{ add_osm_feature} for creating single queries
481+ # ' Alternative version of [ add_osm_feature()] for creating single queries
482482# ' with multiple features. Key-value matching may be controlled by using the
483483# ' filter symbols described in
484484# ' \url{https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#By_tag_.28has-kv.29}.
@@ -491,7 +491,7 @@ check_bind_key_pre <- function (bind = "=", key_pre = "") {
491491# ' quotations. See examples for details.
492492# ' @param bbox optional bounding box for the feature query; must be set if no
493493# ' opq query bbox has been set.
494- # ' @return \link{ opq} object
494+ # ' @return An [ opq] object.
495495# '
496496# ' @references \url{https://wiki.openstreetmap.org/wiki/Map_Features}
497497# ' @seealso [add_osm_feature]
@@ -709,7 +709,7 @@ filter_osm_user <- function (opq, user, touched = FALSE, is_uid) {
709709# ' @param open_url If `TRUE`, open the OSM page of the specified object in web
710710# ' browser. Multiple objects (`id` values) will be opened in multiple
711711# ' pages.
712- # ' @return \link{ opq} object
712+ # ' @return An [ opq] object.
713713# '
714714# ' @references
715715# ' \url{https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#By_element_id}
@@ -801,8 +801,8 @@ opq_osm_id <- function (id = NULL, type = NULL, open_url = FALSE,
801801# '
802802# ' Find all features which enclose a given point, and optionally match specific
803803# ' 'key'-'value' pairs. This function is \emph{not} intended to be combined with
804- # ' \link{ add_osm_feature} , rather is only to be used in the sequence
805- # ' \link{ opq_enclosing} -> \link{ opq_string} -> \link{ osmdata_xml} (or other
804+ # ' [ add_osm_feature()] , rather is only to be used in the sequence
805+ # ' [ opq_enclosing()] -> [ opq_string()] -> [ osmdata_xml()] (or other
806806# ' extraction function). See examples for how to use.
807807# '
808808# ' @param lon Longitude of desired point
@@ -868,8 +868,8 @@ opq_enclosing <- function (lon = NULL, lat = NULL,
868868# '
869869# ' Find all features around a given point, and optionally match specific
870870# ' 'key'-'value' pairs. This function is \emph{not} intended to be combined with
871- # ' \link{ add_osm_feature} , rather is only to be used in the sequence
872- # ' \link{ opq_around} -> \link{ osmdata_xml} (or other extraction function). See
871+ # ' [ add_osm_feature()] , rather is only to be used in the sequence
872+ # ' [ opq_around()] -> [ osmdata_xml()] (or other extraction function). See
873873# ' examples for how to use.
874874# '
875875# ' @param radius Radius in metres around the point for which data should be
@@ -920,7 +920,7 @@ opq_around <- function (lon, lat, radius = 15,
920920# ' Transform an Overpass query to return the result in a csv format
921921# '
922922# ' @param q A opq string or an object of class `overpass_query` constructed with
923- # ' \link{ opq} or alternative opq builders (+ \link{ add_osm_feature} /s).
923+ # ' [ opq()] or alternative opq builders (+ [ add_osm_feature()] /s).
924924# ' @param fields a character vector with the field names.
925925# ' @param header if \code{FALSE}, do not ask for column names.
926926# '
@@ -929,7 +929,7 @@ opq_around <- function (lon, lat, radius = 15,
929929# '
930930# ' @details The output format `csv`, ask for results in csv. See
931931# ' [CSV output mode](https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#CSV_output_mode)
932- # ' for details. To get the data, use \link{ osmdata_data_frame} .
932+ # ' for details. To get the data, use [ osmdata_data_frame()] .
933933# '
934934# ' @note csv queries that reach the timeout will return a 0 row data.frame
935935# ' without any warning. Increase `timeout` in `q` if you don't see the
0 commit comments