Yes, it was after a call to:
OGR_G_SetPoint
that the geometry type was altered. Should really test if it's a 2.5D or 2D
geometry and use OGR_G_SetPoint_2D in the latter case!
Thanks,
SImon
On Mon, May 6, 2013 at 7:29 PM, Simon Lyngby Kokkendorff
wrote:
> Hi Even,
>
> I think you're right. The
Hi Even,
I think you're right. The transformation seems to alter the geometry type
somehow - need to debug a little more to see exactly what's going on.
Thanks,
Simon
On Mon, May 6, 2013 at 3:50 PM, Even Rouault
wrote:
> Selon Simon Lyngby Kokkendorff :
>
> > Hi List,
> >
> >I am program
Selon Simon Lyngby Kokkendorff :
> Hi List,
>
>I am programming an application which can transform ogr-datasources
> (using our own transformation library). In that process I use ogr (version
> 1.10) via the c-api to read and write datasources - usually it works like
> a charm. However, when
Hi List,
I am programming an application which can transform ogr-datasources
(using our own transformation library). In that process I use ogr (version
1.10) via the c-api to read and write datasources - usually it works like
a charm. However, when I try to write an output spatialite datasourc
