Basic Network Visualization and Routing (QGIS3)

Creating, visualizing, and managing networks is an important part of GIS. Many types of physical infrastructure such as roads, railways, utilities can be modeled as networks with lines and nodes - with properties attached to them. In this tutorial, we will learn how road networks are commonly modeled and apply some styling techniques to visualize the routing properties. We will also use QGIS3’s built-in tools for network analysis that to find the shortest path between 2 points along with the network.

Overview of the task

We will take a layer of roadway block for Washington DC, visualize the connectivity and build a network to find shortest path between any 2 points in the city.

Other skills you will learn

  • How to use data defined overrides to align an arrow symbol based on line direction.

Get the data

District of Columbia government freely shares hundreds of datasets on the Open Data Catalog.

Download the Roadway Block shared by DCGISopendata data as a shapefile.


For convenience, you may directly download a copy of the datasets from the links below:

Data Source: [DCOPENDATA]


  1. Locate the downloaded file in the Browser panel. Expand it and drag the Roadway_Block.shp file to the canvas.

  1. You will see a new line layer called Roadway_Block added to the Layers panel. This layer represents each road in Washington DC. Select the Identify tool in the Attributes Toolbar. Click on any road segment to see what attributes are attached to it. There are standard attributes like Route-name, Road-type etc. there is an attribute called SUMMARYDIR. This is an important attribute for routing as it specifies whether the segment is two-way or one-way. It contains 4 different values. BD (Both Directions) for two-way streets. OB (Out Bound) for one-way streets where the traffic is allowed in the direction of the line (start-point to end-point) and IB (In Bound) for one-way streets where the traffic flows in the opposite direction of the line. There is also ?? value where we will assume two-way traffic. We will now use the information in that attribute to display an arrow on one-way streets.

  1. Click the Open the layer Styling Panel button in the Layers panel. Select the Rule-based renderer from the drop-down menu.

  1. We will create a new style with a filter for only the one-way roads. Click the Add rule + button.

  1. In the Edit rule dialog, click the Expression button.

  1. In the Expression string builder dialog, expand the Fields and Values section in the middle-panel. Select the SUMMARYDIR attribute and click All Unique in the right-hand panel. The 4 values that we discussed earlier will appear. Having these values here as a reference helps when building the expression. Also, you can double-click on any value to add them to the expression.

  1. The goal is to create an expression that selects all one-way streets. Enter the following expression and click OK.

"SUMMARYDIR" in ('IB', 'OB')
  1. Next, change the Symbol layer type to Marker line.

  1. Select on center point under Marker placement.

  1. Click on the Simple marker symbol. Scroll down and pick the filled_arrowhead marker. You will see that the arrow-like symbol now appears on the one-way streets. But all of them are pointing in a single direction, whereas we know that our filter contains roads in multiple directions. We can further refine the symbols with a data-defined override for the Rotation value.

  1. Click the Data defined override button next to Rotation.

  1. We can put a conditional expression that returns different rotation values depending on the one-way direction. A 180° degree rotation for the road with opposite direction will make the direction perfect, In this, we will make the Roads with IB attribute rotate 180° hence all roads will have the correct traffic flow direction. Enter the following expression and click OK.

if( "SUMMARYDIR" = 'IB', 180, 0)
  1. Now you will see the arrow-heads aligned to the correct road direction. To keep the style uncluttered, we are choosing to display arrows only on one-way streets. Unlabeled streets are assumed to be two-way. Now that we have the network styled correctly, we can do some analysis. Go to Processing ‣ Toolbox.

  1. Search for and locate the Network analysis ‣ Shortest path (point to point) algorithm. Double-click to launch it.

  1. In the Shortest Path (Point to Point) dialog, select Roadway_Block as the Vector layer representing network. Keep the Path type to calculate as Shortest. Next, we need to pick a start and endpoint. You can click the button and click on any point on the network in the canvas. If you want to replicate the results in this tutorial, you can enter -76.99730092166396,38.887624846748984 as the Start point and -76.99154831062152,38.89151000569929 as the End point. Expand the Advanced parameter section. Choose SUMMARYDIR as the Direction field. You must be familiar with the one-way direction values for the forward and backward traffic flow. Enter OB as the Value for the forward direction and IB as the Value for the backward direction. Keep other options to their default values and click Run.

  1. The algorithm will use the geometry of the layer and provided parameters to build a network graph. This graph is then used to find the shortest path between the start and endpoints. Once the algorithm finishes, you will see a new layer Shortest path added to the Layers panel that shows the shortest path between start and endpoints.

  1. You will see that there are many possible paths between start and endpoints. But given the constraints of the network - such as one-ways, the result is the shortest possible path. It is always a good idea to validate your analysis and assumptions. One easy way to validate it is to use a third-party mapping service to see if their results match with the ones we derived. Here is the shortest path suggested by Google Maps between the same start and endpoints. As you can see the recommended shortest route matches exactly with our results - validating our analysis.


If you want to give feedback or share your experience with this tutorial, please comment below. (requires GitHub account)