Geographic Information Systems Stack Exchange is a question and answer site for cartographers, geographers and GIS professionals. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I used gtfs2pgrouting to import gtfs data in postgresql, then I have these tables

List of relations
 Schema |    Name     | Type  |  Owner   
 gtfs   | agency      | table | postgres
 gtfs   | calendar    | table | postgres
 gtfs   | frequencies | table | postgres
 gtfs   | routes      | table | postgres
 gtfs   | shapes      | table | postgres
 gtfs   | stop_times  | table | postgres
 gtfs   | stops       | table | postgres
 gtfs   | trips       | table | postgres
(8 rows)

(several tables as "shapes" are empty)

But is it possible to use pgr_drivingDistance on this or is it another way to do it? My goal is to create isochrones


share|improve this question
no idea what gtfs is but pgRouting uses dijksra so if you network topology (routes table) you should be able to use assign_vertex_id(...) to create node/edge colums/tables for pgr_drivingDistance. – simplexio Aug 16 '13 at 19:28
the problem is that there is no table for edges, only nodes. Routes is another thing link – Frederic Le Feurmou Aug 17 '13 at 9:36
I'm working on the same problem. One thing you can do is download osm data and create a topology. Then use POSTGIS <-> operator to find the nearest node and work from there. – Ravi Mehta Oct 23 '15 at 9:18

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.