tobi238 / express-geoapi

NodeJS Server for Geospatial Data Processing

NodeJS Server for Geospatial Data Processing

Setup

1. Install dependencies npm install

2. Setup PostgreSQL DB:

   1. Install Docker if you don't already have it.
   2. Create and start a new Docker PostgreSQL Container: npm db:create_container
   3. Seed the DB: npm db:seed

3. start development server:

   • create and configure .env file (see .env.example)
   • start the server: npm run dev

4. start production server: npm run start

Usage

1. Create new user: make a post request to /signup with a json body like { "username":"abc", "password": "def"}

2. Sign in: make a post request to /signin with a json body like { "username":"abc", "password": "def"}.

   • If the credential are valid the server responds a json with a api token:

   {
     "success": true,
     "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJ1c2VybmFtZSI6InRlc3QiLCJwbGFuIjoiZnJlZSIsImlzcyI6ImxvY2FsaG9zdDozMDAwIiwiaWF0IjoxNTE4OTgxMTk5LCJleHAiOjE1MTg5ODQ3OTl9.882VgD1UdebAQONZZbouYUqHLl_mWE4v3ABlyWZrRro"
   }

   • Use this token in the Header of all API requests: Authorization: Bearer <your_token>

3. Access API Endpoint of your choice ✌

express-geoapi's Issues

add rounting services via open source routing machine

the service can be used with docker (see https://hub.docker.com/r/osrm/osrm-backend/). build routing data from osm data and start server in a batch file:

:: prepare osm downloaded data:
:: run commands in same folder as karlsruhe-regbez-latest.osm.pbf
docker run -t -v C:/docker/osrm/data:/data osrm/osrm-backend osrm-extract -p /opt/car.lua /data/karlsruhe-regbez-latest.osm.pbf
docker run -t -v C:/docker/osrm/data:/data osrm/osrm-backend osrm-partition /data/karlsruhe-regbez-latest.osrm
docker run -t -v C:/docker/osrm/data:/data osrm/osrm-backend osrm-customize /data/karlsruhe-regbez-latest.osrm

:: start server from same folder
docker run -t -i -p 5000:5000 -v C:/docker/osrm/data/:/data osrm/osrm-backend osrm-routed --algorithm mld /data/karlsruhe-regbez-latest.osrm

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.