Same coord points will always intersect #6

New Issue

markus · 2021-03-17T07:36:14+01:00

markus commented

2021-03-17 07:36:14 +01:00

We do need a layer property on nodes after all. If we create trainline A on layer A, and trainline B an layer B, but they have a common point, both lines will intersect and allow an interchange here.

Alternatively, I could probably implement some logic preventing us to move from TL A to TL B in the dijkstra... but that seems dirty.

We do need a layer property on nodes after all. If we create trainline A on layer A, and trainline B an layer B, but they have a common point, both lines will intersect and allow an interchange here. Alternatively, I could probably implement some logic preventing us to move from TL A to TL B in the dijkstra... but that seems dirty.

markus commented

2021-06-20 11:46:13 +02:00

Another quick (and not quite as dirty hack) would be to add a no_exist_check argument to dijkstra_node_new via dijkstra_path_new_to_list and dijkstra_node_new_to_list that is se for train layers, which will then always append the new entry. This would allow for two distinct points on the same coord. Might cause headaches down the road though...

Another quick (and not quite as dirty hack) would be to add a `no_exist_check` argument to `dijkstra_node_new` via `dijkstra_path_new_to_list` and `dijkstra_node_new_to_list` that is se for train layers, which will then always append the new entry. This would allow for two distinct points on the same coord. Might cause headaches down the road though...

markus commented

2021-06-20 11:53:36 +02:00

Or, even cheaper, never merge if new AND old are of time train. That's even better I think. And faster.

EDIT: Actually, no. We don't have this info where we need it (as we don't have point layers, only path layers.)

Or, even cheaper, never merge if new AND old are of time train. That's even better I think. And faster. EDIT: Actually, no. We don't have this info where we need it (as we don't have point layers, only path layers.)

markus referenced this issue from a commit

2021-06-20 14:49:12 +02:00

Implement net_meta info for nodes...

markus closed this issue

2021-06-20 14:49:12 +02:00

Sign in to join this conversation.