Graph Directory Contains Only gh.lock When Using Own OSM File

[Josh_Collins]

Thanks for writing back. I’ve managed to resolve the issue now. I was actually just about to close the question on here when I saw your response.

I found out why there was a problem:

• typos in my own script;
• config file still pointing to Germany;
• I didn’t realise I needed to wait.

Once the container has been built and put up, I didn’t realise the software was still building the graphs themselves. The documentation doesn’t make this clear and the script literally prints FINISHED at one point. I found a good explaination of the situation here in the end:

When the graph is generate and first run problem

Hi I use docker compose with an osm from http://geofabrik.de/ and I have several questions: First I wonder when the graph is build, during the image generation or during the first run of the container? Second, I can’t find where the graph folder is locate on the installation, do you have any idea? Third, at the end of the creation of the image, I have this on the log, this can be a problem or not: Successfully tagged docker_ors-app:latest WARNING: Image for service ors-app was built because…

Large PBF, how long to generate graphs/see progress

I am using a very large PBF extract, and starting openrouteservice. It starts and goes into a NOT READY state as it builds the graphs… Which is fine, but I see absolutely no status on where it is in that process. It creates directories and puts gh.lock files in them (car and hgv)… but I never see any output being create there… so how do I get any sort of status on the state of the graph builds? Is this normal?

I wouldn’t mind drafting something for the docs to more clearly break down the set up process. It seems to be a common theme for questions on here. Would someone be willing to proof read it if I put something across?