Overriding multiple routes in database

In the database the callsign UAL331 is showing KSEA KDEN KEWR.
The new routing for UAL331 is now KEWR KIAH.
When i enter the new routing KEWR KIAH it keeps returning the old routing KSEA KDEN KEWR when i submit the changes.
I have had this same problem trying to update other old multiple routes.
Is their a way to update old multiply routes of 3 or more destination?

Hi,
there are several validation steps to avoid outliers being inserted. In case of UAL331 it took far too long as KEWR-KIAH is valid from the begin of this month (it was half-automatically inserted yesterday).

In case of UAL2429 I don't see where KEWR-KDEN-KLAS, KEWR-KDEN-KDEN or KLAS-KEWR-KDEN should come from. I compared different data sources showing KEWR-KDEN only. You don't need to enter it 9 times. Try to enter correct routes only.
But feel free to point out if some routes are outdated and cannot be changed. All these automatic procedures are still under development.

Your contributions are most valuable in regions where OpenSky Network does not over the complete path between origin and destination airport.

The callsign UAL331 just seen on radar depart KEWR.
Still not able to change from incorrect route KDEN KEWR to correct route KEWR KIAH.

I may have found the reason. There was some outdated data in the system which was overriding the correct data.

No worries thank you jluebbe,
Any news regarding when routes with callsigns beginning with Zero will be able to be added to database?

Now it is allowed to have several zeros after the first 3 letters as long as the total length of the callsign does not exceed 7 characters.

Thank you jluebbe for making the necessary adjustments to the system so routes with callsigns starting with zeros can be added to the database.

Hi jluebbe,
Just to let you know i have just updated the route for callsign CES587 to ZSPD KJFK from ZSFZ ZSPD KJFK.
Still showing ZSFZ ZSPD KJFK. in database and ZSFZ KJFK on aircraft label.

That had a simple reason. Flight routes can be updated by users only if they are missing or containing errors. Errors are counted if the detected aircraft position deviates too much from the great circle path between the airports.
In this case, the correct route was still part of the route in the database and did not catch any errors. Maybe a timeout could be another criterion to allow updates.

Thank you luebbe for the feedback, i should have wrote ZSFZ ZSPD the aircraft label was showing for the CES587 when it was in New York radar area.
The callsign staring with zero is working as i manage to get the callsign CPA098 VHHH PANC KJFK to register.
Your help is greatly appreciated jluebbe.
aircraftenthusiast2000

Hi jluebbe,
I have just submitted an updated route for the FDX5047 to LFPG KEWR.
Its still showing on aircraft label VHHH LFPG and VHHH LFPG KMEM in database.

That seems to be an interesting case. But it's not easy to find a solution which is always correct. On some days it operates as VHHH-LFPG-KEWR-KMEM while the VHHH-LFPG leg is sometimes missing.

Currently, the test procedures only check if the aircraft position fits to the route in the database. I may revise the check algorithm a bit to become more reliable. And maybe introduce some check if all legs of the route have recently been covered. But that are dreams of the future.

jluebbe wrote:

Hi,
there are several validation s teps to avoid outliers being inserted. In case of UAL33 it took far too long as KEWR-]KIAH is valid from the begin of this month (it was half-automatically inserted yesterday).

In case of UAL2429 I don't see where KEWR-KDEN-KLAS, KEWRKDEN-KDEN or KLAS-KEWR - KDEN should come from[ I compared different data sources showing KEWR - KDEN only. You don't need to enter it 9 times. Try to enter correct routes only.
But feel free to point out if some routes are outdated and cannot be changed. All these automatic procedures are still under development.

Your contributions are most valuable in regions where OpenSky Network does not over the complete path between origin and destination airport.

Thank you luebbe for the feedback
i should have wrote ZSFZ ZSPD the aircraft label
was showing for the CES587 when it was in New York radar area.

Regarding the CES587, it is now showing the correct route ZSPD KJFK in both database and aircraft label.