1

In pgr_drivingDistance for isochrones the person who answered, missed to say the explanation of the answer about what function used by him to get the output for isochrone. I want to do the same but I got the same result like network table and no difference. with this image, I have attached the code with this. enter image description here

create table htokdisdri as 
    SELECT t1.seq, 
           t1.id1 AS Node, 
           t1.id2 AS Edge, 
           t1.cost, 
           t2.geom AS edge_geom 
    FROM  PGR_DrivingDistance(
           'SELECT id, source, target, traveltime as cost FROM muensterstreets_t',
          (SELECT id 
           FROM muensterlocation 
           WHERE "Name" = 'HILTRUP'),   
          05, false) t1 
    Left join   muensterstreets_t t2 on t1.id2 = t2.id 
    order by t1.seq;
  • 1
    you could create convex hull/alpha shape based polygons around result nodes with e.g. different maximum aggregate costs, see e.g. pgRoutings pgr_pointsAsPolygons function – ThingumaBob Jun 8 at 8:30
1

I got the answer by removing the order by keyword and included false in pgr algorithm as there is no specific target.

create table htokdisdri3 as SELECT t1.seq, t1.id1 AS Node, t1.id2 AS Edge, t1.cost, t2.geom AS edge_geom
FROM 
PGR_DrivingDistance(
  'SELECT id, source, target, length as cost FROM muensterstreets_t',
        (SELECT id FROM muensterlocation as xs WHERE "Name" = 'HILTRUP'),                                                                                   
        1000,
    false, false) t1
Left join 
    muensterstreets_t t2
on t1.id2 = t2.id;

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.