add_path: Add Path
In mapdeck: Interactive Maps Using 'Mapbox GL JS' and 'Deck.gl'

Description Usage Arguments Details transitions data legend id Examples

The Path Layer takes in lists of coordinate points and renders them as extruded lines with mitering.

add_path(
  map,
  data = get_map_data(map),
  polyline = NULL,
  stroke_colour = NULL,
  stroke_width = NULL,
  stroke_opacity = NULL,
  dash_size = NULL,
  dash_gap = NULL,
  offset = NULL,
  width_units = c("meters", "pixels"),
  width_min_pixels = NULL,
  width_max_pixels = NULL,
  width_scale = 1,
  tooltip = NULL,
  billboard = FALSE,
  layer_id = NULL,
  id = NULL,
  auto_highlight = FALSE,
  highlight_colour = "#AAFFFFFF",
  palette = "viridis",
  na_colour = "#808080FF",
  legend = FALSE,
  legend_options = NULL,
  legend_format = NULL,
  update_view = TRUE,
  focus_layer = FALSE,
  digits = 6,
  transitions = NULL,
  brush_radius = NULL
)

`map`	a mapdeck map object
`data`	data to be used in the layer. All coordinates are expected to be EPSG:4326 (WGS 84) coordinate system
`polyline`	optional column of `data` containing the polylines, if using encoded polylines
`stroke_colour`	variable of `data` or hex colour for the stroke. If used, `elevation` is ignored. If using a hex colour, use either a single value, or a column of hex colours on `data`
`stroke_width`	width of the stroke in meters. Default 1.
`stroke_opacity`	Either a string specifying the column of `data` containing the opacity of each shape, or a single value in [0,255], or [0, 1), to be applied to all the shapes. Default 255. If a hex-string is used as the colour, this argument is ignored and you should include the alpha on the hex string
`dash_size`	size of each dash, relative to the width of the stroke
`dash_gap`	size of the gap between dashes, relative to the width of the stroke
`offset`	The offset to draw each path with, relative to the width of the path. Negative offset is to the left hand side, and positive offset is to the right hand side. 0 extrudes the path so that it is centered at the specified coordinates.
`width_units`	The units of the line width, one of 'meters', 'pixels'. When zooming in and out, meter sizes scale with the base map, and pixel sizes remain the same on screen.
`width_min_pixels`	The minimum path width in pixels. This can be used to prevent the path from getting too thin when zoomed out.
`width_max_pixels`	The maximum path width in pixels. his prop can be used to prevent the path from getting too thick when zoomed in.
`width_scale`	The path width multiplier that multiplied to all paths.
`tooltip`	variable of `data` containing text or HTML to render as a tooltip
`billboard`	logical indicating if the path always faces the camera (TRUE) or if it always faces up (FALSE)
`layer_id`	single value specifying an id for the layer. Use this value to distinguish between shape layers of the same type. Layers with the same id are likely to conflict and not plot correctly
`id`	an id value in `data` to identify layers when interacting in Shiny apps.
`auto_highlight`	logical indicating if the shape under the mouse should auto-highlight
`highlight_colour`	hex string colour to use for highlighting. Must contain the alpha component.
`palette`	string or matrix. String will be one of `colourvalues::colour_palettes()`. A matrix must have at least 5 rows, and 3 or 4 columns of values between [0, 255], where the 4th column represents the alpha. You can use a named list to specify a different palette for different colour options (where available), e.g. list(fill_colour = "viridis", stroke_colour = "inferno")
`na_colour`	hex string colour to use for NA values
`legend`	either a logical indiciating if the legend(s) should be displayed, or a named list indicating which colour attributes should be included in the legend.
`legend_options`	A list of options for controlling the legend.
`legend_format`	A list containing functions to apply to legend values. See section legend
`update_view`	logical indicating if the map should update the bounds to include this layer
`focus_layer`	logical indicating if the map should update the bounds to only include this layer
`digits`	number of digits for rounding coordinates
`transitions`	list specifying the duration of transitions.
`brush_radius`	radius of the brush in metres. Default NULL. If supplied, the arcs will only show if the origin or destination are within the radius of the mouse. If NULL, all arcs are displayed

add_path supports LINESTRING and MULTILINESTRING sf objects

The transitions argument lets you specify the time it will take for the shapes to transition from one state to the next. Only works in an interactive environment (Shiny) and on WebGL-2 supported browsers and hardware.

The time is in milliseconds

Available transitions for path

list( path = 0, stroke_colour = 0, stroke_width = 0 )

If the data is a simple feature object, the geometry column is automatically detected. If the sf object contains more than one geometry column and you want to use a specific one, you'll need to set the active geometry using sf::st_geometry( x ) <- "your_column" , where "your_column" is the name of the column you're activating. See ?sf::st_geometry

The legend_options can be used to control the appearance of the legend. This should be a named list, where the names are one of

css - a string of valid css for controlling the appearance of the legend
title - a string to use for the title of the legend
digits - number to round the legend values to

If the layer allows different fill and stroke colours, you can use different options for each. See examples in add_arc.

The legend_format can be used to control the format of the values in the legend. This should be a named list, where the names are one of

fill_colour
stroke_colour

depending on which type of colouring the layer supports.

The list elements must be functions to apply to the values in the legend.

The id is returned to your R session from an interactive shiny environment by observing layer clicks. This is useful for returning the data.frame row relating to the cliked shape.

From within a shiny server you would typically use observeEvent({input$map_arc_click}), where 'map' is the map_id supplied to mapdeckOutput(), and 'arc' is the layer you are clicking on

## You need a valid access token from Mapbox
key <- 'abc'
set_token( key )

mapdeck(
  style = mapdeck_style("dark")
  , location = c(145, -37.8)
  , zoom = 10) %>%
  add_path(
    data = roads
    , stroke_colour = "RIGHT_LOC"
    , layer_id = "path_layer"
    , tooltip = "ROAD_NAME"
    , auto_highlight = TRUE
    , legend = TRUE
  )