added commments to the PassatStatus message description
velodyne processor: not skipping points on car

Because we forget that this "driver" does this processing it's then
puzzling why some points don't show up...

Instead, write a node to filter a region and publish on a separate topic
minor modifications to data_reader
filtering out points on junior at the velodyne driver level

filtering is optional, controlled by parameter
/driving/velodyne/filter_points_on_car

The filter eliminates points that fall within a bounding box given in
velodyne frame. The bounding box min and max points are retrieved from
the ros parameter server.
Extend data reader for more types
Add more EStop and PassatStatus support
fixed some stuffs in kittireader

- filtering out points within the car bounding box
- the matlab script that Devin used to create the .kit did not call
fclose before returning so the .kit files are sometimes corrupted at the
end. Implemented some safe guards to try to catch it.
fixed a bug in data_reader (last spin)
moved the imu_kitti programs to their own package in the private repo
improved kittireader
better initialization of spin reader and bag tf listener
added localize/add_gps_offset
log_run: skipping static_map
calibrating intensities by default

turns out that the velodyne pointcloud node was not calibrating
intensities because the calibrate_intensities parameter was not set and
defaulted to false. Changed to default to true and set the parameter in
junior2.launch.

see #178 in the driving repo
Fixed another instance of boost::filesystem3.
fixed time stamp in kitti reader now that I fixed the matlab scripts
fixed the double seam in kitti playback
kitti velodyne reader: fixed h_angle
simplified the spinQ logic in SpinReader
adjusted the kitti timestamps for better synchronization