mbasa/pgrserver

Routing service that uses pgRouting topologies and is loaded to a JGraphT graph for fast searches even with very dense networks such as OpenStreetMap (OSM) dataset.

pgrserver's Issues

docker & docker-compose

I think it'd make a lot of sense for this repo to have a docker setup. A lot of things could be automated this way, like spinning up a PostGIS/Tomcat instance, creating graphs, easily running on major OSs etc. Would really lower the barrier for getting started.

I can help out a little early next year if you want. Some suggestions:

• ORS has an okish docker setup: https://github.com/GIScience/openrouteservice/blob/master/Dockerfile
• PostGIS best over Kartoza's image IMO (comes with pgrouting3 by default): https://github.com/kartoza/docker-postgis
• probably it makes sense to contain tomcat within the image of this repo similar to ORS

Looking forward to give this a try!

First feedback

I tried it now for a graph spanning all of Austria:

1. generate the topology with osm2po: java -Xmx2g -jar osm2po-core-5.3.2-signed.jar cmd=c prefix=austria austria-latest.osm.pbf
2. load the resulting sql: psql -U postgres -W -h localhost -d gis_test -f austria/austria_2po_4pgr.sql
3. create the view following the README: CREATE VIEW pgrserver AS SELECT id,source,target,cost,geom_way AS geom FROM austria_2po_4pgr ;

That leads to:

• 1.7 Mio (bidirectional) edges
• ~ 2 GB RAM base graph
• ~ 40 seconds to load the graph from PG

That I'm actually quite happy with, good performance, bit too much RAM maybe.

When I try to query even short distances I get an empty response (tried Dijkstra, AStar, CH). If I actually try from on end of Austria to the other (Vienna -> Liechtenstein), CH is running for 10 minutes at > 7 GB RAM on 8 threads before I canceled.

However, small extracts (I tried Sydney real quick) with the same workflow works well!

Did you ever try a bigger graph?

Add network changes to the network

Hi,

thanks a lot for this interesting project. I was wondering if it would be very difficult to implement a user-based network change capability into the project.

e.g. imagine one user would like to add a new network link to the graph and wants to perform routing operations with this changed graph. However, at the same time other users which are using the same graph should not be affected by this network change. Instead, their routing operation should use no changes or their own changes.

I was wondering if there is any direction you could point me in. As we are currently using a pgRouting for this but we would favor a solution loading the network in memory due to performance.

Cheers,

Elias

Turn restricted shortest path (TRSP)

Hi Mario,
this project looks amazing. It solves almost all of our pgr hurdles. We were just considering writing something similar to pgrServer, but now we don't have to ;). But there is one major feature missing for us and that is support for some kind of TRSP algorithm (like pgr_trsp). Do you have any plans to support TRSP algorithm?

Error while running the docker image

which building using the:
docker-compose build pgrserver
we get: ERROR: No such service: pgrserver

Then, I checked the docker-compose.yml and tried:
docker-compose build pgrServer
we get some exception: pgrServer uses an image, skipping

The issue with
docker-compose up

Pulling pgrServer (mbasa/pgrserver:latest)...
ERROR: The image for the service you're trying to recreate has been removed. If you continue, volume data could be lost. Consider backing up your data before continuing.

Continue with the new image? [yN]y
Pulling pgrServer (mbasa/pgrserver:latest)...
ERROR: pull access denied for mbasa/pgrserver, repository does not exist or may require 'docker login': denied: requested access to the resource is denied