RoadHopper is a software for simulating a vehicle to get a driving cycle (time–velocity diagram). For this, a road network based on actual maps data is constructed and a simulation is run on that network.
The maps data is taken from the OpenStreetMap project. It is processed using [GraphHopper] (http://graphhopper.com), an open source routing service for OpenStreetMap.
This project was started during my diploma thesis at the Hybrid Electric Vehicles research group of the Karlsruhe Institute of Technology. The thesis is available on the web; occasionally, it is also referenced throughout this software’s documentation.
To run RoadHopper, you need a custom fork of GraphHopper with a few adjustments necessary for RoadHopper. Also, grab an extract from OpenStreetMap from one of the download pages listed at https://wiki.openstreetmap.org/wiki/Downloading_data. You need either a .pbf or a .osm (XML) file.
Clone my GraphHopper fork and check out the correct branch:
git checkout -b roadhopper-base origin/roadhopper-base
Then, clone RoadHopper into the your GraphHopper directory
graphopper $ git clone https://github.com/andreaswolf/roadhopper
Currently, there are no scripts to run the software, so you need to configure it in your IDE. Create a run configuration with the following parameters:
- Main class:
info.andreaswolf.roadhopper.server.RoadHopperServer - VM options:
-Djetty.port=8989 -Dconfig.file=./roadhopper/application.conf -Dorientdb.config.file=./roadhopper/orientdb/orientdb-server-config.xml -DORIENTDB_HOME=./roadhopper/orientdb/ - Program arguments:
config=./config.properties - Working directory: Path to GraphHopper
Copy config-example.properties to your GraphHopper directory and name it config.properties.
What is also necessary is replacing the dependencies to the com.graphhopper.* modules by references to the modules inside
the IDE workspace.
When starting the software, GraphHopper will process the OSM file and create its internal data structure. Afterwards, head to http://localhost:8989 and select two points. Then, a simulation will run – currently, a very rough estimate. I’m working on that ;-). Afterwards, you see a t–v diagram at the bottom right.
RoadHopper logs a multitude of data during simulation runs, mainly the signal values. To get this data, use the API endpoint /roadhopper/signalvalues. The expected query string parameters are
- the simulation id as
simulation - the signal names (1..n) as
signal
An example could be /roadhopper/signalvalues?simulation=123456789&signal=v&signal=a.
The data import can be run by using a separate class
- Main class:
info.andreaswolf.roadhopper.measurements.Importer - VM options, program arguments, working directory: See above
The CSV files must be placed in the folder measurements/ in the configured working directory. To adjust the folder name,
set the property measurements.path in your program options (or config.properties).
RoadHopper comes with a Maven configuration for building it into a standalone package that can be run with just Java installed.
To build the distribution, run
mvn dependency:copy-dependencies install package
tbd.
tbd.
If you have any feature requests or need customization of RoadHopper to your use case, feel free to contact me at dev (at) a-w dot io.
This software is licensed under the MIT license. See the LICENSE file for more information.