moveVis 1.0.0

moveVis 1.0.0

Updating moveVis to support move2 for representing trajectory data and terra for representing raster data.

Changes:

• Argument res of align_move now expects a units object for representing the target time resolution (see ?moveVis::align_move).
• align_move now relies on s2 for spatio-temporal interpolation.
• frames_spatial now expects terra SpatRasterDataset for multi-temporal raster data via the r argument. See ?moveVis::frames_spatial for details.
• Arguments crs and crs_graticule were added to frames_spatial to control the CRS used by frames (see ?frames_spatial for details). With this version onwards, the CRS of frames created using frames_spatial is no longer determined by the CRS of m but instead by argument crs. All spatial components of frames will be transformed to this CRS if needed. The standard CRS of moveVis frames is Web Mercator (EPSG 3857), as this CRS is the standard CRS of open base map products from the web. This default setting ensures that map labels are not distorted.
• Argument ext of frames_spatial now expect an sf bbox object with same CRS a m.
• render_frame now uses coord_sf instead of coord_cartesian to correctly render different Coordinate Reference Systems.
• join_frames now uses patchwork instead of cowplot to combine plots in frames. Thus, arguments guides, design, render_all_legends and ... were added to control patchwork::wrap_plots.
• moveVis documentation was updated to reflect the changes.
• moveVis example code was updated, using move2 instead of move and terra instead of raster and to reflect the changes.
• The way dateline crossings are handled has been revised: moveVis now relies on sf to compute cross-dateline paths in Lat/Lon instead of doing this internally. Be advised that it is recommended to use a projection suiting your area instead of enabling dateline crossing in Lat/Lon (see ?frames_spatial for details).
• Example movement data were updated to the move2 class
• Example raster data were updated to the terra SpatRasterDataset class and an additional example comprised of disrecte values was added (see ?moveVis::example_data for details)
• s2, move2, terra, units, patchwork, ggnewscale, basemaps and rlang were added as imports
• move, raster and cowplot were removed as imports

Deprecations:

• Arguments r_list and r_times of frames_spatial are deprecated. Use argument r instead and supply a terra SpatRasterDataset to bundle multiple multi-layered rasters of a time series. See ?moveVis::frames_spatial for details.
• df2move and subset_move were deprecated in favor of move2's interface for coercion and subsetting.

Distribution:

• moveVis was added to r-universe for continuous testing and integration. Like on CRAN, platform-specific binaries are build there to ease installation. You can now install the most recent moveVis version from r-universe using install.packages("moveVis", repos = '16eagle.r-universe.dev')

moveVis 0.10.6

moveVis 0.10.6

New S3 class and methods to represent frames, lazy plotting, improvements.

New features:

• Frames are now represented by a new native moveVis S3 class that is outputted by all frames_*() functions such as frames_spatial(). The class comes with native printing and indexing methods. Frames can be easily subsetted ([), plotted ([[) and checked for length (length()). The default print method displays a summary of the created frames.
• With the native moveVis class, frames are now rendered lazy when plotted and not being hold in memory. As data duplication has been reduced to the minimum, this change should reduces memory use of frames_spatial(). All functions work with the new class. This change mostly effects how things work under the hood and does not alter the user interface.
• added documentation search using DocSearch to web page
• Argument digit of align_move() is deprecated, since digits are now calculated automatically.
• Multiple improvements to align_move(), including printing of the detected resolution to which data are aligned.
• Added path_colours to frames_graph() to be able to colour paths equal to paths in frames_spatial()
• Added basemaps as dependency for downloading and caching basemaps, removed native basemap retrieval and plotting functions

Deprecations:

• Argument m of add_timestamps() has been deprecated since the new moveVis class contains all necessary data to obtain frame times. Thus, it is not needed anymore and therefore ignored if still being used.

Bug fixes:

• Bug that caused align_move() to break with an unspecific error message when at least one trajectory of m covered a time range shorter than the requested temporal resolution. The function now warns the user when a temporal resolution is selected that cannot be applied to at least one trajectory and excludes the trajectory/trajectories in question from the returned object.
• Bug that caused frames_spatial() to interrupt with an error when trying to interpolate r_list with fade_raster=T
• Fixed bug in adding margin to user ext in frames_spatial()
• Fixed bug with paths crossing end of grid (aka dateline) when cross_dateline=TRUE in frames_spatial()

moveVis 0.10.5

Revised distance calculations & handling of dateline crossings. Released on CRAN: 2020-03-28

New features:

• Argument cross_dateline of frames_spatial to indicate that unprojected tracks in lon/lat cross the dateline. Instead of clipping frames at longitudes -180 and 180, moveVis extends frames and connects tracks across the dateline.
• Distance calculations are now based on lwgeom
• Refined base map plotting (see additional arguments ... of frames_spatial for available options)
• Added NA handling for base maps (e.g. rasterized labels)
• Dropped dependencies

Bug fixes:

• Minor errors and warnings caused by reverse dependency changes of package sf

Go to http://movevis.org/news/ for a full overview of all releases.

moveVis 0.10.4

Publication, added parallelization, new memory settings and bug fixes. Released on CRAN: 2020-02-07.

Peer-reviewed publication:

• An open-access paper accompanying the moveVis R package has been peer-reviewed by and published in 'Methods in Ecology and Evolution' (see https://doi.org/10.1111/2041-210X.13374).
• Reference: Schwalb-Willmann, J.; Remelgado, R.; Safi, K.; Wegmann, M. (2020). moveVis: Animating movement trajectories in synchronicity with static or temporally dynamic environmental data in R. Methods in Ecology and Evolution. Accepted Author Manuscript. https://doi.org/10.1111/2041-210X.13374.
• Citation: Please use citation("moveVis") to cite moveVis, e.g. when you use it in publications or presentations.

New features:

• Many computationally expensive moveVis tasks can now be parallelized, as multi-core support for moveVis has been implemented (see use_multicore())
• Added a new example data set whitestork_data, representing coordinates and acquisition times of 15 White Storks migrating from Lake of Constance, Germany, to Africa.

New functions:

• use_multicore() lets you turn on multi-core support of moveVis to increase computational time through parallelization.
• use_disk() enables the usage of disk space for creating frames. This can prevent memory overload when creating frames for very large animations.

Bug fixes:

• Bug that caused a gap between traces and paths.

v0.9.9 – last stable release of moveVis with old syntax

This release represents the last version of moveVis using the old moveVis function syntax.

With moveVis 0.10.0, a rewrite of moveVis has been released. The new version of moveVis introduces new functions that make it much easier to create animations from movement and imagery data and customize them. However, code written for older versions of moveVis (<= 0.9.9) will not work with newer moveVis versions (>= 0.10). While it is highly recommended to adjust your old code and use the new moveVis functions, there might be some cases where you need your old code to work. For this, the last version supporting functions of older versions (such as animate_move()) is released here.