Closed nreinicke closed 1 year ago
Right now in the LCSS matcher we just return the matched road for each trace point but it could be useful to also return the computed trajectory since we have it here.
This would also require updating the MatchResult to include more information (maybe it becomes a dataclass with some optional features like a path?)
Right now in the LCSS matcher we just return the matched road for each trace point but it could be useful to also return the computed trajectory since we have it here.
This would also require updating the MatchResult to include more information (maybe it becomes a dataclass with some optional features like a path?)