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

Port MapProjectorInfo msgs from tier4_autoware_map_msgs #103

Open
4 of 7 tasks
mitsudome-r opened this issue Oct 31, 2024 · 1 comment
Open
4 of 7 tasks

Port MapProjectorInfo msgs from tier4_autoware_map_msgs #103

mitsudome-r opened this issue Oct 31, 2024 · 1 comment

Comments

@mitsudome-r
Copy link
Member

mitsudome-r commented Oct 31, 2024

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I've agreed with the maintainers that I can plan this task.

Description

We should move the MapProjectorInfo message from tier4_map_msgs to autoware_map_msgs.
This message is already defined as a interface in Autoware Design Document for Map module and should be added as Autoware's core interface.

Related Links:

I would like to merge them before I port map_loader packages into Autoware Core from Universe

Purpose

The purpose is to move all the interface messages of the outputs of Map components to be in autoware_map_msgs (i.e., from Map -> Sensing, Map->Localization, etc)

Possible approaches

Copy the existing implementation in tier4_autoware_map_msgs into autoware_map_msgs

Definition of done

  • create new MapProjectorInfo message under autoware_msgs
  • release autoware_msgs
  • replace all packages that uses tier4_map_msgs/MapProjectorInfo to use autoware_map_msgs/MapProjectorInfo
  • remove tier4_map_msgs
Copy link

stale bot commented Jan 25, 2025

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the status:stale label Jan 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant