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

Datasources values not being saved correctly during traffic updates #4346

Closed
danpat opened this issue Jul 27, 2017 · 1 comment
Closed

Datasources values not being saved correctly during traffic updates #4346

danpat opened this issue Jul 27, 2017 · 1 comment
Milestone

Comments

@danpat
Copy link
Member

danpat commented Jul 27, 2017

The SegmentDataContainer class is not storing the datasource IDs for segments correctly:

auto GetForwardDatasources(const DirectionalGeometryID id)
{
const auto begin = datasources.begin() + index[id] + 1;
const auto end = datasources.begin() + index[id + 1];
return boost::make_iterator_range(begin, end);
}
auto GetReverseDatasources(const DirectionalGeometryID id)
{
const auto begin = datasources.begin() + index[id];
const auto end = datasources.begin() + index[id + 1] - 1;
return boost::adaptors::reverse(boost::make_iterator_range(begin, end));
}

The logic here sort of looks like it assumes that the datasource is the same in both directions - the code looks like it may have just been ported forward from the first revision of this code, without ever splitting the forward/reverse logic.

This bug has no practical effect on routing, but the debug tiles and annotations=sources results contain bad data.

@danpat danpat added this to the 5.10.0 milestone Jul 27, 2017
@danpat
Copy link
Member Author

danpat commented Aug 2, 2017

Fixed by #4352

@MoKob MoKob closed this as completed Aug 3, 2017
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

2 participants