pgrouting | Development branch | Dataset library

There is a qgis project which has a layer that is connected to database and gets data from http://localhost:5432. When the project is opened in Qgis desktop - everything works perfect - you update data in postgres (localhost:5432) - the layer is updated on the map.

There is a QGIS server which is started inside a docker container. I place the project inside the qgis-server docker container (/etc/qgisserver), but the project can not set connection (localhost:5432) with database in another docker container.

I can not understand how to make qgis server inside container refer to its localhost:5432 but get to the host`s localhost:5432 (where postgres from another container is accessible).

I have tried to do smth like this but have not succeeded:

Hi i add a library pyodbc into my pipfile, when i run the command docker-compose up app-name and run the dockerfile config i get an error when try to install dependency from pipfile.lock my python version is 3.7.4

I work on a network dataset (with PostGIS extension, but since my current method using pgrouting is the only one I found to do what I want and it is extremely painful to run, I want to try and deal with it by attributes) such as the picture below :

Each section (letters) is a single object, and the color is the relevant attribute of the objects.

The table representing this is defined as such :

I am using this query for finding the path using postgresql , postgis, pgrouting, postgis_topology using nodejs

I downloaded Homebrew on macOS 10.12. It seemed to have downloaded successfully, but node is not downloaded through Homebrew. As I try to redownload node, I get this warning that homebrew doesn't support macOS 10.12, despite the first time success message I got that Homebrew downloaded successfully. My question is why Node isn't downloaded, and how I can get past this stage to download? The first time downloading, the Terminal got stuck at this one stage without much update for a long time so i exited and retried. The second and consequent times I tried "brew install node" have all been the same result (output below):

I'm trying to write a function that is able to find the shortest way between two points using pgr_dijkstra function. I'm following this guide. With data provided in the guide everything works fine. But when I try to apply the same steps (build a topology using pgr_createTopology and then test it with pgr_dijkstra) to another data set, pgr_dijkstra returns an empty result. I've also noticed that the guide's data set has a LineString geometry column, while I have a MultiLineString geometry column. What could be the reason?

My table's structure:

I am currently having some problems with docker and connecting a node project with Postgres when running inside it.

I have already asked a related question see link, however, I can’t wrap my head around connection issue between nodeJs and postgres.

My docker-compose file looks like:

I'm working on a routing application using OSM data in pgrouting. I'm using overpass-api to access the data from a specific bounding box. However, after downloading the data, there seem to be tag_keys missing from the data.

When inspecting the data using postgis or QGIS, certain tag_keys are there, like "highway", "oneway" or "maxpeed". However, others seem to be missing. In particular the tag keys "bicycle" (with possible values like "yes" or "no") or "access" are not included in the data. These tag keys are available on OSM online, however.

The following code is used to retrieve the data from OSM through Overpass-API and put it into PGrouting

We built a debian docker image with postgresql to run one of our service. The database is for internal container use and does not need port mapping. I believe it is installed via apt-get in the Dockerbuild file.

We stop and start this service often, and it is a performance issue that the database is slow to startup. Although empty, takes sightly over 20s to accept connection on the first time we start the docker image. The log is as follow :