Index of /
No Clocks
Mapping files
The Ultimate List of GIS Formats and Geospatial File Extensions - GIS Geography
The Ultimate List of GIS Formats and Geospatial File Extensions
mapshaper
Mass Effect Wiki | Fandom
Mass Effect Wiki is a comprehensive database for the Mass Effect video game series. The wiki is dedicated to collecting all information related to the franchise, such as classes, characters, races, walkthroughs, assignments and more!
Including function calls in error messages — topic-error-call
Starting with rlang 1.0, abort() includes the erroring function in the message by default:
my_function <- function() {
abort("Can't do that.")
}
my_function()
#> Error in `my_function()`:
#> ! Can't do that.
This works well when abort() is called directly within the failing function. However, when the abort() call is exported to another function (which we call an "error helper"), we need to be explicit about which function abort() is throwing an error for.
This works well when abort() is called directly within the failing function. However, when the abort() call is exported to another function (which we call an "error helper"), we need to be explicit about which function abort() is throwing an error for.
There are two main kinds of error helpers:
Simple abort() wrappers. These often aim at adding classes and attributes to an error condition in a structured way:
stop_my_class <- function(message) {
abort(message, class = "my_class")
}
Input checking functions. An input checker is typically passed an input and an argument name. It throws an error if the input doesn't conform to expectations:
check_string <- function(x, arg = "x") {
if (!is_string(x)) {
cli::cli_abort("{.arg {arg}} must be a string.")
}
}
To fix this, let abort() know about the function that it is throwing the error for by passing the corresponding function environment as the call argument:
sysxplore
Sysxplore explores DevOps, Cloud, and Linux topics in a straightforward way, making complex concepts easy to grasp. Our goal is to deliver technical information and make it enjoyable to learn.
LandGate | Business Solutions
LandGate provides end-to-end solutions for energy developers, investors, and institutional landowners.
Codeberg.org
Codeberg is a non-profit community-led organization that aims to help free and open source projects prosper by giving them a safe and friendly home.
Kart: DVC for geospatial and tabular data. Git for GIS | Hacker News
Cloud-Optimized Geospatial Formats Guide
Cloud-Native Geospatial Forum - CNG
Where geospatial data users create the future together.
Filmdrop • Element 84
FilmDrop is a suite of open source tools for ingesting, archiving, processing, analyzing and distributing geospatial data in the cloud.
GeoArrow
Home - Overture Maps Foundation
Linux Foundation Project
Cartographic boundary
TRACT
Fips
Cartographic boundary file
Tiger data products guide
Complete technical documentation
Tiger
Kart — Kart 0.17.0 documentation
Kart — Distributed version-control for geospatial and tabular data
Distributed version-control for geospatial and tabular data
gdalraster: Bindings to 'GDAL'
API bindings to the Geospatial Data Abstraction Library ('GDAL', ). Implements the 'GDAL' Raster and Vector Data Models. Bindings are implemented with 'Rcpp' modules. Exposed C++ classes and stand-alone functions wrap much of the 'GDAL' API and provide additional functionality. Calling signatures resemble the native C, C++ and Python APIs provided by the 'GDAL' project. Class 'GDALRaster' encapsulates a 'GDALDataset' and its raster band objects. Class 'GDALVector' encapsulates an 'OGRLayer' and the 'GDALDataset' that contains it. Initial bindings are provided to the unified 'gdal' command line interface added in 'GDAL' 3.11. C++ stand-alone functions provide bindings to most 'GDAL' "traditional" raster and vector utilities, including 'OGR' facilities for vector geoprocessing, several algorithms, as well as the Geometry API ('GEOS' via 'GDAL' headers), the Spatial Reference Systems API, and methods for coordinate transformation. Bindings to the Virtual Systems Interface ('VSI') API implement standard file system operations abstracted for URLs, cloud storage services, 'Zip'/'GZip'/'7z'/'RAR', in-memory files, as well as regular local file systems. This provides a single interface for operating on file system objects that works the same for any storage backend. A custom raster calculator evaluates a user-defined R expression on a layer or stack of layers, with pixel x/y available as variables in the expression. Raster 'combine()' identifies and counts unique pixel combinations across multiple input layers, with optional raster output of the pixel-level combination IDs. Basic plotting capability is provided for raster and vector display. 'gdalraster' leans toward minimalism and the use of simple, lightweight objects for holding raw data. Currently, only minimal S3 class interfaces have been implemented for selected R objects that contain spatial data. 'gdalraster' may be useful in applications that need scalable, low-level I/O, or prefer a direct 'GDAL' API.
IPUMS NHGIS | National Historical Geographic Information System
PowerShell is fun :)Managing your WSL instances in PowerShell using the WSL Module
I use WSL instances on my machine in VSCode to test and develop scripts, as well as to easily test Linux-based applications on my Windows machine. In this blog post, I will show how the Module work…
The Truth About Tidy Wrappers – Outsider Data Science
Are Tidyverse wrappers around powerful database engines really worth it?
Outsider Data Science
Using S7 in a package