|
NAMEv.patch - Creates a new vector map by combining other vector maps. KEYWORDSvector, geometry, level1 SYNOPSISv.patch
Flags:
Parameters:
DESCRIPTIONv.patch allows the user to combine any number of vector maps together to create one composite vector map. If the table structures are identical, attributes are transferred to the new table. NOTESAny vectors that are duplicated among the maps being patched together (e.g., border lines) will have to be edited or removed after v.patch is run. Such editing can be done automatically using v.clean. Lines may need to be snapped with v.clean tool=snap,break,rmdupl. Boundaries may need to be cleaned with v.clean tool=break,rmdupl,rmsa repeatedly until the rmsa tool (Remove small angles at nodes) no longer modifies any boundaries. If vector topology is still not clean, boundaries may also need to be snapped with v.clean tool=snap,break,rmdupl. When using the -e flag, v.patch shifts category (cat) values in the output so that category numbers from the different input maps do not overlap. This shift is applied to both the category values of the features and the category values in the attribute tables. Hence, there is no need to run v.category and v.db.update beforehand. When using the -a flag, the user has to make sure that the features in the different maps added to the output map do not have overlapping category numbers, unless identical category numbers reflect identical attributes, otherwise the attributes of the added maps are lost. To avoid this, the user can use v.category option=sum to change category values of some of the maps before patching. EXAMPLESPatch together two maps with mixed feature types:
Append one map to another:
SEE ALSOv.clean, v.build, v.select, v.overlay AUTHORSDave Gerdes, U.S.Army Construction Engineering Research Laboratory
SOURCE CODEAvailable at: v.patch source code (history) Latest change: Sunday Mar 17 08:44:42 2024 in commit: 81301443e3c0b2a85cf634f7de17d8c23d131cd3 Main index | Vector index | Topics index | Keywords index | Graphical index | Full index © 2003-2025 GRASS Development Team, GRASS GIS 8.4.1 Reference Manual
|