4 ms·
Why write a new gpsd when a mature one exists? Why not just write a Go interface to it?
by huslage 8y ago
Why write a new gpsd when a mature one exists? Why not just write a Go interface to it?
- djsumdog 8y agoYea I didn't get that either. I have a Python sensor gathering app (LtSense) that uses the gpsd python bindings and it works really well. I mean if he's targeting one GPS device, this might work fine, but GPS targets a lot of devices with lots of fixes for broken protocol implementations.
- ocdtrekkie 8y agoPersonally I bought a cheap USB GPS device (GlobalSat BU-353-S4) that offers NMEA compliant strings, and I coded off the NMEA spec. I don't think for a personal project it's unreasonable to say "code for spec, and buy a GPS receiver that meets it".
- akhenakh 8y agoI've tried to explain this in part 1: I assume you talk about gpsd? or libgeoclue? gpsd is slow to start because it tries to detect the baudrate as stated in the manpage Autobauding on the Trimble GPSes can take as long as 5 seconds I didn't find any solutions to disable this behaviour. libgeoclue is a giant ecosystem relying on tons of libraries to work with and it does not work on my system.
- deleted 8y ago[deleted]
- akerro 8y agoNo, a cheap tablet with Android and install OsmAnd~