Timeline for Getting node information of a way in OSM2PGSQL data
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27, 2016 at 21:05 | vote | accept | Andrew Wong | ||
| Apr 27, 2016 at 21:05 | comment | added | Andrew Wong | I'll have the first method implemented now, and it works like a charm. I'll definitely keep in mind that I should switch it to the second once I have some time. | |
| Apr 27, 2016 at 21:05 | comment | added | Andrew Wong | Definitly so. Thank you for clearly indicating both options. | |
| Apr 27, 2016 at 16:59 | history | edited | nebulon42 | CC BY-SA 3.0 |
added sentence stating that parsing members has to be done programmatically
|
| Apr 27, 2016 at 16:59 | comment | added | nebulon42 | Ok, so no rendering as such. I think both ways might work for you, the first one is the quick hacky way and the second one is the "right" but more effortful way. | |
| Apr 27, 2016 at 16:01 | comment | added | Andrew Wong | Apologies. I am looking into differentiating car trip and train trips. One feature I am hoping to use is how close the trip stops are to the train stops. | |
| Apr 26, 2016 at 20:57 | history | answered | nebulon42 | CC BY-SA 3.0 |