diff --git a/README.md b/README.md index b48fd48..0985c95 100644 --- a/README.md +++ b/README.md @@ -267,6 +267,54 @@ sudo wget -O /usr/local/share/tar1090/html/upintheair.json "http://www.heywhatst - It might be interesting to compare to http://192.168.x.yy/tar1090/?pTracks which will by default will display the last 8 hours of traces. +## /tar1090/?pTracks + +- Add /?pTracks to the normal /tar1090 URL you put in +- Shows the last 8 hours of traces you have seen, gives a nice visual representation of your coverage / range +- Can be filtered by altitude with the altitude filter +- Configure a longer duration than 8 hours via the [configuration](#configuration-optional): + +## 0800-DESTROY-SD-CARD + +History function as used for tar1090.adsbexchange.com + +No seriously this writes to disk quite often, it will fill up your sd-card by means of writing lots of little files. + +This is not in any way or form officially supported and you should consider it experimental. +To accomplish this, you need to use the dev branch of my readsb repository. +(https://github.com/wiedehopf/adsb-wiki/wiki/Building-readsb-from-source#wiedehopfs-dev-branch) + +The following options need to be added to for example the decoder options in `/etc/default/readsb` +``` +--write-json-globe-index --write-globe-history /var/globe_history --heatmap 30 +``` +/var/globe_history needs to be a direcotry writeable by the user readsb. +`sudo mkdir /var/globe_history` and `sudo chown readsb /var/globe_history` are useful for that. + +You will also need to point tar1090 to /run/readsb in case you are using another dump1090/readsb. +See the "multiple instances" readme section. + +If you don't want readsb to read data from the SDR, you'll also need to change the receiver options line to something like this: +``` +RECEIVER_OPTIONS="--net-only --net-connector 192.168.2.7,30005,beast_in" +``` +If you have another dump1090/readsb running on the same machine, you'll also need to change all the ports to avoid conflicts. + +This will obviously write data to the hard drive, be aware of that. +The data format is subject to change, don't expect this to be stable. +Be aware of that when upgrading either tar1090 or readsb to a new commit. + +For these features i only maintain the nginx configuration, not the lighttpd configuration. +Thus you'll need to use nginx with the config file provided by the tar1090 install script +or change the lighttpd configuration yourself. +On the default nginx install you'll usually find the server section in this config file: +`/etc/nginx/sites-enabled/default` + +If you can't figure out how to make it work with the above information, please don't ask. +I don't support this feature for the general user base. +This information is only for people who could figure it out from the source code anyhow, +so that they don't have to spend as much time figuring it out. + ## A separate instance with longer data retention for gauging range If this seems too complicated for you or you don't want a 2nd instance, changing / adding PTRACKS=24 to the /etc/default/tar1090 configuration should also extend the history (for /?pTracks only). @@ -319,47 +367,6 @@ sudo cp /usr/local/share/tar1090/html/upintheair.json /usr/local/share/tar1090/h ``` -## 0800-DESTROY-SD-CARD - -History function as used for tar1090.adsbexchange.com - -No seriously this writes to disk quite often, it will fill up your sd-card by means of writing lots of little files. - -This is not in any way or form officially supported and you should consider it experimental. -To accomplish this, you need to use the dev branch of my readsb repository. -(https://github.com/wiedehopf/adsb-wiki/wiki/Building-readsb-from-source#wiedehopfs-dev-branch) - -The following options need to be added to for example the decoder options in `/etc/default/readsb` -``` ---write-json-globe-index --write-globe-history /var/globe_history --heatmap 30 -``` -/var/globe_history needs to be a direcotry writeable by the user readsb. -`sudo mkdir /var/globe_history` and `sudo chown readsb /var/globe_history` are useful for that. - -You will also need to point tar1090 to /run/readsb in case you are using another dump1090/readsb. -See the "multiple instances" readme section. - -If you don't want readsb to read data from the SDR, you'll also need to change the receiver options line to something like this: -``` -RECEIVER_OPTIONS="--net-only --net-connector 192.168.2.7,30005,beast_in" -``` -If you have another dump1090/readsb running on the same machine, you'll also need to change all the ports to avoid conflicts. - -This will obviously write data to the hard drive, be aware of that. -The data format is subject to change, don't expect this to be stable. -Be aware of that when upgrading either tar1090 or readsb to a new commit. - -For these features i only maintain the nginx configuration, not the lighttpd configuration. -Thus you'll need to use nginx with the config file provided by the tar1090 install script -or change the lighttpd configuration yourself. -On the default nginx install you'll usually find the server section in this config file: -`/etc/nginx/sites-enabled/default` - -If you can't figure out how to make it work with the above information, please don't ask. -I don't support this feature for the general user base. -This information is only for people who could figure it out from the source code anyhow, -so that they don't have to spend as much time figuring it out. - ## history not loading issue (possible fix) For a day or so i had a bug in the install script turning symbolic links in /etc/lighttpd/conf-enabled into copies of the files they were pointing to.