Hi Andrea,
I get the same result and can get similar result with the
following simpler line :
LINESTRING (-580 -420, -520 -340, -520 -320, 300 780)
Try to make a flat buffer of 1000.
I think the problem with flat buffer is that it is difficult to
define a clear semantic.
Round buffer is easier to define : set of points at a distance
less than the buffer size
from original geometry.
But what would be the exact definition of a flat buffer ?
One can give a clear definition of flat buffer for a single segment,
but it seems
much more difficult for a complex linestring (at least for me).
To understand what happens I suggest that you take the line
hereabove.
Simplify it (create a segment from the first point to the last
one).
Create a flat buffer of 1000 : this is what you intuitivelly want
to get from your orginal line.
Now extract segments from the line and create the flat buffer
from each segment :
some parts of these buffers are out of the global buffer. This is
where problems start.
Michaël
But if you make the flat buffer of each segment of your line (or
from the line hereabove),
you will start to see the problem.
Now you can do the flat buffer of the global line (simplified see
that
some of these partial buffers are out of the flat buffer of the
seg
If you offset the each segments of the line This later is
generally build from the segments
Le 05/08/2017 à 08:31, Jody Garnett a
écrit :
I
just did the default - guess that is 10.
--
_______________________________________________
jts-dev mailing list
jts-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.locationtech.org/mailman/listinfo/jts-dev