Hi there, Became a feeder earlier today and after installing & setting up (and waiting 5 mins before my feeder page was green and I was feeding data) I noticed a few things; My site was called Oxfordshire It was classed as Southern UK Synced peers were reported as 53 Looking again now I see; My site is now called Oxfordshire _20 It is now classed as Northern UK I'm only synced with 43 peers although I get how this might fluctuate I have also noticed that my location on the map is off by @2.5km or so as the crow files although I don't have a reference for this mornings location on the map because I never zoomed in close enough! Is this normal behaviour as I get that a precise location might not want to be advertised but curious as to why all the changes? Thanks & kind regards, -=Glyn=-
That shouldn't happen. At least i'm not sure how that would happen. As you can see on the map ... it usually decides correctly ;P The map has a note about that yes.
I'm brand new to ADSBx so just feeling my way in gently so if you're not sure how that would happen then I don't have a hope in hell of figuring it out! All of my peers are North of me to the point where its like I have a hard, horizontal cut off point directly underneath me with only one synced peer south of me although I count a dozen or so within striking distance. Yeah I did see a For privacy: locations are approximate notice at top left. Nothing too vital and I'm happy I've added ADSBx as a feeder which brings me up to 4 now so I'll let the dust settle before I tamper any more. I've installed the Stats package and if I click on the Statistics link from the my/ip ADSBexchange Anywhere page I see an aircraft count graph and flight data chart. Is that all of it or have I missed a trick here and is there another way to access the Stats and/or is there any other local ADSB interface I can access other than the usual tar1090? -=Glyn=-
Two links some rudimentary statistics and a map that you can share with other people using that link. Like what? .... No. Local data is local data ... displaying it is in no way or shape connected to feed clients. FA calling the local webinterface skyaware and putting their branding on is highly confusing .... and annoying to explain over and over. MLAT zones are unavoidable unless you can majorly improve the server handling the data and calculating the MLAT positions. Have a look: https://github.com/adsbxchange/mlat-server Python3 apparently encodes the coordinates a bit different sometimes it seems. Anyhow it shouldn't matter which zone you're in. Well it will show in the position accuracy of MLAT being better in one or the other direction. But as mentioned can't be avoided.
