I would like to be able to see historical flight data from my piaware. I do not see a way to see my piaware site activity other than the positions tab that only displays the previous hour.
I do not know how to write code and I am not the person who should be doing much typing at a command prompt. Is there an application to save something like a .csv file to a google docs account that does not require command line coding?
When you say “positions tab”, what precisely do you mean? I have been hanging around here for six years and have never heard that term.
Are you talking about this section on your feeder page?
To my knowledge, the default installation of PiAware (or FlightRadar24, or most others that I am aware of) does not save any historical data. The primary purpose of these feeder apps is to get your data into their system(s). The ability to view your own data at all is more of a cookie and pat on the head to encourage you to feed.
There are several home-grown solutions that individual users have created to save your data to a local database, most requiring a range of skill somewhere between ‘high’ and ‘very high’.
There is a Windows app called Virtual Radar Server (VRS) that can be used to pull data from your Pi and display it on a web page, and it has an optional plugin to record what it sees into a database, but it’s not a default part of the configuration and the only thing worse than VRS support is VRS documentation. And once you have it in the database, you still have to do something with that data.
Summary is that I am not aware of any pre-packaged system that records and keeps historical data from your feeder and presents it in any useful way.
Sorry, not the best news, but this isn’t really the use case that the designers envisioned.
Thank you for the info. Yes, when I say “positions tab” it is the one you showed that is titled “flights with positions…”
I like your Cookie and Pat on the head, great way to sum it up. The way they billed the Enterprise Account, I would have thought it would give you access to historical data you piaware was sending them.
The VRS may very well be the ticket for what I want to accomplish. I do more research on it to learn more. My bad for that assumption. Thanks.
Maybe you want something like that?
Very simple solution, but it seem to be working.
GitHub - georgeglessner/FlightLogger: Log Unique Flights Per Day to CSV From dump1090
Hi,
Not an answer, but just a few comments from someone that also decodes 978 UAT like you.
One problem you are going to run in to is that most of the utilities already out there are for 1090, not the 978 which you are interested in. Many read in direct beast binary or .json text data to create the data.
I do use VRS for testing, and last night did a quick test to see if VRS was able to directly handle the 978 .json data. It can not. The dump978-fa .json output is different than the 1090 format. There might be a VRS utility that can handle it, but I am not aware of one.
The way I handle my 978 UAT and make it more compatible with other programs like VRS and PlanePlotter, is to run a utility to convert the 978 raw data from dump978-fa to AVR. VRS can handle that AVR data directly and so can PP. I also run it through a spare copy of dump1090 to convert the AVR to an even more universal format of beast binary. These extra steps require some command line work, which I know you are trying to avoid. This is how I feed 978 to VRS and PP.
PlanePlotter does an excellent job of easily doing daily reports and logs, but that software does not natively handle 978 UAT raw data or 978 .json from something like dump978-fa. That’s why I first convert it to AVR, then to beast, for feeding other software.
Since 978 UAT is primarily just in the US and border areas, most of the utility type work is not designed to handle that format. That definitely complicates your search for an easy solution.
Good luck,
-Dan
I’m using a variation of the Cactus Project to create a .csv file for flights I see in a day. I checked and I see 978 UAT aircraft in the file. This is captured from /run/dump1090-fa/aircraft.json. So 978 UAT seems to be in that file.
Hi Jim,
He is running 978 UAT only. There is nothing on the 1090 side, and likely no copy of dump1090-fa providing that combined .json output. The test I did last night was to see if VRS could handle the 978 .json file he has. I did not expect it to. It connects fine of course, but does not decode the 978 traffic in that 978 .json feed. The format is likely very different.
My solution here is to convert 978 UAT raw to AVR for other software use.
-Dan
I appreciate the link. But it is 1090 and I am running 978 only. Which I read is different enough to require a different method.
I did find this github project that works with 978, but since I am not a programmer, I cannot tell if it just populates the map, or saves data for later retrieval.
And here is a link to a dump978 project that seems to be a bit more current.
Well of course you could use dump1090 to just view your own local data and not feed any site if you want to. As a matter of fact I did that for a while prior to installing piaware.
That’s what you installed if you used the FlightAware repo.
It’s their GitHub…
There’s a number of additional things required to change from uat to ‘normal’ formats.
Such as GitHub - adsb-related-code/uat2esnt: 978 UAT2ESNT converter
But again, it’s going to be well beyond standard capabilities.
Sure you could. But dump1090 is a decoder, not a feeder. And it still doesn’t store any historic data like the OP wants to do (and doesn’t handle 978 like the OP wants to do).
I think we can agree that the companies that created these feeder apps didn’t create them primarily to make it easier for users to view their own data.