gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
jazzy

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
kilted

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
lyrical

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
rolling

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

No version for distro ardent showing humble. Known supported distros are highlighted in the buttons above.

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

No version for distro bouncy showing humble. Known supported distros are highlighted in the buttons above.

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

No version for distro crystal showing humble. Known supported distros are highlighted in the buttons above.

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

No version for distro eloquent showing humble. Known supported distros are highlighted in the buttons above.

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

No version for distro dashing showing humble. Known supported distros are highlighted in the buttons above.

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

No version for distro galactic showing humble. Known supported distros are highlighted in the buttons above.

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

No version for distro foxy showing humble. Known supported distros are highlighted in the buttons above.

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
humble

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_msgs gps_tools gps_umd gpsd_client

ROS Distro
iron

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	ros2-devel
Last Updated	2026-07-22
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_msgs	3.1.0
gps_tools	3.1.0
gps_umd	3.1.0
gpsd_client	3.1.0

README

gps_umd

This package contains messages for representing data from GPS devices and algorithms for manipulating it.

This branch converts the messages and algorithms in this repository to support ROS 2 Dashing.

There have been a few architectural changes; if you were using these packages in ROS1, note that the gps_common package has been split into two packages: gps_msgs contains only message definitions, and gps_tools contains the nodes and scripts that were in gps_common. In addition, all of the C++ nodes that were in this repository have been converted into Components.

Build Status

Continuous integration status

Build farm status and released packages

ROS2 Distro	ROS2 Build Farm	Released packages
Humble		gps_msgs gps_tools gpsd_client
Jazzy		gps_msgs gps_tools gpsd_client
Kilted		gps_msgs gps_tools gpsd_client
Lyrical		gps_msgs gps_tools gpsd_client
Rolling		gps_msgs gps_tools gpsd_client

gpsd_client Parameters

The gpsd_client::GPSDClientComponent node accepts the following parameters:

Parameter	Type	Default	Description
`host`	string	`localhost`	Hostname or address of the gpsd server to connect to.
`port`	int	`2947`	TCP port of the gpsd server.
`frame_id`	string	`gps`	`frame_id` set on the header of published `GPSFix` and `NavSatFix` messages.
`publish_rate`	int	`10`	How often, in Hz, to poll gpsd and publish. Values `<= 0` are rejected with a warning and fall back to 1 Hz.
`use_gps_time`	bool	`true`	Stamp `NavSatFix` messages with the time reported by the GPS receiver instead of the current ROS time.
`check_fix_by_variance`	bool	`false`	Discard fixes whose reported variances (`epx`/`epy`/`epv`) are not finite. gpsd reports a status of OK even when there is no current fix, as long as there was one previously; this rejects those stale results.
`override_augmentation_source`	bool	`false`	When gpsd reports a DGPS fix, always report it as an SBAS fix, whether or not a satellite with an SBAS ID was used in the solution. Useful for receivers that apply SBAS corrections without listing the SBAS satellite in their skyview. Affects both `NavSatFix` and `GPSFix` status.

These are the node’s built-in defaults, used when a parameter is not set. They match the config file shipped in gpsd_client/config/gpsd_client.yaml, which is what gpsd_client-launch.py loads, so launching from that file and instantiating the component directly behave the same.

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_common gps_umd gpsd_client

ROS Distro
lunar

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	master
Last Updated	2024-05-15
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_common	0.3.4
gps_umd	0.3.4
gpsd_client	0.3.4

README

gps_umd

This package is a space to stage messages and common GPS-processing routines. The previous maintainer has not released these packages since ROS Indigo; this fork was created in order to fix them up and release them for ROS Jade and Kinetic.

One change of note is that in the version of libgps in Ubuntu 16.04, the STATUS_DGPS_FIX flag was removed, so the gpsd_client package will be unable to indicate whether DGPS was used in a fix or not.

Otherwise, the API is unchanged; see http://wiki.ros.org/gps_common .

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_common gps_umd gpsd_client

ROS Distro
jade

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	master
Last Updated	2024-05-15
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_common	0.3.4
gps_umd	0.3.4
gpsd_client	0.3.4

README

gps_umd

This package is a space to stage messages and common GPS-processing routines. The previous maintainer has not released these packages since ROS Indigo; this fork was created in order to fix them up and release them for ROS Jade and Kinetic.

One change of note is that in the version of libgps in Ubuntu 16.04, the STATUS_DGPS_FIX flag was removed, so the gpsd_client package will be unable to indicate whether DGPS was used in a fix or not.

Otherwise, the API is unchanged; see http://wiki.ros.org/gps_common .

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_common gps_umd gpsd_client

ROS Distro
indigo

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	master
Last Updated	2024-05-15
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_common	0.3.4
gps_umd	0.3.4
gpsd_client	0.3.4

README

gps_umd

This package is a space to stage messages and common GPS-processing routines. The previous maintainer has not released these packages since ROS Indigo; this fork was created in order to fix them up and release them for ROS Jade and Kinetic.

One change of note is that in the version of libgps in Ubuntu 16.04, the STATUS_DGPS_FIX flag was removed, so the gpsd_client package will be unable to indicate whether DGPS was used in a fix or not.

Otherwise, the API is unchanged; see http://wiki.ros.org/gps_common .

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_common gps_umd gpsd_client

ROS Distro
hydro

Repository Summary

Checkout URI	https://github.com/ktossell/gps_umd.git
VCS Type	git
VCS Version	master
Last Updated	2014-06-20
Dev Status	UNMAINTAINED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_common	0.1.7
gps_umd	0.1.7
gpsd_client	0.1.7

README

No README found.

CONTRIBUTING

gps_umd repository

gps_common gps_umd gpsd_client

ROS Distro
kinetic

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	master
Last Updated	2024-05-15
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_common	0.3.4
gps_umd	0.3.4
gpsd_client	0.3.4

README

gps_umd

This package is a space to stage messages and common GPS-processing routines. The previous maintainer has not released these packages since ROS Indigo; this fork was created in order to fix them up and release them for ROS Jade and Kinetic.

One change of note is that in the version of libgps in Ubuntu 16.04, the STATUS_DGPS_FIX flag was removed, so the gpsd_client package will be unable to indicate whether DGPS was used in a fix or not.

Otherwise, the API is unchanged; see http://wiki.ros.org/gps_common .

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_common gps_umd gpsd_client

ROS Distro
melodic

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	master
Last Updated	2024-05-15
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_common	0.3.4
gps_umd	0.3.4
gpsd_client	0.3.4

README

gps_umd

This package is a space to stage messages and common GPS-processing routines. The previous maintainer has not released these packages since ROS Indigo; this fork was created in order to fix them up and release them for ROS Jade and Kinetic.

One change of note is that in the version of libgps in Ubuntu 16.04, the STATUS_DGPS_FIX flag was removed, so the gpsd_client package will be unable to indicate whether DGPS was used in a fix or not.

Otherwise, the API is unchanged; see http://wiki.ros.org/gps_common .

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

CONTRIBUTING

gps_umd repository

gps_common gps_umd gpsd_client

ROS Distro
noetic

Repository Summary

Checkout URI	https://github.com/swri-robotics/gps_umd.git
VCS Type	git
VCS Version	master
Last Updated	2024-05-15
Dev Status	DEVELOPED
Released	RELEASED
Contributing	Help Wanted (-) Good First Issues (-) Pull Requests to Review (-)

Packages

Name	Version
gps_common	0.3.4
gps_umd	0.3.4
gpsd_client	0.3.4

README

gps_umd

This package is a space to stage messages and common GPS-processing routines. The previous maintainer has not released these packages since ROS Indigo; this fork was created in order to fix them up and release them for ROS Jade and Kinetic.

One change of note is that in the version of libgps in Ubuntu 16.04, the STATUS_DGPS_FIX flag was removed, so the gpsd_client package will be unable to indicate whether DGPS was used in a fix or not.

Otherwise, the API is unchanged; see http://wiki.ros.org/gps_common .

NavSatFix vs. GPSFix

The node fix_translator converts sensor_msgs/NavSatFix messages to gps_common/GPSFix messages and vice versa. Usage examples:

Translate from NavSatFix to GPSFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from NavSatFix to GPSFix //-->
      <remap from="/navsat_fix_in"  to="/YOUR_NAVSATFIX_TOPIC"/>
      <remap from="/gps_fix_out"    to="/YOUR_GPSFIX_TOPIC"/>
  </node>

Translate from GPSFix to NavSatFix

  <node name="fix_translator" pkg="gps_common" type="fix_translator">
    <!-- Translate from GPSFix to NavSatFix //-->
       <remap from="/gps_fix_in"     to="/YOUR_GPSFIX_TOPIC"/>
       <remap from="/navsat_fix_out" to="/YOUR_NAVSATFIX_TOPIC"/>
  </node>

Only adjust the topic names after “to=” in each remap line.

gps_umd repository

ROS Distrohumble

Repository Summary

Packages

README

gps_umd

Build Status

gpsd_client Parameters

NavSatFix vs. GPSFix

Translate from NavSatFix to GPSFix

Translate from GPSFix to NavSatFix

CONTRIBUTING

gps_umd repository

ROS Distrojazzy

Repository Summary

Packages

README

gps_umd

Build Status

gpsd_client Parameters

NavSatFix vs. GPSFix

Translate from NavSatFix to GPSFix

Translate from GPSFix to NavSatFix

CONTRIBUTING

gps_umd repository

ROS Distrokilted

Repository Summary

Packages

README

gps_umd

Build Status

gpsd_client Parameters

NavSatFix vs. GPSFix

Translate from NavSatFix to GPSFix

Translate from GPSFix to NavSatFix

CONTRIBUTING

gps_umd repository

ROS Distrolyrical

Repository Summary

Packages

README

gps_umd

Build Status

gpsd_client Parameters

NavSatFix vs. GPSFix

Translate from NavSatFix to GPSFix

Translate from GPSFix to NavSatFix

CONTRIBUTING

gps_umd repository

ROS Distrorolling

Repository Summary

Packages

README

gps_umd

Build Status

gpsd_client Parameters

NavSatFix vs. GPSFix

Translate from NavSatFix to GPSFix

Translate from GPSFix to NavSatFix

CONTRIBUTING

gps_umd repository

ROS Distrohumble

Repository Summary

Packages

README

gps_umd

Build Status

gpsd_client Parameters

NavSatFix vs. GPSFix

Translate from NavSatFix to GPSFix

Translate from GPSFix to NavSatFix

CONTRIBUTING

gps_umd repository

ROS Distrohumble

Repository Summary

Packages

README

gps_umd

Build Status

gpsd_client Parameters

ROS Distro
humble

ROS Distro
jazzy

ROS Distro
kilted

ROS Distro
lyrical

ROS Distro
rolling

ROS Distro
humble

ROS Distro
humble

ROS Distro
humble

ROS Distro
humble

ROS Distro
humble

ROS Distro
humble

ROS Distro
humble

ROS Distro
iron