feat(valhalla): increase isochrone limits in valhalla config #77
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
azarz
changed the title
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified Files
|
lgrd
requested changes
Mar 18, 2024
azarz
force-pushed
the
feature/valhalla-isochrone-limits
branch
from
8950fe6
to
75321a9
Compare
Done ! ;) |
lgrd
approved these changes
Mar 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The default values for isochrone contours in valhalla are 2 hours and 200 km. In order to compute the same isochrones in valhalla that we did in pgRouting, we need to increase this limit.
Once this is done, there will be no further need for isochrones in pgRouting, and we could deactivate them in our webservices if needed in case of big sollicitations.