Permit other GPS, RTCM stream via. env vars

First pull request so please let me know if I've missed any best practices.

Added netserial to package scripts.
Optional  sonar.launch uses netserial (socat) as the SonarM8 does not use nmea by default. Space delineated messages were not properly parsed if using nmea_comms.
Remapping tx to rx was what worked for hydro nmea_comms.
Netserial for RTCM as RX is binary
Very confused why it says you made a commit that I made.
It's a good question. I'm on the fence about it.  It makes my life easier.
But it's ugly to include in all.  But it's also not so ugly since it's in
the optional library of launchfiles.



On Wednesday, July 16, 2014, Prasenjit Mukherjee <notifications@github.com>
wrote:

> In kingfisher_bringup/launch/library/sonar.launch:
>
> > @@ -0,0 +1,7 @@
> > +<launch>
> > +  <group ns="sonar">
> > +    <!-- sonar serial comms -->
> > +    <node pkg="kingfisher_bringup" type="netserial" name="netserial_sonar"
> > +      args="2526 /dev/clearpath/sonar 9600" respawn="true"/>
> > +  </group>
> > +</launch>
>
> @mikepurvis <https://github.com/mikepurvis> or @ablakey
> <https://github.com/ablakey>. Do we want to make this a standard? Its not
> standard payload :S. I know its in library, so optionally turning on bag
> recording makes sense but sonars?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/kf/kingfisher_robot/pull/3/files#r15036021>.
>


-- 
Andrew Blakey | GIS Developer | Clearpath Robotics, Inc.
1425 Strasburg Dr. Suite 2A. Kitchener, ON N2R 1H2
T: +1 (519) 513-2416 x 840 | E: ablakey@clearpathrobotics.com |
<ablakey@clearpathrobotics.com> W: www.clearpathrobotics.com