Software Glitch - FR displaying stacked/staggered aircraft. faulty location data?

[Wally3178]

Hi,

I am a dedicated user of the FR24 site and recently started to feed into the network as YHNL1. As a bonus, I also started to use the Premium option for FR24 and that is when my problems began. All of a sudden I had clumps of aircraft appearing around airports (ground traffic), multiple aircraft appearing at the same gate, at the end of runways and on taxiways. I have aircraft suddenly zipping across the airport and into surrounding suburbs, before returning at an equally incredible speed. I am running Windows 7 64bit with an NVIDIA GTX560 armed with the latest drivers, and I use a number of browsers but most commonly I use Chrome for FR24 but I have used IE11 with exactly the same result, the attached image is from Chrome.

Can anyone suggest what the problem might be and perhaps a solution?

Christmas greetings to all at FR24 and thank you for your efforts during 2013.

Cheers and beers,

Wal

[Oblivian]

For a start you are zoomed too far out to display so much ground data in that view. Compare the size of your average house density in the pic to the icon of the plane, the icons don't scale.

So unless you zoom right in they will always appear to over-lap as it can't pinpoint to the seconds/metre location on the map at that height.

The other issue may be the ground uploader is sending bad data. Dongles are known to do this if too close to the source and need error adjustments made

[fungus]

Wal,
I'd just like to know how you ended up with the code 'YHNL'? And greetings to you also.

Regards,
Gregg

[airnrail]

For a start you are zoomed too far out to display so much ground data in that view. Compare the size of your average house density in the pic to the icon of the plane, the icons don't scale.

So unless you zoom right in they will always appear to over-lap as it can't pinpoint to the seconds/metre location on the map at that height.

The other issue may be the ground uploader is sending bad data. Dongles are known to do this if too close to the source and need error adjustments made

Zoom setting may be the case sometimes but the same effect has been evident at Sydney at various times over the last few days and cannot be resolved no matter how far you zoom in - they remain stacked on top of each other. It reverts to normal after a while and then reappears. On Sat a few planes also appeared to land in Botany Bay rather than 34L and other inbounds were showing wavy flight trails similar to those often seen over North America from the FAA feed. In this instance it appears to be a system issue. As Wally3178 alludes, glitches sometimes seem to manifest themselves in Premium more so than in the free version

[Oblivian]

I didn't write it off totally as zoom

The other issue may be the ground uploader is sending bad data. Dongles are known to do this if too close to the source and need error adjustments made

[airnrail]

I didn't write it off totally as zoom

I understand that you didn't but I wonder why you would even bother with this post. Is that how you become a Super Moderator on this forum?

[Oblivian]

Why I bothered? Because your reply sure reads as if I did (blame the zoom for the entire example) and hadn't given any valid input to him.
Whereas my mention of the bad upload data from dongles did, so I re-quoted to point out I had already included a plausible answer to the second half of his query.

By quoting me and then adding your own weekend experiences only says to me "you're wrong.. cause I saw this.."

Your given examples in this case would have been better to have been added to a thread on said weekend if you have seen some examples the last few days for the dev team to take note or added here without openly quoting my post.

In this instance it appears to be a system issue.

Is that how you become a Super Moderator on this forum?

No, It sure isn't the the way. It's by being an active poster on the opposite side of the planet to the main admins, and attempting to assist people with issues in a methodical manner, eliminating apparent multiple issues/causes bit by bit rather than writing the whole system off as being at fault for the whole part like many are keen to do around the forums at present. And keeping the bots at bay.

[Oblivian]

Your given examples in this case would have been better to have been added to a thread on said weekend if you have seen some examples the last few days for the dev team to take note or added here without openly quoting my post.

Much like this..

Attn Mike/Devs/FR24Support

Further to the OPs queries I have just seen one of these phenomenon's occur myself:

Premium status: logged OUT
FF v25
0740 UTC over NZAA region

(http://oi42.tinypic.com/2zp2is3.jpg)

APRT12 (which for some reason is now marked as a fuel vehicle..) was doing its normal perimeter patrol, but then the track was straight-lined for a bit from the centre location where the other AC (JST250 and PST42) appear here, Later moving to other parts of the airport at each 8 second update

Contact was distributed between NZAA2 and NZAA8, both T feeders

[peterhr]

It does seem odd that the planes on the image are positioned as if on a grid.

What would be useful would be to click some of them and to read off what radar has uploaded the positional information from some of those 'wrong' planes. (I would do it but I don't know what airport the image is of).

I don't think it's anything wrong with your browser, much more likely to be a local example of 'garbage in (from a feeder), garbage out (from the web site)' .

...and with a site like this moderators are needed to give 24/7 coverage - it's an unpaid responsibility that keeps site like this free of porn and third party advertising - that there is so little here it shows what a good job they do.

[airnrail]

Why I bothered? Because your reply sure reads as if I did (blame the zoom for the entire example) and hadn't given any valid input to him.
Whereas my mention of the bad upload data from dongles did, so I re-quoted to point out I had already included a plausible answer to the second half of his query.

By quoting me and then adding your own weekend experiences only says to me "you're wrong.. cause I saw this.."

Your given examples in this case would have been better to have been added to a thread on said weekend if you have seen some examples the last few days for the dev team to take note or added here without openly quoting my post.




No, It sure isn't the the way. It's by being an active poster on the opposite side of the planet to the main admins, and attempting to assist people with issues in a methodical manner, eliminating apparent multiple issues/causes bit by bit rather than writing the whole system off as being at fault for the whole part like many are keen to do around the forums at present. And keeping the bots at bay.

You are wrong on all counts - the issue at Sydney affected more than a single feeder - the implication in your original post is that there was maybe a maladjusted feeder present. It is not an issue that caused me any concern or inconvenience at the time I spotted it - I expect that it will eventually right itself - and I have only commented today because someone else posted about a similar problem elsewhere. You and a few others here obviously have far too much time on your hands to be able to churn out endless verbage apparently just for the sake of writing it. It is not mine, yours or any other user's responsibility to be 24/7 troubleshooters for the operators of a commercial website that I for one pay money to use. Keep this trivial matter going if you want to but I won't engage further with you.

[Oblivian]

It does seem odd that the planes on the image are positioned as if on a grid.

Yep, my initial thought after seeing it was possibly a default 'home' or similar old data that is used when an active updated packet is missed as they kept bouncing back/forth to it

What would be useful would be to click some of them and to read off what radar has uploaded the positional information from some of those 'wrong' planes. (I would do it but I don't know what airport the image is of).

psst... I included it was NZAA and 2 radars that were displaying it in the end there

I don't think it's anything wrong with your browser, much more likely to be a local example of 'garbage in (from a feeder), garbage out (from the web site)' .

Yeah, included what I was running as secondary information since the OP mentioned he had chrome. And we all know how bad IE is in any case..

...and with a site like this moderators are needed to give 24/7 coverage - it's an unpaid responsibility that keeps site like this free of porn and third party advertising - that there is so little here it shows what a good job they do.

There's a lot less here nowadays with the added security, but like most things the odd one gets through. Usually actual paid people.. nay people with "far too much time on their hands" (that actually get paid) who sit in an office and join forums manually posting them instead of bots. Can usually spot them as it takes them 1-2mins between post times and dig up old threads with key words.

[peterhr]

I think the grid (if it's just one locality) might be rounding errors on an feeder computer - small software problem

If it's everywhere - it's FR24 (sh*t happens, though it shouldn't)

[Wally3178]

Wal,
I'd just like to know how you ended up with the code 'YHNL'? And greetings to you also.

Regards,
Gregg

Typo, it's a typo!! It should read YNHL which is my closest airport, Nhill, VIC.

I post once in a blue moon and I make a typo......sheesh!!

Wal

[Wally3178]

For a start you are zoomed too far out to display so much ground data in that view. Compare the size of your average house density in the pic to the icon of the plane, the icons don't scale.

So unless you zoom right in they will always appear to over-lap as it can't pinpoint to the seconds/metre location on the map at that height.

The other issue may be the ground uploader is sending bad data. Dongles are known to do this if too close to the source and need error adjustments made

I chose that level of zoom to display all of the occurrences (circled in red), zooming in made absolutely no difference except to show that multiple A/C were parked on the same square metre of tarmac or residential neighbourhood, whichever the case may be. However there is one thing that I did neglect to mention in my earlier post, and that is the Lat/Long indications for individual A/C. In almost every case, whenever the 'glitch' occurs, the last two digits of the coordinates have been dropped; for example 25.2448/55.3695 becomes 25.24/55.36 respectively.

Cheers,

Wal

[peterhr]

psst... I included it was NZAA and 2 radars that were displaying it in the end there

Hi Oblivian... I was referring to the original picture on post #1 on the thread - not yours

It's Dubai http://www.flightradar24.com/25.26,-304.63/14

My browser (chrome on w7 pro x64) is showing it correctly.

Though AIR15 seems to be the type of track I get from my GPS logger driving to work - following roads in from the suburbs, through junctions etc (neatly avoiding buildings)