-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OperatorCodeFlag keeps getting overwritten with "Null" value #119
Comments
Hi |
Hi
THis is a portion of an extract from Thursday after I corrected the field
[cid:7728990a-3b63-42d9-826d-7c3251c5d538]
[cid:0dabe7aa-e71e-4192-8ea9-6069a86c0604]
I noticed it on my EUFI a/c as well today also with an NHZ helicopter. - dont have screenshots of that as i didn't take extracts. Its does it with the HAWK's of the
Here is an example of my HAWK's as they currently stand.
[cid:fdb2c017-4a27-4331-9488-5cb79d3ece68]
These 8 a/c are the Qatar Emiri Air Force HAWK's And i on a regular basis, have to kep fixing the OperatorFlagCodes of these from NULL and I have just noticed, RFR. These are always being reset to whatever the code is picked up from the website you pull your data from. I have to continually reset the codes back to to QEAF.
Now that i've noticed these again, I'll reset them back to QEAF. I chekc on these quite often as i have 1 plane missing and i'm looking for it plus also it makes a mess of my radar when it doen't show the proper colour a/c in the icons.
If you can put a check in to say "if a value already exists that is not NULL then do not overwrite" then that would be great thanks.
…________________________________
Thank You
Rory Fairbairn
________________________________
From: Richard G ***@***.***>
Sent: 19 April 2024 12:00
To: vradarserver/vrs ***@***.***>
Cc: egpd1701 ***@***.***>; Author ***@***.***>
Subject: Re: [vradarserver/vrs] OperatorCodeFlag keeps getting overwritten with "Null" value (Issue #119)
Hi
Are you able to provide some screen shots / some before and after examples would be great!
The operatorflagcode should not be getting written over with a NULL value as every aircraft should have something in the operatorflagcode in the database when updates are preformed.
Thanks
—
Reply to this email directly, view it on GitHub<#119 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACIMSZPWLX55WIB4P4WB4XDY6D2N7AVCNFSM6AAAAABGOYL5QKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRWGMZTKNZWGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi
Forgot to say, with the HAWK - it has also deleted one serial number and changed the Manufacturer field and the registered owners field as well - so its not just 1 field its changing, its multiple ones.
Really annoying 🙂
…________________________________
Thank You
Rory Fairbairn
________________________________
From: Richard G ***@***.***>
Sent: 19 April 2024 12:00
To: vradarserver/vrs ***@***.***>
Cc: egpd1701 ***@***.***>; Author ***@***.***>
Subject: Re: [vradarserver/vrs] OperatorCodeFlag keeps getting overwritten with "Null" value (Issue #119)
Hi
Are you able to provide some screen shots / some before and after examples would be great!
The operatorflagcode should not be getting written over with a NULL value as every aircraft should have something in the operatorflagcode in the database when updates are preformed.
Thanks
—
Reply to this email directly, view it on GitHub<#119 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACIMSZPWLX55WIB4P4WB4XDY6D2N7AVCNFSM6AAAAABGOYL5QKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRWGMZTKNZWGI>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
I completely miss read which repo this was in... I thought that you were posting on sdr-enthusiasts/docker-virtualradar which has a built-in nightly database update process. Thankfully this issue does not appear to be with that, which would have landed this issue on my doorstep. To that end I am going to stop worrying and give you the only suggestion I can think of... In the BaseStation Database Writer Options ensure that overwrite details on existing aircraft is not selected. Then any that you change should stay fixed and will not be overwritten by the VRS SDM aircraft data. Unfortuantely none of your pictures displayed, but I can imagine this issue is annoying. |
Hi
Thanks for the info.
Am i right in thinking that it will still write new aircraft?
…________________________________
Thank You
Rory Fairbairn
________________________________
From: Richard G ***@***.***>
Sent: 19 April 2024 13:05
To: vradarserver/vrs ***@***.***>
Cc: egpd1701 ***@***.***>; Author ***@***.***>
Subject: Re: [vradarserver/vrs] OperatorCodeFlag keeps getting overwritten with "Null" value (Issue #119)
I completely miss read which repo this was in... I thought that you were posting on sdr-enthusiasts/docker-virtualradar<https://github.com/sdr-enthusiasts/docker-virtualradarserver> which has a built-in nightly database update process. Thankfully this issue does not appear to be with that, which would have landed this issue on my doorstep. To that end I am going to stop worrying and give you the only suggestion I can think of...
In the BaseStation Database Writer Options ensure that overwrite details on existing aircraft is not selected.
Then any that you change should stay fixed and will not be overwritten by the VRS SDM aircraft data.
Unfortuantely none of your pictures displayed, but I can imagine this issue is annoying.
—
Reply to this email directly, view it on GitHub<#119 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACIMSZPXCDKO65K7QC6ENX3Y6ECB3AVCNFSM6AAAAABGOYL5QKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANRWGQZTCMRUGY>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Yes, It should still write new aircraft but you will have to keep current aircraft up to date. Please post back and let us know if this solved your issue. |
Fields with data already in the are being overwritten with NULL values, specifically the OperatorFlagCode field.
The text was updated successfully, but these errors were encountered: