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

fixed map and costmap misalignement due to wrong frame_id #36

Merged
merged 7 commits into from
Dec 2, 2014

Conversation

mehditlili
Copy link
Contributor

The map published by STDR had "map" as frame ID whereas I am using "world" as global frame_id. This causes a misalignment between static_map and global_costmap in RVIZ. The only way to fix this was to run a parallel map server that publishes the same static map to a different topic (i.e /new_map) but with a frame_id "world" and choose it in RVIZ instead of "/map".
If my description was not clear, I can show you directly on my computer.

@mehditlili
Copy link
Contributor Author

topic renamed to rviz_map. An alternative like you suggested would be to remap STDR map to unused_map and just use the map from map_server.

@mehditlili
Copy link
Contributor Author

I made a pull request to change the frame-id in stdr from map to world. I will let you know when they merge it so that you merge my last changes in turtlebot_stdr.

@stonier
Copy link
Member

stonier commented Nov 11, 2014

@mehditlili : got a link to that stdr pull request?

@mehditlili
Copy link
Contributor Author

@jihoonl
Copy link
Member

jihoonl commented Nov 29, 2014

Any progress on this?

stonier added a commit that referenced this pull request Dec 2, 2014
fixed map and costmap misalignement due to wrong frame_id
@stonier stonier merged commit 71af0e0 into turtlebot:indigo Dec 2, 2014
@stonier stonier added this to the Indigo milestone Dec 2, 2014
@stonier stonier self-assigned this Dec 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants