by wkitty42 » Mon Jul 13, 2020 11:22 am
Johan G wrote in Mon Jul 13, 2020 1:33 am:In essence one expect there to be duplicates, at least outside a 600 NM radius.
exactly... i've not looked at the code but i wonder how it does this search and what data is available... i expect longitude and latitude are available for each navaid and they would be used to search for navaids within that 600nm range... hopefully by using geod math stuff to check the range from the current navaid to the one being searched as the next navaid... if a navaid by the searched name is not located within 600nm, the code should abort and not find one by that name outside that range... when importing flightplans and running across this, i would probably just skip the navaid...
one way around this is for a flightplan to list the lat,lon so there's no question about where navaids/waypoints are located... i forget which flightplan site it is but at least one does export to FG using lat,lon format for the waypoints... i don't think i ever had problems with flightplans from that site but others did give me some weird out of place navaid/waypoint by using just the name and having FG search it out for its lat,lon...
"You get more air close to the ground," said Angalo. "I read that in a book. You get lots of air low down, and not much when you go up."
"Why not?" said Gurder.
"Dunno. It's frightened of heights, I guess."