Directions refactoring + Show speed limit #2796

Merged
AntonM030481 merged 5 commits from RouteSegments-refactoring-and-speed-limit into master 2022-06-26 21:35:51 +00:00

5 commits

Author SHA1 Message Date
Anton Makouski
0add8a3ade Fixes for review
Signed-off-by: Anton Makouski <anton.makouski@gmail.com>
2022-06-24 10:33:57 +03:00
Anton Makouski
a3d0914e5a Fixes for review
Signed-off-by: Anton Makouski <anton.makouski@gmail.com>
2022-06-23 19:37:20 +03:00
Anton Makouski
1703c99f75 Fix compile for Linux no unity build
Signed-off-by: Anton Makouski <anton.makouski@gmail.com>
2022-06-22 10:06:20 +03:00
Anton Makouski
3841cbaf04 Fix compile for Linux no unity build
Signed-off-by: Anton Makouski <anton.makouski@gmail.com>
2022-06-21 17:56:59 +03:00
Anton Makouski
5c71e7324f RouteSegments generation refactoring + SpeedLimit
Now RouteSegments generation starts at DirectionsEngine::Generate().
But this is just preparation, when segments are not created,
but turns, street names, any new staff like speed limits are created
with indexes when it should be applied later.
Later in FillSegmentInfo all this info is unpacked to RouteSegments
and populated by segments and junctions.
This approach is overcomplicated and makes difficult adding new info,
like speed limits, by creating more and more data to pack and unpack.
Also extra memory allocations are done for intermediate steps.
Several todo were found mentioning desirability of changes.
For this reason it was decided to create RouteSegments
at DirectionsEngine::Generate() with all available info
with minimal post-processing at later stages.

Signed-off-by: Anton Makouski <anton.makouski@gmail.com>
2022-06-21 16:34:41 +03:00