wk: Lightweight Well-Known Geometry Parsing

Canonical link: https://rscholar.com/pkg/wk

Dewey Dunnington • Edzer Pebesma • Anthony North • View description and downloads View dependencies GitHub project

2020 Published

0.9.3 Version

0 Citations

3 Authors

Referenced by ⇅	Year
wellknown: Convert Between "WKT" and "GeoJSON" (Version 0.7.4)	2015
rsgeo: An Interface to Rust's 'geo' Library (Version 0.1.7)	2023
PROJ: Generic Coordinate System Transformations Using 'PROJ' (Version 0.5.0)	2020
apcf: Adapted Pair Correlation Function (Version 0.3.1)	2019
arcgisplaces: Search for POIs using ArcGIS 'Places Service' (Version 0.1.0)	2024
bigrquerystorage: An Interface to Google's 'BigQuery Storage' API (Version 1.1.0)	2024
bigrquery: An Interface to Google's 'BigQuery' 'API' (Version 1.5.1)	2015
ceramic: Download Online Imagery Tiles (Version 0.9.5)	2019
fasterize: Fast Polygon to Raster Conversion (Version 1.0.5)	2018
geoarrow: Extension Types for Spatial Data for Use with 'Arrow' (Version 0.2.1)	2024
geos: Open Source Geometry Engine ('GEOS') R API (Version 0.2.4)	2020
mregions2: Access Data from Marineregions.org: Gazetteer & Data Products (Version 1.1.1)	2024
neotoma2: Working with the Neotoma Paleoecology Database (Version 1.0.5)	2023
redistmetrics: Redistricting Metrics (Version 1.0.7)	2021
rgbif: Interface to the Global Biodiversity Information Facility API (Version 3.8.0)	2012
rosm: Plot Raster Map Tiles from Open Street Map and Other Sources (Version 0.3.0)	2015
s2: Spherical Geometry Operators Using the S2 Geometry Library (Version 1.1.7)	2016
sf: Simple Features for R (Version 1.0-17)	2016
soilDB: Soil Database Interface (Version 2.8.4)	2012
spocc: Interface to Species Occurrence Data Sources (Version 1.2.3)	2014
wkutils: Utilities for Well-Known Geometry Vectors (Version 0.1.3)	2020

RPKG Scholar presents a tabulation of an author's contribution in the development of R packages stored in the Comprehensive R Archive Network (CRAN). Within this site, we consider package dependencies (suggests,imports,depends,enhances) as citations because we believe that using one's package to develop another is tantamount to citing the author of the package being imported, suggested or enhanced.