broken API / graphs dir not working

[sbma44]

Thanks so much for this project. I hit a few hiccups following the README, but nothing insurmountable. At the end of it I got a working OTP web UI! Nice.

But I'm attempting to play around with transit isochrones and running into problems with API calls. Sample call:

http://localhost:8080/otp/routers/default/isochrone?fromPlace=29.7524,-95.347&mode=TRANSIT&date=08-23-2020&time=4:30pm&maxWalkDistance=500&cutoffSec=1800

results in output like this.

A few things to note:

• I'm using default because the graph appears to build with an empty string as its name. This is confirmed when visiting http://localhost:8080/otp/routers/, which includes <routerId></routerId>.
• using a router ID of default generates some results, but no transit--all the isochrones I get back are walking-only. If I set the mode to TRANSIT only (as above) I get back empty results.
• the graphs directory in the image doesn't look like it's getting populated properly:

/var/otp/graphs # find .
.
./houston-gtfs.zip
./houston.osm.pbf
./otp.sh
./graphs
./Graph.obj
./houston_extract.sh

I'll go ahead and build my own Docker image, but I figured I might as well file a bug report in case anyone else is trying to get the API going with this one.

[sbma44]

fix for this is simple: make a subdirectory with your desired router name, put the files in there, and invoke build like so:

mkdir houston
cd houston
cp /path/to/houston-gtfs.zip .
cp /path/to/houston-osm.pbf .
cd ..
docker run   -v $PWD:/graphs  -e JAVA_OPTIONS=-Xmx4G   urbica/otp --build /graphs/houston