Timeline for Calculate catchment area with pgrouting
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 28, 2020 at 16:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Nov 29, 2019 at 12:00 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Oct 30, 2019 at 6:57 | answer | added | Michal De | timeline score: 1 | |
| Oct 24, 2019 at 18:06 | comment | added | Michal De | I have this message: "Only lon/lat coordinate systems are supported in geography." When I delete ":GEOGRAPHY", result is the same. Unit of leng is meter. Coordinates are also in meters (EPSG:2180). | |
| Oct 23, 2019 at 15:15 | comment | added | geozelot |
what's the unit of leng, meter? What happens if you replace it with ST_Length(geom::GEOGRAPHY) AS cost?
|
|
| Oct 23, 2019 at 13:54 | comment | added | Michal De | I have just added two screenshots. | |
| Oct 23, 2019 at 13:52 | history | edited | Michal De | CC BY-SA 4.0 |
added 286 characters in body
|
| Oct 23, 2019 at 13:30 | comment | added | geozelot |
your first query executes pgr_drivingDistance once for every row in osm_roads_vertices_pgr; it simply fetches the full table, but instead of selecting columns that function will be executed for each row. just omit the FROM osm_roads_vertices_pgr. as to your actual issue; without knowing your network, this is impossible to debug (it might just as well be the expected result, and it just needs an explanation as to why it is)
|
|
| Oct 23, 2019 at 12:08 | history | asked | Michal De | CC BY-SA 4.0 |