Defines types of spatial data on a linear network and provides
functionality for geometrical operations, data analysis and modelling
of data on a linear network, in the 'spatstat' family of packages.
Contains definitions and support for linear networks, including
creation of networks, geometrical measurements, topological
connectivity, geometrical operations such as inserting and deleting
vertices, intersecting a network with another object, and interactive
editing of networks. Data types defined on a network include point
patterns, pixel images, functions, and tessellations. Exploratory
methods include kernel estimation of intensity on a network,
K-functions and pair correlation functions on a network, simulation
envelopes, nearest neighbour distance and empty space distance,
relative risk estimation with cross-validated bandwidth selection.
Formal hypothesis tests of random pattern (chi-squared,
Kolmogorov-Smirnov, Monte Carlo, Diggle-Cressie-Loosmore-Ford,
Dao-Genton, two-stage Monte Carlo) and tests for covariate effects
(Cox-Berman-Waller-Lawson, Kolmogorov-Smirnov, ANOVA) are also
supported. Parametric models can be fitted to point pattern data using
the function lppm() similar to glm(). Only Poisson models are
implemented so far. Models may involve dependence on covariates and
dependence on marks. Models are fitted by maximum likelihood. Fitted
point process models can be simulated, automatically. Formal
hypothesis tests of a fitted model are supported (likelihood ratio
test, analysis of deviance, Monte Carlo tests) along with basic tools
for model selection (stepwise(), AIC()) and variable selection (sdr).
Tools for validating the fitted model include simulation envelopes,
residuals, residual plots and Q-Q plots, leverage and influence
diagnostics, partial residuals, and added variable plots. Random point
patterns on a network can be generated using a variety of models.
Functionality for data analysis and modelling of spatial data, mainly
spatial point patterns, in the 'spatstat' family of packages.
(Excludes analysis of spatial data on a linear network, which is
covered by the separate package 'spatstat.linnet'.) Exploratory
methods include quadrat counts, K-functions and their simulation
envelopes, nearest neighbour distance and empty space statistics, Fry
plots, pair correlation function, kernel smoothed intensity, relative
risk estimation with cross-validated bandwidth selection, mark
correlation functions, segregation indices, mark dependence
diagnostics, and kernel estimates of covariate effects. Formal
hypothesis tests of random pattern (chi-squared, Kolmogorov-Smirnov,
Monte Carlo, Diggle-Cressie-Loosmore-Ford, Dao-Genton, two-stage Monte
Carlo) and tests for covariate effects (Cox-Berman-Waller-Lawson,
Kolmogorov-Smirnov, ANOVA) are also supported. Parametric models can
be fitted to point pattern data using the functions ppm(), kppm(),
slrm(), dppm() similar to glm(). Types of models include Poisson,
Gibbs and Cox point processes, Neyman-Scott cluster processes, and
determinantal point processes. Models may involve dependence on
covariates, inter-point interaction, cluster formation and dependence
on marks. Models are fitted by maximum likelihood, logistic
regression, minimum contrast, and composite likelihood methods. A
model can be fitted to a list of point patterns (replicated point
pattern data) using the function mppm(). The model can include random
effects and fixed effects depending on the experimental design, in
addition to all the features listed above. Fitted point process models
can be simulated, automatically. Formal hypothesis tests of a fitted
model are supported (likelihood ratio test, analysis of deviance,
Monte Carlo tests) along with basic tools for model selection
(stepwise(), AIC()) and variable selection (sdr). Tools for validating
the fitted model include simulation envelopes, residuals, residual
plots and Q-Q plots, leverage and influence diagnostics, partial
residuals, and added variable plots.
Defines sparse three-dimensional arrays and supports standard
operations on them. The package also includes utility functions for
matrix calculations that are common in statistics, such as quadratic
forms.
Defines types of spatial data such as point patterns, mainly in two
dimensions, but also in higher dimensions. Provides class support, and
functions for geometrical operations on spatial data, used in the
'spatstat' family of packages. Excludes spatial data on a linear
network, which are covered by the separate package 'spatstat.linnet'.
# Please note that **rgdal** will be retired by the end of 2023, plan
transition to sf/stars/terra functions using GDAL and PROJ at your
earliest convenience.
# Version 1.5-27 (development, rev. 1149-)
* Correcting logic error in check for MXE UCRT builds (temporary)
# Version 1.5-26 (2021-09-15, rev. 1141-1148)
* Mute use of PROJ CDN for MXE UCRT builds (temporary)
* Run autoupdate on configure.ac to handle obsolete AC_HELP_STRING etc.
# Version 1.5-25 (2021-09-08, rev. 1122-1140)
* Add environment variable access to --with-data-copy by
PROJ_GDAL_DATA_COPY (https://github.com/r-spatial/sf/issues/1605)
* Adaptations for PROJ 8.
* Handle mixed 2D/3D in readOGR():
(https://github.com/r-spatial/sf/issues/1683)
* Add tweak for UCRT builds.
* Thin examples for spTransform().
# Version 1.5-23 (2021-02-03, rev. 1120-1121)
* Further fallout after removing valgrind issues.
# Version 1.5-22 (2021-02-02, rev. 1106-1119)
* Attempt to remove further valgrind leak in proj6.cpp: PROJcopyEPSG()
and in ogr_proj.cpp, both wrongly placed object destructors.
* Modified roundtripping all declared projections in ?project examples
because some listed projections for PROJ >= 5 provoke valgrind
leakages by returning very large out-of-scope values for input
coordinates (0, 0); inversion of these is not attempted; some listed
projections are not projections.
# Version 1.5-21 (2021-01-27, rev. 1093-1105)
* Suggest **rgeos** to write pre-SFS multipolygon objects to avoid
unpleasant workaround.
* Try to eliminate current valgrind leaks, starting from
(https://github.com/r-spatial/gstat/issues/82).
* Try to increase robustness to installation with early PROJ 6
versions, which often lack functionality found necessary later (for
example visualization order); the code had assumed that this
function always was available and behaved as it now does. There are
now graceful failures when not available.
# Version 1.5-19 (2021-01-05, rev. 1083-1092)
* Dan Baston: raster speedups
* PROJ 7.2.1 includes a bug-fix for `+proj=ob_tran` cases that
required changes in detection and handling of target/source CRS
reversal,
https://lists.osgeo.org/pipermail/proj/2020-December/009999.html
# Version 1.5-18 (2020-10-13, rev. 1071-1082)
* condition `tests/test_enforce_xy.R` on PROJ >= 6 and GDAL >= 3
(email BDR, I forgot to re-check with PROJ-5.2.0/GDAL-2.2.4).
* Adaptation to EPSG 10 database format started (from PROJ 7.2);
choose DB columns by name not number in vignette.
# Version 1.5-17 (2020-10-08, rev. 1051-1070)
* `"CRS"` instantiation now prefers PROJ: use
`rgdal::set_prefer_proj(FALSE)` to return to earlier behaviour. It
seems that access from C/C++ code to mechanisms in PROJ offers more
depth than going through GDAL to PROJ. This `"CRS"` instantiation in
**sp** and **raster**; Proj4 and WKT2 strings may differ depending
on whether instantiation is straight from PROJ or goes via
GDAL. Confirmed with multiple reverse dependency checks over almost
900 CRAN packages.
* By default use PROJ function to extract the source CRS from a
`"BOUNDCRS"`. When `+towgs84=` is given, PROJ and GDAL see the
apparent source Proj4 string as implicitly implying a coordinate
operation transforming to target WGS84, leading to the WKT2
representation being a `"BOUNDCRS"`, not a `"PROJCRS"` or
`"GEOGCRS"`, and thus causing misunderstandings later in searching
for the most accurate coordinate operation for a transformation. May
be controlled by setting the `get_source_if_boundcrs=` in
`sp::CRS()` from **sp** 1.4-4 (2020-10-07). Confirmed with multiple
reverse dependency checks over almost 900 CRAN packages.
* Add support for instantiating from `"OGC:CRS84"` to provide a
guaranteed GIS/visualization axis order WGS84 instantiator
(preferred to `"EPSG:4326"`).
* Permit empty string in `SRS_string=` argument to `sp::CRS()` and
functions called by it.
* Use GDAL `ORSIsProjected()` instead of simply looking for
`"+proj=longlat"` in the Proj4 string representation where possible.
# Version 1.5-16 (2020-08-07, rev. 1047-1050)
* Typo in C code; use `try()` around Area-of-Interest calculation for
coordinate operations (email BDR, I forgot to re-check with
PROJ-5.2.0/GDAL-2.2.4).
# Version 1.5-15 (2020-08-04, rev. 1020-1046)
* Add support for instantiating from `"ESRI:"`.
* Add Area-of-Interest to coordinate operation search (reduces the
number of candidates found in many cases), and use in
`rgdal::spTransform()` by default (`use_aoi=FALSE` to suppress);
illustrate in vignette
https://cran.r-project.org/web/packages/rgdal/vignettes/CRS_projections_transformations.html.
* Harden to condition on PROJ functions only available from 6.2.0;
block `"+proj=ob_tran` tests for PROJ 6.0.0-6.1.1.
* Support PROJ CDN https://cdn.proj.org for on-demand download of
transformation grids if requested by user; document in vignette
https://cran.r-project.org/web/packages/rgdal/vignettes/CRS_projections_transformations.html.
# Version 1.5-12 (2020-06-26, rev. 1007-1019)
* Further corrections to `configure.ac` for older PROJ/GDAL versions
# Version 1.5-10 (2020-06-09, rev. 991-1006)
* Corrections to `configure.ac` for older PROJ/GDAL versions
# Version 1.5-8 (2020-05-28, rev. 846-990)
* Released to match **sp** 1.4.0 (2020-02-21) to 1.4-2 (2020-05-20)
following months of development adapting to breaking changes in the
external libraries used here: PROJ and GDAL; see also
https://cran.r-project.org/web/packages/sp/news.html.
* Expose `options("rgdal_show_exportToProj4_warnings"="none")` to mute
Proj4 string degradation warnings.
* Add new vignette
https://cran.r-project.org/web/packages/rgdal/vignettes/CRS_projections_transformations.html.
* CRAN Windows binary uses PROJ >= 6 and GDAL >= 3
* Add PROJ-based CRS comparison: `compare_CRS()`.
* `project()` and `spTransform()` use WKT2 comment if available,
fallback to Proj4 representation if not.
* List coordinate operations (based on pyproj code): `list_coordOps()`.
* Add `enforce_xy=` arguments to try to ensure that only
GIS/visualization axis order is present.
* Add `"CRS"` object comment carrying WKT2 (2019) multiline string
representation on read operations.
* Use `"CRS"` object comment carrying WKT2 (2019) multiline string
representation on write operations.
CHANGES IN spatstat.utils VERSION 2.2-0
OVERVIEW
o New function to compute breakpoints for a cut operation.
o Internal tweaks to improve efficiency.
NEW FUNCTIONS
o exactCutBreaks
Compute the exact numerical values of the breakpoints
used in cut.default.
CHANGES IN spatstat.utils VERSION 2.1-0
OVERVIEW
o New functions providing NA and zero values, and empty vectors,
of the appropriate type.
NEW FUNCTIONS
o RelevantNA
Return a missing value of the appropriate type.
o RelevantEmpty
Return a zero-length vector of the appropriate type.
o RelevantZero
Return a value equivalent to 0, of the appropriate type.
CHANGES IN spatstat.utils VERSION 2.0-1
OVERVIEW
o Tweaks.
CHANGES IN spatstat.utils VERSION 2.0-0
OVERVIEW
o Updated to new spatstat family.
SIGNIFICANT USER-VISIBLE CHANGES
o package dependence
spatstat.utils now suggests the package spatstat.core
which is part of the new spatstat family.
CHANGES IN spatstat.utils VERSION 1.20-0
OVERVIEW
o Computation is slightly accelerated.
SIGNIFICANT USER-VISIBLE CHANGES
o general
Overall speed of computation is slightly increased.
CHANGES IN spatstat.utils VERSION 1.19-0
OVERVIEW
o Minor improvements.
CHANGES IN spatstat.utils VERSION 1.18-0
OVERVIEW
o Minor improvements.
SIGNIFICANT USER-VISIBLE CHANGES
o do.call.matched, do.call.without
New argument 'envir' determines the environment in which
the call will be evaluated.
# version 1.0-2
* `st_read()` and `st_write()` using GDAL handle binary attributes
(OFTBinary fields) ; #1721
* a `pivot_longer` method is added for `sf` objects (the `data.frame`
method works, but raises a warning)
* `rbind.sf` preserves primary geometry column; #1717
* `configure` constrains using `--static` to `Darwin` platform; #1702,
#1712, #1713
* old-style `crs` objects created with sf < 0.9-0 generate a message,
and will cause a warning in the future.
* when `st_crs()` is called with a WKT2 as text input, its `input`
field will be replaced with the CRS name (if it has one).
* GEOS (>= 3.9.0) operations use `GEOSGeom_setPrecision_r` to set
precision of geometries; #1535
* `st_read()` with specified `query` ignores argument `layers`, and
warns if it is given; #1444
# version 1.0-1
* fix regression in `st_intersection()`: when using s2 attributes were
assigned wrongly; #1704
* `crs` (sf) to `CRS` (sp) conversion no longer needs validation by
`rgdal`; https://github.com/edzer/sp/issues/107
* retrieve ESRI's WKT version of CRS by `st_crs(id)$WKT1_ESRI`; #1690
# version 1.0-0
* add `s2` to Imports:
* add Dewey Dunnington to contributors
* `sf_use_s2()` prints a message when using s2 has been switched to on or off.
* use `s2` spherical geometry as default when coordinates are ellipsoidal. This can
be switched off (defaulting to planar geometry, using GEOS, as in sf < 1.0-0)
by setting environment variable `_SF_USE_S2` to `false` before package `sf`
is loaded, or by `sf_use_s2(FALSE)`; #1649
* `st_nearest_feature()` with missing `y` returns nearest features in
the remaining set of `x`; https://github.com/r-spatial/s2/issues/111
* `st_write()` gains an argument `config_options` to set GDAL config
options; #1618
* fix regression in `sf_project(..., keep = TRUE)`; #1635
Provides R bindings for Google's s2 library for geometric calculations
on the sphere. High-performance constructors and exporters provide
high compatibility with existing spatial packages, transformers
construct new geometries from existing geometries, predicates provide
a means to select geometries based on spatial relationships, and
accessors extract information about geometries.
Provides a minimal R and C++ API for parsing well-known binary and
well-known text representation of geometries to and from R-native
formats. Well-known binary is compact and fast to parse; well-known
text is human-readable and is useful for writing tests. These formats
are only useful in R if the information they contain can be accessed
in R, for which high-performance functions are provided here.
# Please note that **rgeos** will be retired by the end of 2023, plan
transition to sf functions using GEOS at your earliest convenience.
# Version 0.5-7 (development, rev. 641-675)
* adapt to OverlayNG in GEOS 3.9
* update Windows static library to GEOS 3.9
* add gMinumumRotatedRectangle() and gMaximumInscribedCircle() for GEOS 3.9
* adapt configure.ac for GEOS 3.10
* add support for structured geometry fixer in gMakeValid() from 3.10
# countrycode 1.3.0
* destination argument accepts a vector of strings and tries one after
the other
* countryname(warn=TRUE) by default
* better class checks
* countryname defaults to `country.name.en` for missing country names
(nomatch=NULL)
* Vietnam: better regex and support for vdem
* Namibia fixes: eurostat, genc2c, wb_api2c, ecb
* Various regex improvements
* Congo French disambiguation
# countrycode 1.2.0
* New 'countryname' function converts country names from any language
(thanks to @davidsjoberg)
* New `guess_field` function guesses which code a vector uses
* Bug in dict build inserted NA in region variable (Thanks to M. Pascariu)
* Added region23 with the old, more granular regions
* Added unicode.symbol, which converts to emoji flags
* Added ISO 4217 currency name, alpha, and numeric codes
* Added UN region codes and names
* Added IANA ccTLD codes
* Improved various regexes
# countrycode 1.1.3
* Added Demographic and Health Surveys (thanks to @mcooper)
# countrycode 1.1.2
* Updated World Bank regions with manual additions
# countrycode 1.1.1
* Bug: Typo prevented users for using "p4n" as origin code
* Fixed bad icao.region codes (Thanks to @espinielli)
* Added country name "United Arab Republic" and its regex (Thanks to
Gina Reynolds)
* Added SOM to wb code (Thanks to Fabian Besche)
* Added Vietnam to codelist_panel
# viridisLite 0.6.1
## New features
* N/A.
## Minor improvements and fixes
* Include unemployment data in package to avoid CRAN check errors when original
data is not accessible.
---
# viridisLite 0.6.0
## New features
* Add 3 more color maps: mako, rocket, and turbo.
## Minor improvements and fixes
* Minor bug fixes and improvements here and there.
1.5-12
o use pkg-config --static --libs when needed
o adapt to API changes in R 4.0.0, also improves symbol
placement in recent R versions
1.5-11 (2020-02-26)
o fixed missing PROTECT() (thanks to Tomáš Kalibera)
o minor changes to remove R CMD check warnings
# viridisLite 0.4.0
## New features
* Add 3 more color maps: mako, rocket, and turbo.
## Minor improvements and fixes
* Minor bug fixes and improvements here and there.
# manipulateWidget 0.11.0 (2020-03-21)
## New features
* New comparison mode: the UI generated with `manipulateWidget()` has
now new controls to enter in comparison mode, choose the number of
charts, the layout and the variables to compare.
* `compareOptions()` gains a new argument `allowCompare` to hide/show
the new controls presented above.
* New function `mwTranslations()` to translate UI elements.
* UI has been slightly reworked.
## Bug Fixes
* The number of unnecesary updates has been decreased resulting in
better performance.
* Sometimes, there were some conflict when a parameter in
`manipulateWidget()` had the same name as a variable in the global
environment.
* `mwSelect(multiple = TRUE)` was not updating charts when selection
was empty.
* `staticPlot()` was evaluating expressions in the wrong environment.
## Breaking changes
* shiny applications using functions `mwModule()` and `mwModuleUI()` :
you have to passed directly ui options like buttons on
`mwModuleUI()` rather than in `mwModule()`
An R interface to the 'codediff' JavaScript library (a copy of which
is included in the package, see <https://github.com/danvk/codediff.js>
for information). Allows for visualization of the difference between 2
files, usually text files or R scripts, in a browser.
A tool to provide an easy, intuitive and consistent access to
information contained in various R models, like model formulas, model
terms, information about random effects, data that was used to fit the
model or data from response variables. 'insight' mainly revolves
around two types of functions: Functions that find (the names of)
information, starting with 'find_', and functions that get the
underlying data, starting with 'get_'. The package has a consistent
syntax and works with many different model objects, where otherwise
functions to access these information are missing.
0.1-9 2021-07-24
o use R_ClearExternalPtr() instead of CAR()=0 to
be more API-compliant
o minor R API compliance cleanup
o added native symbol registration
