-
Notifications
You must be signed in to change notification settings - Fork 10
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
feat: add multi lanelet parser #17
base: main
Are you sure you want to change the base?
feat: add multi lanelet parser #17
Conversation
I was wondering if we should create another parser for loading multiple files. Are there any reasons for not merging the Lanelets after loading each files one by one? |
After call |
@reviewers |
@soblin Could you review and test this PR? |
@soblin I misunderstood. In the parent PR, Maxim-san already has tested the related PR including this PR. So please ignore my request to test. |
@mitsudome-r Could you respond to this message? |
Signed-off-by: Barış Zeren <[email protected]>
@kosuke55 @soblin @Motsu-san @mitsudome-r @takayuki5168 @youtalk |
class MultiFileLoader | ||
{ | ||
public: | ||
static std::unique_ptr<LaneletMap> loadMap( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you align the function return type to lanelet::LaneletMapPtr
just like lanelet::io::load ? Although I guess lanelet::LaneletMapPtr is just an alias of std::unique_ptr (or shared_ptr)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
loader.lineStrings_, loader.points_); | ||
} | ||
|
||
static std::unique_ptr<LaneletMap> loadMap( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this future related to the differential loading mechanism ? Then can we dynamically add next map while dropping visited map by using the add
and removed
function to each layers, so we do not need to recreate the entire lanelet map whenever ego passes the boundary ?
I think my comments answers your question. I believe it is possible to merge/delete map objects in sliding window manner in the context of differential map loading. Here is my suggestion:
|
You can create a function to merge each layer of Lanelet map as mentioned by @soblin's comment.
(Note that above code is just an image and I haven't tested the code. |
@soblin @mitsudome-r cc: @StepTurtle |
Signed-off-by: Barış Zeren <[email protected]>
18fe5cc
to
2ddb81f
Compare
Hey @YamatoAndo , sorry about this, but I tried a few things and couldn't quite figure out the points from the last comments. I also haven’t had enough time to work on the lanelet reviews. Could I ask for your help with the this PR? Apologies again for the trouble. 🙏🏽 |
@StepTurtle Hi,
After merging this PR, please create a PR similar to #30. Once that PR is merged, we will create a new release tag. |
@kosuke55 @soblin @Motsu-san @mitsudome-r @takayuki5168 @youtalk
Could you support this PR instead? |
@StepTurtle All right, then I'd like to propose moving your implementation in autoware.universe's |
@kosuke55 @soblin @Motsu-san @mitsudome-r @takayuki5168 @youtalk |
Let me follow up on this. |
@mitsudome-r @StepTurtle what are the actions that you've decided to take on this task? |
@mitsudome-r will handle this PR and I guess he will do some updates on code in this week. |
Description
Move autowarefoundation/autoware_common#234 to new
autoware_lanelet2_extension
repository.This PR add a new library class to facilitate the loading of multiple OSM files in lanelet2_extension. These changes were made to support dynamic lanelet loading.
Related links
Proposal Link
Tests performed
In this video, the map in background loaded with current approach and the white map load new class and cannot see any difference. Also the maps which loaded with new class tested with mission and behavior planner and cannot see any problem.
Video Link
Notes for reviewers
Interface changes
Effects on system behavior
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.
In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.
Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.
After all checkboxes are checked, anyone who has write access can merge the PR.