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 precision issue, and would not be so costly (a read of all coordinates to get min/max, then subtraction/addition for every coordinate). Maybe it could be add at the geos input/ouput level, thus not necessitating to change all code? Cheers, Rémi-C 2014-02-03 Sandro Santilli <[email protected]>: > 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 operations, maybe the GEOSOffsetCurve method should > be changed to _use_ the BinaryOp class (detail more useful in a GEOS > ticket, > btw). > > --strk; > _______________________________________________ > postgis-users mailing list > [email protected] > http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users >
_______________________________________________ postgis-users mailing list [email protected] http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
