Then: java -Ddw.graphhopper.datareader.file=kazakhstan-latest.osm.pbf -jar web-bundle/target/*.jar server config-example.yml
or java -jar web-bundle/target/graphhopper-web-bundle-3.0-SNAPSHOT.jar server config-example.yml
and I got:
no main manifest attribute, in web-bundle/target/graphhopper-web-bundle-3.0-SNAPSHOT.jar
I start the map matching server with the main web server binary
./graphhopper.sh -a web -i map.pbf
The matching funtionality seems to be present as documented in the map-matching page.
The integration of the map-matching from it’s own repository to the main repository seems pretty recent, it’s probably due to that that either the documentation or the .jar file need some fixing.
Previously the map-matching was available also as a separate CLI tool in addition to the GraphHopper server application. Do you know are there plans to bring it back to working condition in the main GraphHopper repository or will it be deprecated?
java -jar web-bundle/target/graphhopper-web-3.0-SNAPSHOT.jar match
was not included in the main application web/target/graphhopper-web-3.0-SNAPSHOT.jar, and was only available in the web-bundle/target/graphhopper-web-3.0-SNAPSHOT.jar which no longer worked. Thus my confusion…
I got the same error message as the original poster.
namely
miikama:graphhopper$ java -jar web-bundle/target/graphhopper-web-bundle-3.0-SNAPSHOT.jar --help
no main manifest attribute, in web-bundle/target/graphhopper-web-bundle-3.0-SNAPSHOT.jar
But the jar
miikama:graphhopper$ java -jar web/target/graphhopper-web-3.0-SNAPSHOT.jar --help
usage: java -jar graphhopper-web-3.0-SNAPSHOT.jar
[-h] [-v] {server,check,import,match} ...
positional arguments:
{server,check,import,match}
available commands
named arguments:
-h, --help show this help message and exit
-v, --version show the application version and exi