Forum #18 - Topic #23 - Message List

First of all thank for your great work.

I would like to describe the situation (I'm sorry for my pure english) I have downloaded 1.0.0a win 32 version. I have used some sample data for routing CREATE TABLE "map_polish"."rtest" (

"gid" SERIAL,

"source" INTEGER NOT NULL,

"target" INTEGER NOT NULL,

"cost" DOUBLE PRECISION DEFAULT 0 NOT NULL,

"rcost" DOUBLE PRECISION DEFAULT 0 NOT NULL,

"x1" DOUBLE PRECISION DEFAULT 0 NOT NULL,

"y1" DOUBLE PRECISION NOT NULL,

"x2" DOUBLE PRECISION NOT NULL,

"y2" DOUBLE PRECISION NOT NULL,

"rule" TEXT,

"to_cost" DOUBLE PRECISION NOT NULL,

CONSTRAINT "rtest_pkey" PRIMARY KEY("gid")

) WITH OIDS;

CREATE INDEX "rtest_idx" ON "map_polish"."rtest"

USING btree ("source", "target");

INSERT INTO "map_polish"."rtest" ("gid", "source", "target", "cost", "rcost", "x1", "y1", "x2", "y2", "rule", "to_cost") VALUES

(1, 1, 2, 1, 0, 1, 1, 2, 2, NULL, 100),

(2, 3, 2, 1, 0, 3, 3, 2, 2, NULL, 100),

(3, 2, 4, 1, 0, 2, 2, 4, 4, NULL, 100),

(4, 4, 5, 1, 0, 4, 4, 5, 5, '3', 100),

(5, 3, 5, 1, 0, 3, 3, 5, 5, NULL, 100),

(36, 5, 3, 1, 0, 5, 5, 3, 3, '4', 555);

Then I run query: SELECT * FROM shortest_path_shooting_star('SELECT gid AS id,source::int4,

target::int4, cost::double precision, rcost::double precision AS reverse_cost, x1,y1,x2,y2,rule,to_cost FROM map_polish.rtest order by gid',1,5,true,false);

And sometimes I get error (Postgresql process terminates). But in most cases the result is:

vertex_id edge_id cost

0 1 1

1 3 1

4 4 1

6 36 1

2 5 1

1)Edges where found correctly

2)In my opinion vertices are not correct

3)In data there are 2 turn restriction for edges 3->4, 4->36. But in result they do not influence on resulting costs

I use it with postgresql 8.2.3 and postgis 1.2.1 Win XP.

Thanks in advance.