We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The other osrm-* programs has a nice usage info screen - but osrm-datastore lacks this
[info] osrm-extract <input.osm/.osm.bz2/.osm.pbf> [options]:
Options: -v [ --version ] Show version -h [ --help ] Show this help message -c [ --config ] arg (="extractor.ini") Path to a configuration file.
Configuration: -p [ --profile ] arg (="profile.lua") Path to LUA routing profile -t [ --threads ] arg (=7) Number of threads to use
The text was updated successfully, but these errors were encountered:
The datastore exposes visible options if you request help. Those consist of generic and config options that are defined here.
but osrm-datastore lacks this
You then go on posting the extract help output --- is this by accident?
Sorry, something went wrong.
my bad, -h works - but whereas the other executables also show the help screen if called without parameters, datastore just fails with an exception
and no - the output was no accident - it was just to show your other executables react on being called with out parameters.
Right, datastore should print the help in case no arguments are given and no ini file is available.
A fix will be merged in with 4afa69d
No branches or pull requests
The other osrm-* programs has a nice usage info screen - but osrm-datastore lacks this
osrm-extract
[info] osrm-extract <input.osm/.osm.bz2/.osm.pbf> [options]:
Options:
-v [ --version ] Show version
-h [ --help ] Show this help message
-c [ --config ] arg (="extractor.ini")
Path to a configuration file.
Configuration:
-p [ --profile ] arg (="profile.lua") Path to LUA routing profile
-t [ --threads ] arg (=7) Number of threads to use
The text was updated successfully, but these errors were encountered: