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

When saving the robot's position, it saves the gps value in params if it is correct. #12

Open
wants to merge 3 commits into
base: ros-devel
Choose a base branch
from

Conversation

jmnavarrete
Copy link
Collaborator

@jmnavarrete jmnavarrete commented Oct 7, 2024

This pull request introduces GPS integration into the poi_manager module, enhancing the functionality by allowing the capture and use of GPS data for points of interest (POIs). Key changes include adding new GPS-related attributes, methods, and modifying existing methods to incorporate GPS data.

The poi_manager node can subscribe to the gps, so if it detects that the gps value is correct, it will add the information in the param value saving both latitude and longitude obtained from the gps.

GPS Integration:

  • Added import for NavSatFix from sensor_msgs.msg to handle GPS data.
  • Introduced new GPS-related attributes (gps_topic_name, gps_time, gps_msg, gps_timeout) in the __init__ method.
  • Added gpsCb callback method to handle incoming GPS messages.
  • Subscribed to the GPS topic in the rosSetup method.
  • Implemented getCurrentGPSPose method to retrieve the current GPS position.

Enhancements to POI Handling:

  • Modified save_poi_service method to accept an optional params parameter for additional data, such as GPS coordinates. [1] [2]
  • Updated createNewPOIFromRobotPose method to include GPS data in the POI parameters if available.

Configuration Updates:

  • Added gps_topic_name to the configuration dictionary in ServiceInitialPose2D.

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

Successfully merging this pull request may close these issues.

1 participant