map_table: A decomposition of 'vector' map data structures to tables.

View source: R/map_table.R

map_tableR Documentation

A decomposition of 'vector' map data structures to tables.

Description

Creates a set of related tables to store the appropriate entities in spatial map data.

Usage

map_table(x, ...)

Arguments

x

object to tidy

...

arguments passed to methods

Details

The basic entities behind spatial data, and hence the "map tables" are:

vertices

the positions in geometric space, e.g. x, y, z, time, long, lat, salinity etc.

branches

a single connected chain of vertices, or "parts"

objects

a collection of branches aligned to a row of metadata

This is the basic "topology" of traditional GIS vector data, for points, lines, polygons and their multi-counterparts. By default map_tables will produce these tables and also de-duplicated the input vertices, adding a fourth table to link vertices to branches.

Other topology types such as triangle or quad meshes can extend this four-entity model, or exist without the branches at all. See "mesh_table" ??

These are currently classed as object_table, branch_table, branch_link_vertex_table, and vertex_table. But there are no methods.

Value

list of tibbles


spbabel documentation built on March 31, 2023, 11:55 p.m.