<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">My best guess is each line is creating a close polyline - which is why the islands do not have duplicate points. <div><br></div><div>We wrote a program to run though each line, identify the location each line begins to backtrack, then break and remove the remaining points. Unfortunately, some of the contours do not start and stop at the edge of the DEM, but rather have beginning nodes many points within the DEM. Anything on the "back side" of the node is dropped.<div><br></div><div><img height="477" width="746" apple-width="yes" apple-height="yes" src="cid:FA5D7AA0-DA2C-42B2-9F03-0D55BA67AFCB"><br><div apple-content-edited="true"> <div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div><br></div><div><br></div><div>Heidi Ochis</div><div>Computer Terrain Mapping, Inc</div><div>420 21st Ave, Suite 114</div><div>Longmont, CO 80501</div><div>303-444-1670</div><div><a href="mailto:hiho@ctmap.com">hiho@ctmap.com</a></div></div></div><div style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><br></div></div><br class="Apple-interchange-newline"></div><br class="Apple-interchange-newline"> </div><br><div><div>On May 2, 2018, at 12:32 AM, Markus Metz wrote:</div><br class="Apple-interchange-newline"><div dir="ltr"><div><div>Hi Peter,<br><br>On Tue, May 1, 2018 at 11:33 PM, Peter Tittmann <<a href="mailto:ptittmann@gmail.com">ptittmann@gmail.com</a>> wrote:<br>><br>> Hi Markus,<br>><br>> I'm ashamed to admit that I hacked my way into fixing this problem by exporting the vector dataset using `v.out.ogr` to a geopackage then importing it. The cleaning tools in v.in.ogr seemed to solve my problem..<br><br></div>the reason why this works is that these incorrect boundaries are not exported. When re-importing, you will get a clean vector but some of the original areas are gone. If you still want to find out what went wrong where, you would need to find out where these incorrect boundaries first appeared in the processing steps of your original vector.<br><br></div>Markus M<br><div><div><br>><br>> Very clumsy, but it worked.<br>><br>> Thank you!<br>><br>> Peter<br>><br>> On Fri, Apr 27, 2018 at 11:51 AM, Markus Metz <<a href="mailto:markus.metz.giswork@gmail.com">markus.metz.giswork@gmail.com</a>> wrote:<br>>><br>>> [ please keep this on the GRASS mailing list ]<br>>><br>>> On Fri, Apr 27, 2018 at 6:43 PM, Peter Tittmann <<a href="mailto:ptittmann@gmail.com">ptittmann@gmail.com</a>> wrote:<br>>> ><br>>> > Hi Markus,<br>>> ><br>>> > grass72 -v<br>>> > GRASS GIS 7.2.2<br>>><br>>> This is already the latest 7.2 release. You might try GRASS 7.4.<br>>><br>>> ><br>>> > i will try to figure out how to get the latest release up and running. If you have any suggestions for fixing the boundaries, that would be great.<br>>><br>>> If upgrading to the latest GRASS 7.4 release does not help, I would need the data for testing to find out why removing small areas fails. If the vector has been imported from an external datasource without modification of the geometries inside GRASS, this version would be preferable. Otherwise the history of plot_pa_with_lidar@project_area would be helpful (<a href="http://v.info">v.info</a> -h).<br>>><br>>> Markus M<br>>> ><br>>> > Peter<br>>> ><br>>> > On Thu, Apr 26, 2018 at 11:19 PM, Markus Metz <<a href="mailto:markus.metz.giswork@gmail.com">markus.metz.giswork@gmail.com</a>> wrote:<br>>> >><br>>> >><br>>> >><br>>> >> On Fri, Apr 27, 2018 at 1:37 AM, Peter Tittmann <<a href="mailto:ptittmann@gmail.com">ptittmann@gmail.com</a>> wrote:<br>>> >> ><br>>> >> > Hi,<br>>> >> ><br>>> >> > I am attempting to use the `rmarea` tool in v.clean with a threshold of ~ 1000 sq meters.<br>>> >> ><br>>> >> [...]<br>>> >><br>>> >> ><br>>> >> > I am getting a rather cryptic message ‘Failed to build area’.<br>>> >> ><br>>> >> > > v.clean -c --overwrite --verbose input=plot_pa_with_lidar@project_area output=plot_pa_rmarea tool=rmarea threshold=1017.2<br>>> >> > --------------------------------------------------<br>>> >> > Tool: Threshold<br>>> >> > Remove small areas: 1017.2<br>>> >> > --------------------------------------------------<br>>> >> > WARNING: Vector map <plot_pa_rmarea> already exists and will be overwritten<br>>> >> > Using native format<br>>> >> > Copying features...<br>>> >> > 100%<br>>> >> > Rebuilding parts of topology...<br>>> >> > Building topology for vector map <plot_pa_rmarea@project_area>...<br>>> >> > Registering primitives...<br>>> >> > 1720636 primitives registered<br>>> >> > 3439992 vertices registered<br>>> >> > Building areas...<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > WARNING: Area of size = 0.0 ignored<br>>> >> > 100%<br>>> >> > 499671 areas built<br>>> >> > 6004 isles built<br>>> >> > Attaching islands...<br>>> >> > 100%<br>>> >> > Attaching centroids...<br>>> >> > 100%<br>>> >> > Topology was built<br>>> >> > Number of nodes: 728615<br>>> >> > Number of primitives: 1720636<br>>> >> > Number of points: 0<br>>> >> > Number of lines: 0<br>>> >> > Number of boundaries: 1222309<br>>> >> > Number of centroids: 498327<br>>> >> > Number of areas: 499671<br>>> >> > Number of isles: 6004<br>>> >> > WARNING: Number of incorrect boundaries: 9<br>>> >> > WARNING: Number of duplicate centroids: 14<br>>> >> > --------------------------------------------------<br>>> >> > Tool: Remove small areas<br>>> >> > ERROR: Failed to build new area<br>>> >><br>>> >> I guess the problem are these 9 incorrect boundaries. Which GRASS version are you using? Can you try again with the latest release in case you are not using the latest release?<br>>> >><br>>> >> Markus M<br>>> ><br>>> ><br>><br>><br></div></div></div> _______________________________________________<br>grass-user mailing list<br><a href="mailto:grass-user@lists.osgeo.org">grass-user@lists.osgeo.org</a><br>https://lists.osgeo.org/mailman/listinfo/grass-user</div><br></div></div></body></html>