2017-11-12 19:50 GMT+02:00 Moritz Lennert <mlenn...@club.worldonline.be>: > MarkusM is the one who really knows, but AFAIU, the GEOS implementation > of buffering is the best we have (or the only one without errors in > specific cases). There is not function for creating parallel lines in > GEOS, so for that the functions in buffer2.c are the best we have, but > they are pretty bad. Apparently, creating a parallel line is not as > simple as it would sound, and we are still looking for a correct > implementation, or rather to even see if such an implementation is > possible. I played around with native buffering (both versions) and they both look similarly bad :( Thus I made v.profile to hard depend on GEOS buffers (no native option) till we manage to fix problems with native buffering. Please test if trunk seems to be OK now (I added also a test case based on your example). r71769 will need a backport if there will be no objections.
> Moritz Māris. _______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev
