Timeline for Creating Isochrones - pgr_drivingDistance 2.6 SQL error
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 9, 2019 at 15:13 | comment | added | obchardon | Nothing to do with your question, but you could be interested by the project OpenTripPlanner (open source) that can create some isochrone based on OSM data and GTFS data (if you also want to compute public transport isochrone). | |
| Jul 8, 2019 at 16:31 | answer | added | AK9 | timeline score: 3 | |
| Jul 8, 2019 at 16:02 | comment | added | AK9 | @IanTurton yes both return a sensible number of results but I dont know how to relate any of the results from the pgr_drivingDistance (seq,node,edge,cost,aggcost) back to the original ways table. nothing seems to make sense. | |
| Jul 8, 2019 at 15:48 | comment | added | geozelot |
pgr_drivinDistance primarily returns all nodes that can be reached within the cost threshold; you want to join the route results of your example with the vertice table using route.node. to get isochrones, try pgr_pointsAsPolygon. this might help.
|
|
| Jul 8, 2019 at 15:44 | comment | added | Ian Turton | do the sub queries (SELECT gid as id , source , target , length_m as cost FROM "ways") and SELECT * FROM pgr_drivingDistance( 'SELECT gid as id , source , target , length_m as cost FROM "ways" ' ,274738,500,FALSE) ) as route return sensible results? | |
| Jul 8, 2019 at 15:38 | history | asked | AK9 | CC BY-SA 4.0 |