Timeline for OSM2PO Postgres to graph for A*
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 14, 2018 at 19:53 | 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. | |
| Feb 12, 2018 at 11:15 | 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. | |
| Jan 12, 2018 at 12:43 | 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. | |
| Dec 13, 2017 at 11:57 | 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. | |
| Feb 16, 2016 at 18:37 | answer | added | Carsten | timeline score: 1 | |
| S Feb 12, 2016 at 18:47 | history | suggested | whyzar | CC BY-SA 3.0 |
improved formattiong and sentence structure
|
| Feb 12, 2016 at 18:17 | review | Suggested edits | |||
| S Feb 12, 2016 at 18:47 | |||||
| Feb 12, 2016 at 15:33 | comment | added | user3199699 | The issue here is that the data created by OSM2PO for the postgresql database refers to "target" and "source" id's. I assumed these id's would detail the next/previous node it was connected to but I believe this actually refers to the beginning or end node in a collection of 'ways'. When building a graph to apply route finding algorithms like A* Djikstras you need to use the geometry information provided by each node to create an edge between the two points described ((x1,y1),(x2,y2)). | |
| Feb 12, 2016 at 15:26 | comment | added | user3199699 | For anybody struggling with the same problem. | |
| Feb 12, 2016 at 14:29 | review | First posts | |||
| Feb 12, 2016 at 14:30 | |||||
| Feb 12, 2016 at 14:25 | history | asked | user3199699 | CC BY-SA 3.0 |