ng?
>
> Opened a ticket at GEOS referencing to this discussion:
> http://trac.osgeo.org/geos/ticket/682
>
> (hopefully I put it in the rigtht place)
>
> -jakob
>
>
>
> > Date: Mon, 3 Feb 2014 11:37:03 +0100
> > From: s...@keybit.net
> > To: postgis-users
ostgis-users] Problems with ST_OffsetCurve
>
> On Mon, Feb 03, 2014 at 11:29:13AM +0100, Rémi Cura wrote:
> > By the way Sandro,
> >
> > don't you think that Geos should automatically translate the whole input
> > using a pivot point ?
> > It would of course
On Mon, Feb 03, 2014 at 11:29:13AM +0100, Rémi Cura wrote:
> By the way Sandro,
>
> don't you think that Geos should automatically translate the whole input
> using a pivot point ?
> It would of course be difficult when getting data pieces by pieces (like in
> aggregates),
> but when the whole dat
By the way Sandro,
don't you think that Geos should automatically translate the whole input
using a pivot point ?
It would of course be difficult when getting data pieces by pieces (like in
aggregates),
but when the whole data is available, why not?
It would considerably help toward reducing the
On Mon, Feb 03, 2014 at 10:54:13AM +0100, Rémi Cura wrote:
> Hey,
> you use far too big coordinates.
> Please consider using st translate on your data, then curve offset, then
> inverse translate.
Speaking of which, this treatment is one of those performed on catching
an exception in binary operat
Oups I put a -15 translation in above example, it also works for -16 of
course like required.
Cheers,
Rémi-C
2014-02-03 Rémi Cura :
> Hey,
> you use far too big coordinates.
> Please consider using st translate on your data, then curve offset, then
> inverse translate.
> This is mandatory (when
Hey,
you use far too big coordinates.
Please consider using st translate on your data, then curve offset, then
inverse translate.
This is mandatory (when using so many digits, you artificially increase the
need for precision in numeric computing, which is problematic).
It is true for all computati
On Mon, Feb 03, 2014 at 11:43:37AM +0300, jakob ventin wrote:
> Hello all,
> I am using ST_OffsetCurve function to calculate offsets for lines and
> polygons. I have a quit large amount of data, several tens of thousands of
> features which I have to do these calculations for in an automated proc
Hello all,
I am using ST_OffsetCurve function to calculate offsets for lines and polygons.
I have a quit large amount of data, several tens of thousands of features which
I have to do these calculations for in an automated processs. Now I have run
into a problem: St_OffsetCurve crashes for some
