|
Re: Encounter Segmentation Fault with GEOS 2.2.2: msg#00098gis.geos.devel
Sheng Liang (SH/CBC) wrote: > HI: > I have tried aString1.c_str(), but I still get the same > error. And I even use such code: > GEOSGeom aPolygon1,aPolygon2; > const char *aString1 = "POLYGON ((125.331 0,3.35823e-06 > 125.331,-125.331 6.71646e-06,-1.00747e-05 -125.331,125.331 0))"; > > const char *aString2 = "POLYGON ((245.331 120,120 245.331,-5.331 > 120,120 -5.331,245.331 120))"; > > > aPolygon1 = GEOSGeomFromWKT(aString1); > aPolygon2 = GEOSGeomFromWKT(aString2); > > GEOSGeom anIntersection = GEOSIntersection(aPolygon1,aPolygon2); > > And the error is the same. I see, so I am not a C API user, so may be I'm missing something. Cheers -- Mateusz Loskot http://mateusz.loskot.net |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | RE: Encounter Segmentation Fault with GEOS 2.2.2: 00098, Sheng Liang (SH/CBC) |
|---|---|
| Next by Date: | initGEOS/finishGEOS and multiple subsystems: 00098, Howard Butler |
| Previous by Thread: | Re: Encounter Segmentation Fault with GEOS 2.2.2i: 00098, strk |
| Next by Thread: | C API, GEOSGeom_getCoordSeq, quick question...: 00098, Stephen Lime |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |