gps_umd
gps_umd copied to clipboard
swri-robotics
There's about one year of changes that haven't been tagged and pushed to the buildfarm. Can we get a ROS1 release that includes those changes?
With `find_package(gps_tools)` in another ROS 2 package, this CMake warning appears when building that other package: ``` CMake Warning at /opt/ros/galactic/share/gps_tools/cmake/ament_cmake_export_libraries-extras.cmake:116 (message): Package 'gps_tools' exports library 'gps_tools' which couldn't be...
What are the GPS parameters that affect the odometry values? odometry msg values: x:492873.313 y:5527538.68483 I am using the hector_gazebo gps plugin in the simulation environment. How can I get...
As pointed out in https://github.com/swri-robotics/gps_umd/issues/62, many of the fields in the GPSFix and GPSStatus are not populated, poorly named, or have other problems. We don't want to break compatibility, so...
This pull request includes a few code cleanup changes. If you would prefer these as separate pull requests, please let me know. 1. Uses CMake's built-in `find_library` to find `libgps`...
The [GPSFix](http://docs.ros.org/en/api/gps_common/html/msg/GPSFix.html) message has the fields `pitch`, `roll`, `dip` and corresponding uncertainty fields (`err_pitch`, etc.). These fields do not appear populated anywhere by the code in this repository. These are...
It would be nice if this were a lifecycle node to make the behavior more predictable and controllable.
Rather than checking the ```status``` field for the fix validity, we should be looking at the ```mode``` field. These fields are described here: https://gpsd.gitlab.io/gpsd/gpsd_json.html. Currently, the checks on the ```status```...
In the client.cpp source file for gpsd_client we see this: ``` void stop() { // gpsmm doesn't have a close method? OK ... } ``` The documentation for libgpsmm reads...
