You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
Checklist
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
The text was updated successfully, but these errors were encountered: