Folks, Been feeding Flightaware for over a year now and am looking in to sharing data with ADSBx The mlat-client is puzzling as one of the required fields is -user 'username' I don't know of any usernames with Adsbexchange so what is that referring to? Geffers
Any plans to have a way to register so we can get stats from that same username (and maybe implant a unique receiver ID so noone can fool with our stats)?
No. We don't track your stats. We don't have the budget or the staff for such things. ADSBx is not a multi-million dollar business selling feeder data commercially to airlines or taking checks to block aircraft from view. Feed data and know that it is going to benefit everyone and the world unlike FA, FR24, et all.
That's not to say we aren't willing let someone take the torch and figure out how to do it. It would require writing a feeder client or having the feeder send additional data from itself ... periodically ... that adds more bandwidth .. more data storage .. more problems ... lot's of more important things to figure out than feeder stats ... For example .. What to do with the JSON archive that is well over 5TB compressed. How to improve MLAT server performance - really only one way to do this is add more server and break globe into smaller squares in areas with many feeders. (https://www.ovh.com/world/dedicated-servers/all_servers.xml?range=game - roughly $130/mo .. so about $260/mo) 2 more of these would do it .. maybe ... then taking the time to get it all working again. How to prevent commercial businesses from not contributing to ADSBx but thrashing the servers with requests. Commercial businesses don't seem to want to setup and and support the site. Multiple FBO in US and Europe use the site to track client aircraft that are on blocklist - do you think even one of them would put up a feeder? No. But they have no problem sending emails and complaining. How to prevent people who are downloading the JSON archives and reselling the data. We've caught 2 in the last 6 months! Need people to go around kneecapping these guys and digging shallow holes. Fixing whatever is wrong with VRS database updates and how to get people back to updating it. .. the list goes on .... Oh and I forgot -- figuring out this stupid forum so I can mod some people!
Not that this is really important... just a question like that... but having the need for people to have their receiver associated with an account would probably help you contact them in case of problems...
When they sign up for a custom port they can leave email. But I agree - I just don't know how we could feasibly do it without writing a feeder client.
Does the client allows email address as the username ? If so changing the instructions to tell people to put their email might be a start...
lot's of funny characters ... etc etc ... I'm not sure and it's probably not something worth risking. If they install the ADSBx custom image then I see them on ZT. If they install the FA ADSBx image then there is a field for contact information and it sends that to an ADSBx server. I could write a bash script to ping our servers ...
All of my feeds had a common root and then something descriptive. I also put my email address in the ADSBx portion of the feeder config. My favorite thing is looking at the feeder map and seeing my new sites pop up as a google map pin. I just added a new one today where no one else was close.
