#3030: v. generalize fails to generalize polygons in a random manner ---------------------+-------------------------- Reporter: dido | Owner: grass-dev@… Type: defect | Status: new Priority: major | Milestone: 7.0.5 Component: Vector | Version: 7.0.4 Resolution: | Keywords: v.generalize CPU: x86-64 | Platform: MSWindows 7 ---------------------+--------------------------
Comment (by dido): OK, I will close the issue due to the fact that an algo rework of v.generalize not to leave too long non-generalized boundaries behind will be too costly to be implemented. Still this particular use-case needs a good explanation in the v.generalize manual. I could not find any clue that the generalize algorithm will simply stop and retain the boundary untouched IF any topology damage occurs during processing. The good workarounds must also find a way to the manual -- to slice-down the input adequately, then to apply v.generalize and v.dissolve, or to apply multiple v.generalize steps with increasing distance. Regards, Dido -- Ticket URL: <https://trac.osgeo.org/grass/ticket/3030#comment:12> GRASS GIS <https://grass.osgeo.org> _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/grass-dev