Bug report #4050
GPSD Server WATCH request
|Affected QGIS version:||master||Regression?:||No|
|Operating System:||Windows||Easy fix?:||No|
|Pull Request or Patch supplied:||Yes||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||14036|
The JSON command send to GPSD server (QGis Gps Tracker module) doesn't change the server emitted packet type to NMEA.
Gps Tracker just disconnects from the server, because he can't handle the gpsd server specific packet format.
Just a small fix.
#6 Updated by Joseph Wolf about 8 years ago
I've been using the RPM version for Fedora 15:
Quantum GIS - 1.7.4-Wroclaw 'Wroclaw' (exported)
It doesn't have the fix. My work around was to execute the following in the shell:
gpspipe -r | nc -l 5555
I then just connect to my fake GPSD at port '5555'. Not pretty, but it saves the the trouble of making a build environment.
#9 Updated by Giovanni Manghi about 8 years ago
- Status changed from Closed to Feedback
- Target version changed from Version 1.7.1 to Version 1.8.0
- Resolution deleted (
Tomas Vrana wrote:
This patch actually broke my gpsd support. Reverting the patch fixed the problem.
so this means that the patch fixed one issue but created a new one? If yes, can you please detail more? so we can eventually close again this ticket and/or file a new one, Thanks.
#10 Updated by Tomas Vrana about 8 years ago
Since last spring I have used gpsd: 2.96 (revision 2011-12-02T19:52:26) with qgis on OpenSuSE with current qgis version from GEO repository. After one of the updates during fall it suddenly stopped working and it still doesnt - current version is qgis-1.7.4-8.6.i586. Since that time I have been using GPS directly via COM port. Last week I needed to do some outdoor mapping using NTRIP corrections so I digged a little deeper and found this patch. After I have changed the request from 'raw' to 'nmea' in GIT version I was able to connect to gpsd again.. I guess it could it could be related to the fact that my GPS uses the 'ublox binary' protocol to talk with gpsd ?