The is problem, is with the table "Bodenbedeckung__BBNachfuehrung" which
has big polygon inside.
Without using custom functions the system does not crashes.
The custom functions wraps the postgis functions.
Exception is the st_curvetoline and st_linetocurve functions that
during migration of postgis 1.5 to 2.0 were changed.
Personal opinion: the new behavior is useless.
We have modified the 2.0 source to include the old st_cur* st_line*
behavior, that seems on 64 bit inside 2.0 source are not working.
Thanks for taking time for looking,
Mario Jurcevic
On 07/05/2013 10:08 AM, Sandro Santilli wrote:
On Thu, Jul 04, 2013 at 09:27:11PM +0200, Mario Jurcevic wrote:
Sorry this one is the right:
http://ubuntuone.com/202BqXg3Lvtt9zGuu3sDcx
The SQL file contains calls to custom functions that
are not available here. I handled to get the import
started by creating an "import_cadastre" schema, but
after 2.5k lines of sql the process ends with:
psql:interlis_import_51d5cb94e16e41.40947245.sql:2661: ERROR: function
geo_curvedtolinear(geometry) does not exist
LINE 1: ...o_LinearToCurved(ST_Multi(ST_BuildArea(ST_Collect(Geo_Curved...
Can you get the segfault crash without using custom
functions ?
--strk;
--
Cordiali Saluti,
MSc. Ing. Mario Jurcevic
Master in Computer Science
--------------------------------------------
GEOSAR SA
Via Essagra 12
CH-6592 S.Antonino
Tel: +41 (0)91 220 49 94
E-mail: [email protected]
www.geosar.ch
www.soft-gis.com
_______________________________________________
postgis-users mailing list
[email protected]
http://lists.osgeo.org/cgi-bin/mailman/listinfo/postgis-users
