You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Had a bug where not all node ids were being populated. The edges were correct and the few nodes I found were correct, but my assumption that (result.nodes.length === result.ids.length + 1) isn't always true.
I'm currently work-arounding it by detecting the problem and then populating the nodes array myself based on what is in the edges. My network is one directional and uses the manual (non geojson based) api.
My random guess is that the nodes are based on the contracted network while the edges is based on the real network.
I'd like to leave this bug here even thought I haven't managed to create a very small test case for this yet, so if someone else runs into the issue, they can see my workaround and perhaps add more information from their own debugging.
The text was updated successfully, but these errors were encountered:
Had a bug where not all node ids were being populated. The edges were correct and the few nodes I found were correct, but my assumption that (result.nodes.length === result.ids.length + 1) isn't always true.
I'm currently work-arounding it by detecting the problem and then populating the nodes array myself based on what is in the edges. My network is one directional and uses the manual (non geojson based) api.
My random guess is that the nodes are based on the contracted network while the edges is based on the real network.
I'd like to leave this bug here even thought I haven't managed to create a very small test case for this yet, so if someone else runs into the issue, they can see my workaround and perhaps add more information from their own debugging.
The text was updated successfully, but these errors were encountered: