You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #3841 (comment) I asked for clarification about relation between extract and contract steps, and requirement of GeoJSON file with timezones.
@karenzshea explained in #3841 (comment) the GeoJSON file is optional and it is required only if .osrm.restrictions file is present.
Then, to disable the conditional turn restriction application by running osrm-extract with --parse-conditional-restrictions option.
There are a few issues:
GeoJSON file is not really optional. It is required indirectly though, by presence of some intermediate file, which is required by default now.
AFAICT, use of the suggested option has no effect and .osrm.restrictions file is still generated that makes the contraction step require GeoJSON file with timezones.
The suggested alternative solution by removing the .osrm.restrictions file is not a solution, but a hack, especially from OSRM API usage point, not really helpful..
Apparently, --parse-conditional-restrictions controls corresponding flag in ExtractorConfig:
Yes, as explained in the bunch of inline comments to the 5dfb1cb commit, setting valid_now=0 by default does the trick. The other changes, without valid_now=0 have no effect, AFAICT.
I'm using OSRM 5.12.0
In #3841 (comment) I asked for clarification about relation between extract and contract steps, and requirement of GeoJSON file with timezones.
@karenzshea explained in #3841 (comment) the GeoJSON file is optional and it is required only if
.osrm.restrictions
file is present.Then, to disable the conditional turn restriction application by running
osrm-extract
with--parse-conditional-restrictions
option.There are a few issues:
GeoJSON file is not really optional. It is required indirectly though, by presence of some intermediate file, which is required by default now.
AFAICT, use of the suggested option has no effect and
.osrm.restrictions
file is still generated that makes the contraction step require GeoJSON file with timezones.The suggested alternative solution by removing the
.osrm.restrictions
file is not a solution, but a hack, especially from OSRM API usage point, not really helpful..Apparently,
--parse-conditional-restrictions
controls corresponding flag inExtractorConfig
:and, obviously, that does not have any effect either, as in 2.
Any chance to get that situation clarified?
The text was updated successfully, but these errors were encountered: