[pgrouting-users] Problems recalculating the network topology

[Peter Hopfgartner]

On Thu, 2010-07-08 at 11:49 -0400, Stephen Woodbridge wrote:
> Peter Hopfgartner wrote:
> > Dear pgRouting tribe!
> > 
> > I would like to run assign_vertex_id() for a simple table, like the
> > following:
> > 
> > CREATE TABLE dhl_ret_l
> > (
> >   gid integer NOT NULL,
> >   the_geom geometry,
> >   source integer,
> >   target integer,
> >   length double precision,
> >   "cluster" integer,
> >   CONSTRAINT dhl_ret_l_pkey PRIMARY KEY (gid),
> >   CONSTRAINT enforce_dims_the_geom CHECK (st_ndims(the_geom) = 2),
> >   CONSTRAINT enforce_geotype_the_geom CHECK (geometrytype(the_geom) =
> > 'LINESTRING'::text OR the_geom IS NULL),
> >   CONSTRAINT enforce_srid_the_geom CHECK (st_srid(the_geom) = 3003)
> > )
> > 
> > This is fine for the first time. Now I would like to recalculate the
> > network topology, so I do:
> > 
> > SELECT DropGeometryColumn('public', 'vertices_tmp', 'the_geom');
> > DROP TABLE vertices_tmp;
> 
> Try doing:
> 
> DROP TABLE vertices_tmp CASCADE;
> 
> -Steve
> 

(...)

This does not change anything. Could it be that this is related to the
oldish 8.2 PostgreSQL?

Thanks,

Peter

-- 
Dott. Peter Hopfgartner

R3 GIS Srl - GmbH
Via Johann Kravogl-Str. 2
I-39012 Meran/Merano (BZ)
Email: peter.hopfgartner at r3-gis.com
Tel. : +39 0473 494949
Fax  : +39 0473 069902
www  : http://www.r3-gis.com

XING : http://www.xing.com/go/invita/8917535