Joined: Fri Oct 21, 2005 2:50 am
Posts: 28
Location: Minneapolis, MN, US area
|
|
In the file fsbuild2.cfg [FSBUILD] section I use:
NAVCHKDUPDIST=100
I keep it tight because of local jurisdiction waypoints that may not be unique within larger areas. Often local airport terminal areas use 'soft' waypoints that may have duplicate labels in airports not very far away. They often have the form 'D10' or similar and are based on DME waypoints used frequently in RNAV departures and approaches for SID/STARS and IAPs. Subscribed coded databases purchased for some navigation instruments and planners often use these for boundaries (turn left at . . .) or as a single point to define a non-ICAO defined intersection for use within local procedures.
You'll often find these in the AIRAC FMC updates sold by Navigraph.
Another label sometimes duplicated over long distances is of the NDB navaid which are of short range.
By keeping the search range limited it can reduce the duplicate waypoint problem.
There is a non-sticky option (between sessions) that must be set each time called Build From Route Grid. I proof my auto-gen routes on the map and if I find anything suspicious I'll highlight the waypoint in question on the grid. If I manually edit the grid then I'll choose this option so the route includes my change instead if ignoring it and just rebuilding from the route described in the route box which would create the same route table.
_________________
Ron Ginsberg
Minnesota - Land of 10,000 Puddles
|
|
Login
Register
FAQ
Search
