data update (systematic cleanup: "^Str\." -> "Strasse")
wwwdata.t: don't use If-Modified-Date in the future

It seems that in this case the response is always a 200. Now the
If-Modified-Date time is set to "now", so the envisioned 304 response
works now.
GPS::GpsmanData::Stats: a little bit more Pod
GPS::GpsmanData::TkViewer: new -statsargscb option

Also, Pod now documents all constructor options.
SRTShortcuts: gps_data_viewer with places/areas support in Stats window
added scrollarray.js
test for scrollarray.js
ScrollArray: added as_array() method
ScrollArray test: test as_array() and empty array
ScrollArray: empty() method, with test
bbbikeleaflet: very experimental accelerometer support
fragezeichen2org.pl: better wording

"expired records, sort by dist" instead of "alternative sorting"
vectorutil.t: better diagnostics in offset_line tests

Now the coord lists are compared as strings (with some magic to
protect from floating point inaccuracies), which produces better
understandable diagnostics.
vectorutil.t test: corrected coords for 45degree case
offset_line: simplified math a little bit
GPS::GpsmanData::Tk: destructor should check for definedness

It seems that $v is sometimes undef, for whatever reason.
offset_line: fix behavior for "large" angles

Now offset_line returns three offsetted points for large angles
(>90degrees). This fixes previous bad behavior if angles were near
180degrees.

Bad examples in the past were a comments_path entry ("Fussgaengerampel
oestlich der Muenchener Str. zum Ueberqueren benutzen") and the bbd
produced by the current-gps-routes.pl script.
vectorutil test: improved offset_line testing

* dissolved TODO in offset_line test with 180deg angle
* more test cases
* corrected test cases
* test_offset_line helper can deal with different length lists for
  hin/rueck
* set $Test::Builder::Level in test_offset_line
data update (u.a. completion of Waldesruh)