Build a map of path-based geometry, this is a simple description of the number of parts in an object and their basic structure. Translation and restructuring operations for planar shapes and other hierarchical types require a data model with a record of the underlying relationships between elements. The gibble() function creates a geometry map, a simple record of the underlying structure in path-based hierarchical types. There are methods for the planar shape types in the 'sf' and 'sp' packages and for types in the the 'trip' and in-development 'silicate' packages.
The goal of gibble is to provide a straightforward map of path-based data structures. Paths are connected linear sequences of coordinates, otherwise known as lines. Structured spatial data includes objects composed of paths, which are islands, holes within island, lines, and points. Polygons require an extra grouping level subobject to ensure holes are nested within their island, but this is ignored for other types.
The map is simply a record of the path, its size (number of vertices and geometric dimension), its groupings (which object and subobject), and its type (something like “polygon”, “line”, “point”). Internally a bare functionality works with matrices and all numeric values, but gibble then turns this set of values into a data frame where entities can be labelled arbitrarily.
Sequential linear structures are not optimal for many operations when working with spatial data, and in particular they cannot describe surfaces in 3D geometry because they are inherently, topologically, one-dimensional. Gibble provides a simple bridge between path and primitive types, which do generalize to any topological dimension. Gibble considers a point to be a degenerate path, so that the path concept is consistent for any simple features-analogue.
Please note that this project is released with a Contributor Code of Conduct. By participating in this project you agree to abide by its terms.
Fix gibble for PATH objects from silicate (when they are points).
SpatialPoints was has object column, needed for silicate.
Fixed multipoints for silicate, both sf and sp.
Fixes for SpatialLines and SpatialMultiPoints, found in anglr.