[RSPS-2011]: Fix speed too high bug #45
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jira Ticket
RSPS-2011
Implementation details
Fix bug when we load a map with custom speeds, close it and the load the same map another time.
When do it GH is not using the correct max_speed for that transport.
We found that the problem was that GH once import the OSM file it stores the max_speed property of the speed encoder in a property file. And because we are setting the custom speeds after that, if we un load and reload the map GH will use the value store in that properties file.
To solve it after import the custom speed we need to save the encoder values another time in the properties files.
Testing
I add a test simulating that behaviour.