Erratic data, aircraft moving back and forth

Hi,

Since a few weeks I am trying to use this data in a 3D projection, just for fun. It worked amazingly well and is very rich compared to my previous feeds. But since like a week or so the data returned has become pretty erratic. If I poll the live feed about every 10 seconds, about every other location I get is completely wrong. For instance, an aircraft on finals is moving in, then moves a bit back, then forward again, back again - it looks like a Echternach procession . But this happens only since about a week. Did something change on the backend?

I poll in an area some kms around Schiphol Amsterdam airport (AMS). I also see a lot of aircraft appear in the list, disappear again, re-appearing 20 seconds later... this was not the case until a week or so ago

 

Upgraded to VRS 2.4.2 running on Linux last night. Woke up to a dump truck load of complaints. We have no choice, Google Maps bill was $4040.

 

I am not sure if we understand each other. I am querying AircraftList.json. Google Maps does not come into play with that. But is my observation with regards to the data quality since about a week correct? Because it seems VirtualRadar/desktop.html is still pretty stable - that is, the aircraft seem to move in more or less understandable courses

 

And why are you repeatedly querying the API json?

Would make more sense to digest the TCP feed on your own and not smash ADSBx servers.

 

Because it says 'public api' and I assumed I could, making a donation if I started to use this for real. This is not what I am supposed to do? I must admit I stopped at finding a public API. I am just going for LIVE data, FYI

 

Do you have a feeder setup? Are you not using it for real? Maybe that is the problem - maybe the planes are imaginary.

Without detail of what you are doing I cannot help you. If it is a top secret thing then email me, james at adsbexchange.com.

Every request gets a cookie to 'stick' to one of the 30 Global API servers for up to 8 hours with an idle timeout of 30 minutes. This is done by IP.

All 30 Global maybe not be in exact sync because a few people think it's a good idea to send 50 requests a second to power their own apps. VRS is a dumpster fire when serving concurrent connections. Bitcoin mining would be more efficient.

There are currently 1,200+ requests a second hitting the public api endpoint.

I think this week I'm going to implement a limit of 1 request every 5 seconds per IP on the Public API.

Therefore, I suggest you use the TCP feed and feed that into your own VRS instance and smash your own VRS server.

My guess is you are getting handed off to different servers each time. If you are requesting the feed so fast that you notice planes are not in the same positions - then you should be using the LIVE TCP stream and filtering on whatever you are doing on your end.

 

In my test I am requesting data about every 10 seconds. At http: // public-api.adsbexchange.com / VirtualRadar / AircraftList.json. I will try the TCP feed next

 

As I said before .. public feeds are always getting smashed and a poor way to get data. But ti works for plane watchers.