16-06-2006, 11:16 AM
I think an other spokesman is needed here. Then, I come in 
If I understand well the problem is that although a plane is parked on the right airport. it can be nearer to a small airport in the
neighbourhood. The drawing posted by Spokesman Drew tells it better than any words: easy to be parked at PANC but closer to LHD
center than PANC center.
Changing the airport database or checking at touch down would just move the problem but not remove it (nice isn't it
)
The first condition to get the right answer is to ask the right question:
So, obviously, to check if the plane is at the right airport, the question is not "Which is the closest airport?" but "How far is the plane from
the scheduled airport ?"
Then, a test like
IF (PlaneToPANCCoord <= MaxAcceptabeDistance) THEN YouDidIt := TRUE;
should do the job.
How to fix this "Max acceptable distance" ?
Perhaps the answer is also on Drew's figure. In FSNAV airports are always in one ore several brown circles. If the data is picked by
FSNAV from FS2004 airport database, then it should be possible to
Get the circle center(s) and ray(s) of the scheduled airport and check if the plane is at less than the ray length to the related center.
If this distance is unavailable, perhaps a (user editable) value of about a long runway, let's tell 12000 feets would fit ?
@ Fabrizio
Softwares are currently designed, written ant tested by humans. As consequence, all of them can indeed be improved. NB, the same
remark is true about our way to use the softawares as they currently are
You are 100% right to ask for improvements on FSP but...
You are 200% wrong in the way and tone to ask it. What hell is the point undermining the individual qualities of the team who worked on
the current FsP just because by time we get some unfair penalties? An undeserved -300 can't be an excuse for insults or even a "DO IT
RIGHT NOW" harsh obligation.
This is not only because problems are usually better solved by friendly cooperation between users and designers. But simply, if
something cannot be delivered as long as it is not perfect... just imagine:
You pay an architect and builders for a house. As they are honest and serious upon your criteria, as soon as they see something which
could be better , they re-build... You woulsd simply never get your house. Human life would be building houses at day and sleeping
outdoor at night
Useless to tell that we would have to forget about flight simming etc.
Is it such a world you are dreaming about Fabrizio ?
Dan
BUY it now ??? WHAT ???
You MUST provide us a free trial vesion to check if they are OK, then engage yourself to provide 2 free
upgrade by week (this will save us a boring washing job.
"Faut quand-même pas deconner !!!
"

If I understand well the problem is that although a plane is parked on the right airport. it can be nearer to a small airport in the
neighbourhood. The drawing posted by Spokesman Drew tells it better than any words: easy to be parked at PANC but closer to LHD
center than PANC center.
Changing the airport database or checking at touch down would just move the problem but not remove it (nice isn't it

The first condition to get the right answer is to ask the right question:
So, obviously, to check if the plane is at the right airport, the question is not "Which is the closest airport?" but "How far is the plane from
the scheduled airport ?"
Then, a test like
IF (PlaneToPANCCoord <= MaxAcceptabeDistance) THEN YouDidIt := TRUE;
should do the job.
How to fix this "Max acceptable distance" ?
Perhaps the answer is also on Drew's figure. In FSNAV airports are always in one ore several brown circles. If the data is picked by
FSNAV from FS2004 airport database, then it should be possible to
Get the circle center(s) and ray(s) of the scheduled airport and check if the plane is at less than the ray length to the related center.
If this distance is unavailable, perhaps a (user editable) value of about a long runway, let's tell 12000 feets would fit ?
@ Fabrizio
Softwares are currently designed, written ant tested by humans. As consequence, all of them can indeed be improved. NB, the same
remark is true about our way to use the softawares as they currently are

You are 100% right to ask for improvements on FSP but...
You are 200% wrong in the way and tone to ask it. What hell is the point undermining the individual qualities of the team who worked on
the current FsP just because by time we get some unfair penalties? An undeserved -300 can't be an excuse for insults or even a "DO IT
RIGHT NOW" harsh obligation.
This is not only because problems are usually better solved by friendly cooperation between users and designers. But simply, if
something cannot be delivered as long as it is not perfect... just imagine:
You pay an architect and builders for a house. As they are honest and serious upon your criteria, as soon as they see something which
could be better , they re-build... You woulsd simply never get your house. Human life would be building houses at day and sleeping
outdoor at night

Is it such a world you are dreaming about Fabrizio ?

Dan
Quote:" New: spokesman t-shirt available in store - DON'T miss it, Buy yours now!!! "
BUY it now ??? WHAT ???

upgrade by week (this will save us a boring washing job.
"Faut quand-même pas deconner !!!

![[Image: banniere064.png]](http://www.britair-virtual.com/bannieres/banniere064.png)