Bug fixes. Released on CRAN: 2019-10-06.
frames_spatial()now clips all tracks to
extis smaller than the extent of
add_scalebar()to switch between
0for smaller-scale extents. Distance rounding is now iterated by digit to solve this.
frames_spatial()that resulted in wrong plot extents when an extent smaller than the extent of m was provided using argument ‘ext’. In such a case, movement tracks are now clipped to small extents and move outside of the visible frame instead of altering the frame extent.
trace_show = TRUE. Traces are now always displayed behind paths.
Adding some small but practical features. Released on CRAN: 2019-04-30.
frames_spatial()for defining path transparency.
frames_spatial()makes it now possible to define the colour of the last tail element, to which the path colour is faded. Default is “white”.
frames_spatial()for displaying the trace of the complete path (instead that it vanishes after the tail).
frames_spatial()for defining the colour of the trace.
add_colourscale()for defining the colouring of NA values.
add_colourscale()to show or hide NA values in discrete background rasters.
animate_frames()to hold the last frame, adding a pause of a user-defined duration to the end of an animation.
frames_spatial()to define whether paths should be faded towards the last frame or not. Useful in combination with
trace_show = Tand when using
moveVisnow stores the timestamps represented by each frame as an attribute
ggplotframe. Frame times can now be accessed using
add_timestamps()can now extract timestamps directly from frames, which makes defining
get_frametimes()lets you extract the timestamps associated with each frame of a list of frames created using
add_colourscale()now calculates scale and legend with frame-wide fixed limits, when
coloursis defined as a named vector, e.g.
c("-1" = "red", "0" = "blue", "1" = "green").
moveVisnow displays the approximated duration of an animation on the console, when creating frames or rendering frames.
Bug fixes. Released on CRAN: 2019-04-11.
fade_raster = Tin
frames_spatial()due to unequal vector lengths returned by the internal interpolation function (issue #45)
fade_raster = Fand/or
r_timescontained time elements outside the time range covered by the timestamps of
moveVis rewrite introducing a new logic and new functions. Released on CRAN: 2019-03-20
ggplot2syntax can now be added to every single frame, allowing you to customize almost everything that can be customized using
add_functions wrapping pre-defined
ggplot2functions are included. For example,
add_ggoffers dynamic overplotting, e.g. for polygons or points that change over time
colourcolumn in your movement data, allowing segmentation coulouring or colouring based on a logic, you defined beforhand
frames_spatial()you can define user-defined area of interest (AOI), which scales the frame extent to a specific area
moveVissupports Mapbox (free, registration needed). OpenStreetMap and Carto (both free) as base map services. See the manual of
frames_spatial()now takes the argument
equidistantto define whether the map should be stretched to an equidistant (squared) extent (x and y axis representing same distance) or not (projection-native ratio).
coord_sfto display projections (see details section of
animate_frames(): see the README and the description of the individual functions for further details.
subset_move(): subset movement data for a particular time span
df2move(): simple wrapper that converts data.frames into move or moveStack objects
view_spatial(): view movement data on an interactive map using
get_libraries(): These functions have been replaced by a new logic and new functions.
Reorganizing standard basemap usage by moveVis. Released on CRAN: 2018-11-23
map_typeare now retrieved from either OpenStreetMaps for thematic imagery or Microsoft Bing Maps for satellite/hybrid imagery. The usage of OpenStreetMaps is free. For intensive use of the Bing Maps basemap options, please provide your own Bing Maps API key through the
api_keyargument, after registering at Microsoft here: https://msdn.microsoft.com/en-us/library/ff428642.aspx. Google Maps services will be implemented in a future update for restricted usage using an API key.
map_type: “satellite” (default), “hybrid”, “roadmap”, “roadmap_dark”, “roadmap_bw”, “roadmap_watercolor”.
animate_move: Increase or decrease the degree of detail of a static basemap.
animate_move: Define, if a static basemap should be cropped to the extent of
mor if a wider extent of optimal resolution should be used.
Updating unit tests for CRAN checks. Released on CRAN: 2018-09-14
Windows library detection bugs fixed. Released on CRAN: 2018-09-07
time_pos_xallow to specify the location of the timestamp display
time_sizeallows to specify the font size of the timestamp display
video support, automatic time harmonization, bug fixes. Released on CRAN: 2017-11-01
get_libraries()– handles all extern libraries that are needed for video formats. Just run it to get information on what you need to install. Replaces get_imconvert(), which can still be called for code compatibility reasons
get_formats()– outputs all file formats that can be used with moveVis depending on which libraries are installed on the system.
adding frames_layout, static_data etc., improvements to workflow. Released on CRAN: 2017-08-20
adding animate_stats() and stats arguments for animate_move(). Released on CRAN: 2017-06-28
animate_stats()– Enables creation of statistic plot animations visualizing possible relationships between movement paths and basemap. Define individual plot designs based on ggplot2 syntax.
fixing major bug. Released on CRAN: 2017-06-28
adding frame_width and frame_height arguments. Released on CRAN: 2017-06-28
Bug report contributors:
fixing important bug; adding animate_raster(). Released on CRAN: 2017-05-23
animate_raster()– for animating just basemaps/for doing the same as with animate_move(), but without movement data
Bug report contributors:
initial release. Released on CRAN: 2017-04-28
Initial example data sets:
This document should provide a broad overview on changes that are applied to the moveVis R package. There is no warranty for completeness, since minor changes might not be included. All improvement and feature descriptions are bundled per release version. The document is currently maintained by Jakob Schwalb-Willmann.