On Saturday 07 July 2007 11:16, Thomas Förster wrote: > Am Samstag 07 Juli 2007 09:41 schrieb Vivian Meazza: > > OK so it's 2 features, not 1 bug - excellent. I also noted that the route > > taken from parking to active runway seemed a bit odd, but then I compared > > our taxiways to those on Google Earth - we seem to have bits missing > > alongside 28L, which explains that. Not good for our default airport > > though. > > The route finding is extremely simple. It just calculates the shortest way > between 2 points (in terms of travel distance) of the ground network. The > ground network is a directed graph though. Probably there are some > invisible "one-ways" in it.
I just checked using taxidraw. There are some taxiroutes missing, thus preventing traffic to follow the shortest route. I'm working on it. > It might be possible to make the way finding more clever (e.g. penalize > runway crossings etc.), but this would need a more sophisticated groundnet, > with more node types (i.e. holding positions) than now. Which might be a > good idea anyway. > Eventually, that would be the plan. Before we can do this, we need to have more sophistcation in the ground network, and consequently, also in it's principal design tool; taxidraw. Part of that is going to be my summer / fall project. Cheers, Durk ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
