2014-04-15 16:58 GMT+02:00 Sandro Santilli :
> On Tue, Apr 15, 2014 at 04:40:34PM +0200, Reijer Copier wrote:
> > Thanks!
> >
> > We are currently considering using PostGIS Topology only to maintain
> > a topology aware copy of the data (to be used for analyses where
> > topology matters) and use
On Tue, Apr 15, 2014 at 04:40:34PM +0200, Reijer Copier wrote:
> Thanks!
>
> We are currently considering using PostGIS Topology only to maintain
> a topology aware copy of the data (to be used for analyses where
> topology matters) and use the original geometry (containing circular
> strings) whe
Thanks!
We are currently considering using PostGIS Topology only to maintain a
topology aware copy of the data (to be used for analyses where topology
matters) and use the original geometry (containing circular strings)
when we have to (re)generate output geometry.
BTW: Is cgal/sfcgal going
The problem is going to be precision.
If this is important for you you may want to switch to cgal which support
arbitrary curve in arrangment (from memory)
If precision is not important, you can easily add an uggly fix : add 2
triggers to edge table that
_when something want to access an edge, co
As long as they are simple circles, you should be able to convert back and
forth between curves and lines. Splines, beziers, et al, are probably not
going to work at all and would need to be approximated as lines.
http://boundlessgeo.com/2012/01/getting-curvey/
On Mon, Apr 14, 2014 at 8:02 AM,
Dear list,
According to the documentation, PostGIS Topology only supports edges
made out of linestrings. However, we are currently working on a dataset
that contains lots of curved geometries. It would be great if we could
build topology based on those curved geometries without having to
conv
