Hi wiedenhopf,
For my site 107377 I’ve changed the ‘Precision on Coverage Map’ setting from 1km to exact.
In addition, my settings on the FA webpage show:
Antenna elevation above ground: 46 feet
Ground elevation: 39 feet
Has this corrected the issue?
The “Precision on coverage map” doesn’t matter in this regard.
But something has changed.
I think just the distance calculation was thrown off, seems to be showing now.
Still not showing quite like i would expect, but maybe that’s because you are the only receiver in the area.
I think you can remove your other stations by selecting their stats page via the orange bar and clicking on the cog wheel.
If there is no option yet for removing them it will show up in the next few days of inactivity on those stations.
That looks good.
You can restart the dump1090 part of combine1090 like this:
sudo systemctl restart combine1090-dump
Then the graphs should start displaying range correctly.
Hi wiedhopf,
Yes, the position is quite close now, not exact but at least I’m not in the ocean anymore!
As recommended, I’ve removed the other stations.
I’ve graciously been given a FlightAware Pro Stick Plus, courtesy of SweetPea11 and have added a new site: YPCC2 - 107512
Thanks for all your help.
sudo nano /etc/default/combine1090
You can change the 1 to a 2 in this line:
JSON_OPTIONS="--json-location-accuracy 1"
After restarting combine1090-dump the webinterface will show an accurate location.
The position on the stats page is always a bit off.
The “Exact” setting doesn’t really work, the position is still rounded.
(actually the 1km setting on the stats page results in a more accurate position than the “exact” setting which is the same as the 10 km setting)
But that setting only affects the coordinates being displayed to other users when they view your stats page.
So it doesn’t really matter.
Hi wiedenhopf,
Settings changed.
sudo nano /etc/default/combine1090
JSON_OPTIONS=“–json-location-accuracy 2”
sudo systemctl restart combine1090
Thanks for the info on the ‘exact’ setting.
Now that I have two receivers, could I enabled MLAT? And will it work properly?
You need at least 4 receivers for MLAT and they would need to be 1km apart from each other.
(300 m apart in might also work)
But your microADSB receiver can’t be used for MLAT anyway because the receiver doesn’t give timestamps for its messages.
I’d expect all aircraft operating to Cocos to have ADS-B?
It’s a bit confusing, combine1090 consists of two services, you need to restart the dump1090-fa portion:
sudo systemctl restart combine1090-dump
When the system was running there last year the military and coast watch planes were not surprisingly not displayed on flightaware.
Maybe 4 sites to get MLAT working can be a project for another day.
S.
Does anyone know where I can find information on the data formats for:
AVR format
BaseStation format
Beast binary format
I would like to stream and filter this data from my FF
https://github.com/flightaware/dump1090/blob/752a7aeac02f5a1765684ccd3d2bfb2ff2860d8b/net_io.c#L1203
https://github.com/flightaware/dump1090/blob/752a7aeac02f5a1765684ccd3d2bfb2ff2860d8b/net_io.c#L559
https://github.com/flightaware/dump1090/blob/752a7aeac02f5a1765684ccd3d2bfb2ff2860d8b/net_io.c#L1317
Other info:
It’s often easier to look at the aircraft.json, it represents the current aicraft state for all aicraft being received.
Thank you, I will give this a try. My desire is to pull all local data to track ground movement. I want to be sure to get all of the aircraft data to include, airline, aircraft operator, flight number/id, and tail number as we intend to track the flow of traffic through our de-icing pad to automate tracking of the flow through the area for safety and efficiency. That said, we want to get the streamed data from the two FFs we just mounted, but also need the extended flight data from the database. What I have not been able to ascertain is if that data is streamed through the port data or will it need to be cross referenced from the FlightAware feed?
Just to make you aware none of that is not broadcast.
Well the callsign is and you can derive an airline from that.
For the tail number you already need a database lookup from hex id to tail number.
Anyhow good luck.
You may be interested in a Firehose surface feed, perhaps, which does exactly this sort of aggregation (aggregation of data from FlightFeeders / ASDE-X / flight plan / flight info / registry info / etc) – FlightAware Firehose℠ Flight Data Feed - FlightAware
That’s what e.g. the Jetvision devices (Radarcape, Airsquitter) can display.
But beside the ADS-B information they are using two seperate databases and some other sources, then it’s combined into a single record.
As wiedehopf stated not all information are broadcasted from the signal itself.
You can check the data of the Jetvision Radarcape Demo Receiver operating live here:
https://radarcape-demo.jetvision.de/aircraftlist.html
As said, you can also build your own database with the information coming from the aircraft json file.
If you then get two more tables (flight information, aircraft information) and build relations to it, then you have similar result of what Jetvision is doing without getting their device.
You can use your Pi flight feeder as a receiver in VirtualRadarServer (which runs on Windows but also has a Mono version that runs on Linux.) VRS uses an online database lookup to populate its own local Basestation database, and it can display ICAO hex, registration, callsign, route, airframe make and model, etc. That will give you most of the info that you want, albeit locally only. Just change the default IP address of the receiver from 127.0.0.1 to the local IP of your Pi.
I started with VRS recording the aircraft received at my location.
However i don’t like how VRS has structured the database. You need to have some sort of SQL skills if you use it outside VRS
Almost all relational databases are a flavor of SQL. It’s not hard to deal with. If all you want to do is change some data there are GUI tools that make that easy. There probably are for running custom reports beyond what VRS is capable of too. And anything those GUI tools can do, you can do from the command line if you learn how. (I used to know how to do CLI queries, search & replaces and so on, at least for Microsoft SQL Server, but I haven’t used those skills for so many years I’ve forgotten how.)
I am not saying it’s hard to deal with it. But you need to have some basic understandings.
And the data structure used by VRS is weird and not well set in my opinion