When replaying recordings, the read files are binary, so the file open
needs to reflect this so that spurious end of file characters aren't
misinterpreted.
* Install dump1090 and faup1090 to /usr/bin (It's Linux-standard, not my
first choice.)
* Build dump1090 to expect HTML and Javascript files in
/usr/share/dump1090/public_html
* Make 'make -f makefaup1090 install' install the dump1090 HTML and Javscript
files in the above directory.
* With this build style dump1090 can be invoked from anywhere and it will
find its files.
For remotely received messages that have a mlat timestamp, we have no
useful way of turning that timestamp into a wallclock timestamp, so
don't try, or we'll just produce wildly wrong results (_days_ in error)
There is a danger in always using relative decoding where possible.
If there is an undetected error in the first pair of messages received,
then global CPR decoding will give a bad position, and subsequent
relative decoding will just walk around near that bad position even
though many error-free pairs of odd/even messages may have been received.
The first pair of position messages also tends to be the most error-prone, as
they are usually received at the extreme edge of receiver range.
(I see this happen at least once a day in practice)
So, instead, prefer to use global decoding when we have sufficiently recent data.
With recent data this should always be as good as relative decoding, and it
avoids getting stuck with bad data for long periods of time. If we don't have
enough recent data for a global solution, fall back to relative decoding.
If a CPR message with an undetected error is received this can produce out-of-range results for latitude.
e.g. even latitude of 78000, odd latitude of 0 produces a latitude index j=35 and rlat0 = 213.
* With --net-only switch dump1090 wouldn't look for an RTLSDR device
* Without --net-only switch dump1090 would abort if it couldn't find an RTLSDR
device.
* Now with --net --no-rtlsdr-ok dump1090 will try to find an RTLSDR device but
go ahead and start either way.
* It isn't needed.
* Also include /usr/share/dpkg/buildflags.mk in Makefile and makefaup1090
and add our compile-specific CFLAGS to the CFLAGS that sets up
so we compile with the preferred Debian build flags.
* If faup1090 can't start because the 10001 port is already in use it will now
exit with an exit status of 98 (EADDRINUSE).
* Emit the faup1090 version number if faup1090 is run with the --help argument.
* Make wicked sure we don't come up on any other ports that we shouldn't be on.
* Add "install" argument to faup1090 makefile makefaup1090.
BUGZID:
It seems server code should be compatible with HTTP 1.1; the features
unique to 1.1 mostly are upon the client to support, and some headers
used (for example Cache-Control) may need 1.1.
Oliver Jowett
MalcolmRobb
Karl Lehenbauer
hhm
Jeff Lawson
Karl Lehenbauer