Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unsupported topic type type for sensor GPS #2

Open
droter opened this issue May 15, 2018 · 1 comment
Open

unsupported topic type type for sensor GPS #2

droter opened this issue May 15, 2018 · 1 comment

Comments

@droter
Copy link

droter commented May 15, 2018

Hi,

What are the GPS message types supported?
Is it possible to add:
sensor_msgs/NavSatFix
nav_msgs/Odometry

In the GPS config:
'GPS':
type: AbsolutePosition
is_master: False
frame_id: /gps_link
topic: /enu
topic_type: geometry_msgs/PoseWithCovarianceStamped
use_header_stamp: True
static_covariance: True
covariance: [0.7, 0.0, 0.0,
0.0, 0.7, 0.0,
0.0, 0.0, 1.0 ]

Thanks,

Matt

@DavideACucci
Copy link
Collaborator

DavideACucci commented May 15, 2018

Dear Matt,
NavSatFix is not directly applicable, as it contains geographic coordinates (lat/lon/h) whereas roamfree determines positions and orientations with respect to a East-North-Up Cartesian frame. To use GPS receivers, geographic coordinates need to be transformed beforehand. One solution is to convert from lat/lon/h in WGS84 (as from the GPS receiver) to XYZ coordinates with respect to an arbitrary (user defined) local-level frame. One way is to use geographiclib.

DavideACucci pushed a commit that referenced this issue Feb 3, 2022
added previous state in backward augmented state

Approved-by: Davide Cucci
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants