[pgrouting-users] pgr_drivingdistance problem

[James_Keener]

When I run pgr_drivingdistance on an small extract (578 rows) (attached) from an extract of Pennsylvania’s osm pbf file not all edges are being followed. I first downloaded the pbf. Then I imported it with osm2pgrouting`

osmosis --read-pbf file=pennsylvania-latest.osm.pbf --write-xml pennsylvania-latest.osm
osm2pgrouting -file pennsylvania-latest.osm -conf /usr/share/osm2pgrouting/mapconfig.xml -dbname osm3 -user jim -skipnodes -passwd hunter2

and then running

CREATE TABLE smallways AS
  SELECT * FROM ways 
  WHERE ST_DISTANCE(the_geom, ST_GEOMFROMTEXT('POINT(-79.900121 40.448889)', 4326)) < 0.2;

and creating the appropriate indices to build a test environment (the output of which is the small extract (578 rows)(attached)). To test pgr_drivingdistance, I did the following:

CREATE OR REPLACE VIEW testing AS 
  SELECT gid,
    the_geom
  FROM ( SELECT
          seq,
          id1 AS vertext_id,
          id2 AS gid,
          cost
         FROM pgr_drivingdistance(
          'SELECT gid AS id, source, target, 
                  length AS cost, reverse_cost 
           FROM smallways', 
          179103,
          0.5,
          false, 
          true) ) t
  INNER JOIN smallways USING (gid);

and then loading that view into QGIS, I see the following: <img src="upload://urO8cYNWhbgfKr9M6ye4IpiPcuh.jpeg" style="width:800; clear: both"> Why are some edges not being selected? I initially thought it was the (source, target)` (labels in screenshot) ordering, but that doesn’t seem to be the case, as some edges such as 148517 to the SW of the annotated starting point, seems to be in good order. ``

Jim

smallways.sql.bz2 (39.1 KB)

[Vicky_Vergara1]

Hello Jim

I executed your query, I am not getting the same results as you are.
Right now we are in the process of releasing pgRouting 2.1
I used the pgr_DrivingDistance developed for the 2.1 version.
The github branch develop has the latest but its changing a lot during this days.

Vicky

---

Date: Fri, 28 Aug 2015 20:45:45 -0400
From: jim@jimkeener.com
To: pgrouting-users@lists.osgeo.org; postgis-users@lists.osgeo.org
Subject: [pgrouting-users] pgr_drivingdistance problem

When I run pgr_drivingdistance on an small extract (578 rows) (attached) from an extract of Pennsylvania’s osm pbf file not all edges are being followed. I first downloaded the pbf. Then I imported it with osm2pgrouting`

osmosis --read-pbf file=pennsylvania-latest.osm.pbf --write-xml pennsylvania-latest.osm
osm2pgrouting -file pennsylvania-latest.osm -conf /usr/share/osm2pgrouting/mapconfig.xml -dbname osm3 -user jim -skipnodes -passwd hunter2

and then running

CREATE TABLE smallways AS
  SELECT * FROM ways 
  WHERE ST_DISTANCE(the_geom, ST_GEOMFROMTEXT('POINT(-79.900121 40.448889)', 4326)) < 0.2;

and creating the appropriate indices to build a test environment (the output of which is the small extract (578 rows)(attached)). To test pgr_drivingdistance, I did the following:

CREATE OR REPLACE VIEW testing AS 
  SELECT gid,
    the_geom
  FROM ( SELECT
          seq,
          id1 AS vertext_id,
          id2 AS gid,
          cost
         FROM pgr_drivingdistance(
          'SELECT gid AS id, source, target, 
                  length AS cost, reverse_cost 
           FROM smallways', 
          179103,
          0.5,
          false, 
          true) ) t
  INNER JOIN smallways USING (gid);

and then loading that view into QGIS, I see the following: <img src="upload://urO8cYNWhbgfKr9M6ye4IpiPcuh.jpeg" style="width:800;clear:both;"> Why are some edges not being selected? I initially thought it was the (source, target)` (labels in screenshot) ordering, but that doesn’t seem to be the case, as some edges such as 148517 to the SW of the annotated starting point, seems to be in good order. ``

Jim

_______________________________________________ Pgrouting-users mailing list Pgrouting-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/pgrouting-users