Publishing an empty cloud when stopping to republish a pointcloud
Overwriting last pointcloud with one point close to origin, shouldn't be added to obstacle map
Merge pull request #90 from nilsbore/hydro-devel

Fixing a problem where move_base would keep adding obstacles from the last published pointcloud. I might actually re-write this to have the republish node publish an empty pointcloud every now and then to stop warnings from move_base that the sensor is not longer within the bounds of the map.