shootingstar (#18) - shootingstar_sp_smart problem (#400) - Message List

Hi, I had very few time left those last days. I quickly check into the function. You can help yourself by raising notices. Like RAISE NOTICE as shown below.... The problem seems to be that when the extra edges are created, the cost or some other field are not populated properly. In order to check that, I added Notices in this part of the code :

-- Newly created edges should be appended here
        FOR i IN 1..6 LOOP
	  --curr := extra_edges[i];
	  RAISE NOTICE 'i=%', i;
	  IF extra_edges.rule[i] IS NULL THEN extra_edges.rule[i]:='NULL';
	  ELSE extra_edges.rule[i]:=''''''||extra_edges.rule[i]||'''''';
	  END IF;
	  IF extra_edges.to_cost[i] IS NULL THEN extra_edges.to_cost[i]:=0;
	  END IF;
          --FA : the raise notice example
	  RAISE NOTICE 'gid %',extra_edges.gid[i];
	  RAISE NOTICE 'source %',extra_edges.source[i];
	  RAISE NOTICE 'target %',extra_edges.target[i];
	  RAISE NOTICE 'cost %',extra_edges.length[i];
	  RAISE NOTICE 'rule %',extra_edges.rule[i];
	  RAISE NOTICE 'to cost %',extra_edges.to_cost[i];

So when you try to concatenate a value that is null to the variable query, it screws the things up and the query take a NULL value. You may want to check in this direction. Basically, what the wrapper does is finding the closest segments to your points, split them into extra_edges, and pass the pieces of information to those extra edges. Something goes wrong in this process. I checked in the query that doesn't work, the source and destination segment are found. It is when passing the information that things get messed up.

I hope it helps! Cheers

flivingstone