Show Posts
1
TopoFusion Pro / network tool on very dense trail networks
« on: May 09, 2010, 07:26:16 PM »
I'm accumulating tracks for a trail network in town and I'm running into some troubles. I'm trying to use the network function to merge everything together.
This trail system has probably 5-8 miles (I haven't ridden the advanced stuff with the stunts yet) of trail on 64 acres, for reference. This trail doubles on itself a lot. The network function is having a lot of troubles determining intersections and deciding what to reduce. In some areas, it's telling me there's an intersection where none exists...just that two trails pass so close together, there might be a little overlap from one ride to another. Another place I'm having trouble is that there's a couple loops on the trail that TF is reducing entirely. On one, the loop is reducing to a dead end, and on another, the loop (which serves as something of a central ending of all the trails at the bottom of the hill) is getting reduced to nothing more than a single point.
I've dropped the tolerances as low as possible on the algorithm. If I make them any lower, it won't even reduce two tracks on the same trail from two different rides with different reception.
Any suggestions about how to deal with such a dense network of trails?
I used to do this sort of thing by hand, and if the network algorithm can't handle such a high density, them I'm going to have to continue doing it by hand.
This trail system has probably 5-8 miles (I haven't ridden the advanced stuff with the stunts yet) of trail on 64 acres, for reference. This trail doubles on itself a lot. The network function is having a lot of troubles determining intersections and deciding what to reduce. In some areas, it's telling me there's an intersection where none exists...just that two trails pass so close together, there might be a little overlap from one ride to another. Another place I'm having trouble is that there's a couple loops on the trail that TF is reducing entirely. On one, the loop is reducing to a dead end, and on another, the loop (which serves as something of a central ending of all the trails at the bottom of the hill) is getting reduced to nothing more than a single point.
I've dropped the tolerances as low as possible on the algorithm. If I make them any lower, it won't even reduce two tracks on the same trail from two different rides with different reception.
Any suggestions about how to deal with such a dense network of trails?
I used to do this sort of thing by hand, and if the network algorithm can't handle such a high density, them I'm going to have to continue doing it by hand.