Skip to content

Conversation

@carsten-kuebler
Copy link
Contributor

This PR addresses issue #166.

Add landmarks and detected landmarks as new OSI messages.
Add landmarks to GT and detected landmarks to SensorData.
Move field measurement_state to Candidate... messages.

Add landmarks and detected landmarks as new OSI messages.
Add landmarks to GT and detected landmarks to SensorData.
Move field measurement_state to Candidate... messages.
Update datatype to uint64 for cycle_counter.
@carsten-kuebler carsten-kuebler requested a review from a user March 22, 2018 16:43
@carsten-kuebler carsten-kuebler added the FeatureRequest Proposals which enhance the interface or add additional features. label Mar 22, 2018
@carsten-kuebler carsten-kuebler added this to the v3.0.0 milestone Mar 22, 2018
{
// The description of the road marking.
//
optional RoadMarking road_marking = 1;

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be optional Landmark landmark , since we describe CandidateLandmark here, shouldn't it?
The comment should be changed accordingly.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. Thx. I made a bugfix.

Correction of the faulty OSI message CandidateLandmark
@ghost ghost merged commit 52d2e7b into master Mar 23, 2018
@pmai pmai deleted the feature/New-Landmark-Messages branch March 27, 2018 12:17
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

FeatureRequest Proposals which enhance the interface or add additional features.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants