Thanks so much for your quick replies.
Here’s one row of the json as decoded from the chunk.gz file in Chrome’s developer console:
{ "now" : 1614176304.1,
"messages" : 5,
"aircraft" : [
{"hex":"aa50c9","altitude":3000,"vert_rate":256,"track":58,"speed":158,"mlat":[],"tisb":[],"messages":3,"seen":5.5,"rssi":-28.6},
{"hex":"000000","squawk":"1735","mlat":[],"tisb":[],"messages":2,"seen":63.4,"rssi":-39.1}
]
}
That’s cut off…
And it’s the wrong format.
"altitude":3000
dump1090-fa uses alt_baro and alt_geom.
So you’re not using dump1090-fa.
Or you’re using one that’s 3 years old or something before i even started doing ADS-B stuff.
Maybe just start over with a fresh Raspbian if you’re really using something that old? 
Raspbian Lite: ADS B receiver · wiedehopf/adsb-wiki Wiki · GitHub
Hmm, not sure how that got cut off.
This is installed on a fresh copy of Raspbian but I installed an older dump1090-fa deb so that must be the problem. I didn’t realize they had changed the data schema in recent updates.
Thanks for your help.
It really shouldn’t be.
Can you check if it’s really dump1090-fa that is running?
pgrep -af dump1090
Yes, it claims to be dump1090-fa 3.1.0
I’m going to compile and install the new version now.
4.5 years out of date, then (3.1.0 was released in Sep 2016)
My, how time flies! It’s been working great until now!
If you are using Raspbian Stretch or Buster on RPi, then there is no need to compile. Prebuilt packages are available from Fliggtaware repository.
wget https://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_4.0_all.deb
sudo dpkg -i piaware-repository_4.0_all.deb
sudo apt-get update
sudo apt-get install dump1090-fa
Thanks, but I’d prefer to compile myself and avoid 3rd party repositories.
OK compile it if it suites and satisfies you.
However even if you compile, you cant avoid the “third party” as the source code is provided by the same third party who supplies repository packages (i.e. Flightaware)
For sure. Just keeping things as clean as possible.
It seems that timelapse1090 seized to work after upgrading to Piaware v5 showing clock time as n/a.
Any idea how to solve this?
Try running the tar1090 install script it fixes common issues that might affect the timelapse history loading as well.
Thanks Wiedehopf, problem solved!
using Timelapse1090, I really like it. I was wondering: can the data Timelapse1090 is using be exported to (eventually) csv file-format?
Lots of things are possible.
But i will certainly not program it.
Also how would you structure the CSV?
An entry for every location the plane occupied … gets you very large and bulky file.
Hi Wiedehopf,
Yes I can imagine the files will be bulky. What is the data file Timelapse1090 uses for the playback? I will give it a shot from there 
Data is in /run/timelapse1090 the chunk_XX.gz files.
But really you would be better served just reading the /run/dump1090-fa or /run/readsb aircraft.json in regular intervals as timelapse1090 is doing exactly that.
Maybe you’re interested in a different approach, it writes a json file per hex code and day: GitHub - wiedehopf/tar1090: Provides an improved webinterface for use with ADS-B decoders readsb / dump1090-fa
Destroy sd-card is somewhat of a joke, it’s not too write intensive but putting a warning label on doesn’t hurt …
Biggest drawback is that you’d have to index yourself but display of tracks in tar1090 using the history tab after selecting an aircraft or searching for the hex number will let you check all the history you have on that plane by clicking through the days.
This kinda needs an index as mentioned … useful nonetheless.
Is Timelapse working on PiAware 5.0?
I just upgraded to 5.0 but the timelapse page just shows the map, no flights in it (after about 20 minutes).
Thanks
Install tar1090 to fix up the lighttpd, you can remove that if you don’t need it but it will fix up the lighttpd configuration stuff.