1
TopoFusion Pro / Merging into an existing network reduces data
« on: September 18, 2008, 07:35:01 AM »
Thanks for the detailed post. I'll see if I can figure out what's going on.
First thing I notice is that you said you were selecting the files you wanted and doing a network analysis. That's not the way the feature works -- it combines all files that are currently loaded and enabled.
That might be what you meant by selected. Just wanted to check.
There should be nothing wrong with re-using an existing network as input into a new network procedure. It's designed to work that way.
Otherwise, I think your understanding of things is correct. The number of points should only increase when you add new data. The only exception is with "contractions" when the algorithm deletes short, insignificant spurs. But unless you had a lot of that (very doubtful) that's not it.
I just experimented making a network that came out with ~10,000 points. I then added a 7000 point overlapping track to it and the new network came out at 16,300 points. That's about what is expected.
I can always take a look at your files if we can't figure it out just talking it out.
I don't think anything changed in the network code from v3.38 to v3.41. A lot changed around v3.35 and such. One thing that did change in 3.41 is the GPX output routine, but I'm pretty sure it only increased the file size (more fields).
First thing I notice is that you said you were selecting the files you wanted and doing a network analysis. That's not the way the feature works -- it combines all files that are currently loaded and enabled.
That might be what you meant by selected. Just wanted to check.
There should be nothing wrong with re-using an existing network as input into a new network procedure. It's designed to work that way.
Otherwise, I think your understanding of things is correct. The number of points should only increase when you add new data. The only exception is with "contractions" when the algorithm deletes short, insignificant spurs. But unless you had a lot of that (very doubtful) that's not it.
I just experimented making a network that came out with ~10,000 points. I then added a 7000 point overlapping track to it and the new network came out at 16,300 points. That's about what is expected.
I can always take a look at your files if we can't figure it out just talking it out.
I don't think anything changed in the network code from v3.38 to v3.41. A lot changed around v3.35 and such. One thing that did change in 3.41 is the GPX output routine, but I'm pretty sure it only increased the file size (more fields).