Improved Routing Information

[DaveReid]

I would have thought that the routes information is held locally on each users individual computer, same as aircraft data.  If you already have information on your computer regarding call sign that will not be over written, same as aircraft data.  Unless you delete the existing info on your computer, nothing will change.

It will only be new route data which will be added not existing data over written.

Yes, you are correct in that route data is cached locally (in MyFlights.db3), but that's not the issue here.

The question, as yet unanswered, it whether a user picking up, say, RYR96V for the first time will get the (incorrect) Rome-East Midlands route downloaded from the server, or will routes that are already in the server database be validated so that changes can be picked up and propagated to users.

AirNav ?

[bratters]

I don't think we're going to make any further headway here until we get a more comprehensive and detailed explanation of the system from from "Dev".

I would request Airnav that when the detail is published it is couched in terms with which we are all familiar;  introducing phrases like "client table" just further complicates an already confusing issue.

We await developments with interest.

[anorak]

That would be the "KISS" principle then?   :-)

[bratters]

That would be the "KISS" principle then?   :-)

Same principle and on the same lines as COIK  - Clear Only If Known - a caution against the use of technical words and jargon when addressing people outside your own field. Sounds obvious but happens all the time.

[Really]

RYR23UZ showing route EGBE - EGBB

Clearly wrong, the two airports are very close to each other, possible bug with this new system?

[DaveReid]

RYR23UZ showing route EGBE - EGBB

Clearly wrong, the two airports are very close to each other, possible bug with this new system?

I recall in the early days when I was fine-tuning my Heathrow arrivals/departures algorithm that it would occasionally mis-identify flights to/from London City (same runway orientation), so I can sympathise with AirNav's programmers - it's not a trivial exercise by any means.

Having said that, it's common knowledge that EGBE (Coventry) doesn't have any scheduled flights, so I'm rather surprised that the server process attempts to identify departures from there at all.

According to my database RYR23UZ (RYR1085) is EPRZ-EGBB, by the way.

  <?xml version="1.0" encoding="utf-8" ?>
- <Flight>
  <FlightNumber>RYR23UZ</FlightNumber>
  <Callsign>Ryanair 23UZ</Callsign>
- <Leg>
- <Origin>
  <ICAOCode>EPRZ</ICAOCode>
  <IATACode>RZE</IATACode>
  <AirportName>RZESZOW</AirportName>
  <Country>POLAND</Country>
  </Origin>
- <Destination>
  <ICAOCode>EGBB</ICAOCode>
  <IATACode>BHX</IATACode>
  <AirportName>BIRMINGHAM/ELMDON</AirportName>
  <Country>UNITED KINGDOM</Country>
  </Destination>
  <GCDistanceNM>899</GCDistanceNM>
  <DistanceFromOriginNM>845</DistanceFromOriginNM>
  <DistanceFromDestinationNM>56</DistanceFromDestinationNM>
  </Leg>
  </Flight>

[54901 - Jim]

Routes Error

See attached file.

This Washington to Oregon flight is over Wisconsin as I write this ... definitely taking the LONG way to get there.

Thanks for checking it!

Jim

[DaveReid]

This Washington to Oregon flight is over Wisconsin as I write this ... definitely taking the LONG way to get there.

There shouldn't be any need for complicated algorithms to work out the routings for AWE flights - the entire Star Alliance schedule is freely downloadable from the Net.

  <?xml version="1.0" encoding="utf-8" ?>
- <Flight>
  <FlightNumber>AWE925</FlightNumber>
  <Callsign>Cactus 925</Callsign>
- <Leg>
- <Origin>
  <ICAOCode>KPHL</ICAOCode>
  <IATACode>PHL</IATACode>
  <AirportName>PHILADELPHIA (INTERNATIONAL)</AirportName>
  <Country>UNITED STATES</Country>
  </Origin>
- <Destination>
  <ICAOCode>KPDX</ICAOCode>
  <IATACode>PDX</IATACode>
  <AirportName>PORTLAND (INTERNATIONAL)</AirportName>
  <Country>UNITED STATES</Country>
  </Destination>
  <GCDistanceNM>2084</GCDistanceNM>
  <DistanceFromOriginNM>664</DistanceFromOriginNM>
  <DistanceFromDestinationNM>1422</DistanceFromDestinationNM>
  </Leg>
  </Flight>

[bratters]

How do the two differing systems interact with each other? Does the latest idea over-ride Flightstats or is it the other way round? Which is preferential?

Some interesting questions to be answered.

[AirNav Development]

Dave: do you have that Star Alliance schedule listing and can you send it to us?

[DaveReid]

Some interesting questions to be answered.

Form an orderly queue, please !   :-)

Actually, I've answered one of my own questions in the meantime.

Perhaps [AirNav Development] could confirm that existing routes in the database (which could be wrong, as in this case) are being validated as well as new ones ?

Routes that are already in the database don't seem to be being checked by the new algorithm.  For example the following flights have all landed at or taken off from Heathrow today, and clearly there must be sufficient network coverage of LHR for the algorithm to identify them as such (AirNav routes in brackets):

CPA037 (VIDP-EGCC-LIMC)
CPA038 (EGCC-LIMC-VHHH)
DLH1FW (EDDF-EGBB)
DLH1VV (EDDF-EGCC)
DLH7PH (EIDW-EDDF)
QFA30 (VHHH-YMML)
UAL931 (KSFO-KLAX)
UAL948 (KLAX-KDEN)

IMHO, detecting that a a route arrives or departs from an airport which isn't consistent with the route currently in the database ought to be sufficient to invalidate that route record until it has been investigated.

[DaveReid]

Dave: do you have that Star Alliance schedule listing and can you send it to us?

www.staralliance.com/assets/doc/en/services/tools-and-downloads/pdf/StarAlliance.pdf

[AirNav Development]

We need the list in xml format, not in pdf.

[tarbat]

We need the list in xml format, not in pdf.

What XML tags?

[AirNav Development]

These:

  <?xml version="1.0" encoding="utf-8" ?>
- <Flight>
  <FlightNumber>AWE925</FlightNumber>
  <Callsign>Cactus 925</Callsign>
- <Leg>
- <Origin>
  <ICAOCode>KPHL</ICAOCode>
  <IATACode>PHL</IATACode>
  <AirportName>PHILADELPHIA (INTERNATIONAL)</AirportName>
  <Country>UNITED STATES</Country>
  </Origin>
- <Destination>
  <ICAOCode>KPDX</ICAOCode>
  <IATACode>PDX</IATACode>
  <AirportName>PORTLAND (INTERNATIONAL)</AirportName>
  <Country>UNITED STATES</Country>
  </Destination>
  <GCDistanceNM>2084</GCDistanceNM>
  <DistanceFromOriginNM>664</DistanceFromOriginNM>
  <DistanceFromDestinationNM>1422</DistanceFromDestinationNM>
  </Leg>
  </Flight>