Vector topology cleaning: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
(+Polygon import from SHAPE file:) |
||
| Line 16: | Line 16: | ||
Note: There are some modules that do not like self-intersecting lines, e.g with {{cmd|v.buffer}} problems are expected. | Note: There are some modules that do not like self-intersecting lines, e.g with {{cmd|v.buffer}} problems are expected. | ||
---- | |||
'''Polygon import from SHAPE file:''' | |||
[[Image:Polygons overlapping.png|center|thumb|300px|Overlayed polygons after import from SHAPE file (Simple Features]] | |||
v.clean applied: | |||
[[Image:Polygons overlapping cleaned.png|center|thumb|300px|Overlayed polygons topologically cleaned. Note the double categories.]] | |||
=== See also === | === See also === | ||
Revision as of 18:21, 2 January 2012
Q: How can I patch to fitting area maps with have been digitized separately and correct the topology? I observe that the shared polygon boundaries do not perfectly match...
A: You can use v.clean for this.
Tools to consider:
- TBD
- ...
Q: How about self-intersecting lines and boundaries?
A: In the GRASS topological model self-intersecting lines are allowed, self-intersecting boundaries are not. Self-intersecting lines are ok e.g. for v.net modules, e.g. to represent a bridge of a secondary road over a highway.
Note: There are some modules that do not like self-intersecting lines, e.g with v.buffer problems are expected.
Polygon import from SHAPE file:
v.clean applied:
