Openrouteservice is a online route planning application that is based on open source software, open data and open standards.
The openrouteservice client requires nodejs and a valid Api-Key to access the openrouteservice API. Also make sure that git is installed.
If you encounter any permission issues during the installation:
- on Linux: try running npm-commands with
sudo:
e.g.:
sudo npm install- on Windows(GitBash recommended): try running npm-commands with the
--no-optionalflag:
e.g.:
npm install --no-optional- Download openrouteservice repository:
# clone repository from github
git clone https://github.com/GIScience/openrouteservice-app.git
# switch to repository folder
cd openrouteservice-app- Install dependencies:
# install all modules listed as dependencies in package.json
npm install
# install dependencies listed in bower.json
node_modules/bower/bin/bower install- Install required modules for slider layout:
(This step is for layout purposes only. If you want to skip it remove grunt:sliderMakeCss from the task queue in the renamed Gruntfile.js [see next step])
# Switch to bower_components/angular folder:
cd bower_components/angularjs-slider
# install all modules listed as dependencies in package.json
npm install
# switch back to openrouteservice-app folder:
cd ../..- Initiate default files:
# Copy `Gruntfile.default.js` to `Gruntfile.js`
cp Gruntfile.default.js Gruntfile.js
# Copy `weathercheck.default.txt` to `weathercheck.txt`.
cp app/weathercheck.default.txt app/weathercheck.txt- Replace weathercheck.txt content with your Api-Key:
# Finally open `app/weathercheck.txt` in your favorite text editor and replace the content with your Token.
# e.g.:
vim app/weathercheck.txtFor the standard openrouteservice version do:
grunt ors
If you want to use the openrouteservice client with a local backend version of openrouteservice you have to adjust the endpoint paths to the backend war version you are using in Grunfile.js.
Afterwards do:
grunt ors_local
If you would like to contribute, please note that we are using a branching model to structure our git workflow and are following commit message guidelines.
For minor bugfixes use the development branch:
git checkout development
For new features, please create a new branch:
git checkout -b feature_branch
In every case do a pull request to our development branch. Be sure to pull the latest changes beforehand and fix any emerging conflicts.
To enable console output information and logging for bugfixing and feature development do:
grunt dev
Help us to provide the openrouteservice in your language by translating some simple keywords!
In this spreadsheet you can add a column for your language or check the already added words if they are correctly translated. Our service will be updated regularly with the latest language versions.
If there are further questions, please let us know!
(The MIT License)
Copyright (c) 2017 GIScience Research Group, Heidelberg University.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.