21.1 Results For An Overview of The Interface: Twentyone
21.1 Results For An Overview of The Interface: Twentyone
TWENTYONE
ANSWER SHEET
Refer back to the image showing the interface layout and check that you remember the names and functions of the
screen elements.
Back to text
1. Save as
2. Zoom to layer
3. Invert selection
4. Rendering on/off
5. Measure line
Back to text
21.2.1 Preparation
In the main area of the dialog you should see many shapes with different colors. Each shape belongs to a layer you
can identify by its color in the left panel (your colors may be different from the ones below):
647
QGIS Training Manual
Back to text
21.3.1 Colors
• Verify that the colors are changing as you expect them to change.
Note: If you want to work on only one layer at a time and don’t want the other layers to distract you, you can hide a
layer by clicking in the checkbox next to its name in the layers list. If the box is blank, then the layer is hidden.
Back to text
Back to text
Customize your buildings layer as you like, but remember that it has to be easy to tell different layers apart on the
map.
Here’s an example:
Back to text
The lowest symbol layer is a broad, solid gray line. On top of it there is a slightly thinner solid yellow line and finally
another thinner solid black line.
If your symbol layers resemble the above but you’re not getting the result you want:
1. Check that your symbol levels look something like this:
Back to text
Back to text
• Move the new symbol at the bottom of the list clicking the button.
• Choose a good color to fill the water polygons.
• Click on Marker of the Geometry generator symbology and change the circle with another shape as your wish.
• Try experimenting other options to get more useful results.
Back to text
2. Right-click and choose Open Attribute Table, or press the button on the Attributes Toolbar.
3. Count the number of columns.
Tip: A quicker approach could be to double-click the rivers layer, open the Layer properties ► Fields tab,
where you will find a numbered list of the table’s fields.
• Information about towns is available in the places layer. Open its attribute table as you did with the rivers layer:
there are two features whose place attribute is set to town: Swellendam and Buffeljagsrivier. You can add
comment on other fields from these two records, if you like.
• The name field is the most useful to show as labels. This is because all its values are unique for every object
and are very unlikely to contain NULL values. If your data contains some NULL values, do not worry as long
as most of your places have names.
Back to text
Your map should now show the marker points and the labels should be offset by 2mm. The style of the markers and
labels should allow both to be clearly visible on the map:
Back to text
• Enter a space in this field and click Apply to achieve the same effect. In our case, some of the place names
are very long, resulting in names with multiple lines which is not very user friendly. You might find this setting
to be more appropriate for your map.
Back to text
1. Still in edit mode, set the FONT_SIZE values to whatever you prefer. The example uses 16 for towns, 14 for
suburbs, 12 for localities, and 10 for hamlets.
2. Remember to save changes and exit edit mode
3. Return to the Text formatting options for the places layer and select FONT_SIZE in the Attribute field of
the font size data defined override dropdown:
Back to text
The settings you used might not be the same, but with the values Classes = 6 and Mode = Natural Breaks (Jenks) (and
using the same colors, of course), the map will look like this:
Back to text
21.8.1 Digitizing
The symbology doesn’t matter, but the results should look more or less like this:
Back to text
The exact shape doesn’t matter, but you should be getting a hole in the middle of your feature, like this one:
• Undo your edit before continuing with the exercise for the next tool.
Back to text
• Undo your edit before continuing with the exercise for the next tool.
Back to text
• Use the Merge Selected Features tool, making sure to first select both of the polygons you wish to merge.
• Use the feature with the OGC_FID of 1 as the source of your attributes (click on its entry in the dialog, then
click the Take attributes from selected feature button):
Note: If you’re using a different dataset, it is highly likely that your original polygon’s OGC_FID will not be 1. Just
choose the feature which has an OGC_FID.
Note: Using the Merge Attributes of Selected Features tool will keep the geometries distinct, but give them the same
attributes.
Back to text
21.8.5 Forms
For the TYPE, there is obviously a limited amount of types that a road can be, and if you check the attribute table for
this layer, you’ll see that they are predefined.
• Set the widget to Value Map and click Load Data from Layer.
• Select roads in the Label dropdown and highway for both the Value and Description options:
Back to text
To this:
The first image shows the buffer with the Segments to approximate value set to 5 and the second shows the value set
to 20. In our example, the difference is subtle, but you can see that the buffer’s edges are smoother with the higher
value.
Back to text
Your map should now show only those buildings which are within 50m of a road, 1km of a school and 500m of a
restaurant:
Back to text
Open Network Analysis ► Shortest Path (Point to Point) and fill the dialog as:
Back to text
Your result:
Back to text
• For the 5 degree version, replace the 2 in the expression and file name with 5.
Your results:
• 2 degrees:
• 5 degrees:
Back to text
1. Open the Query Builder by right-clicking on the all_terrain layer in the Layers panel, and selecting the Properties
► Source tab.
2. Then build the query "suitable" = 1.
3. Click OK to filter out all the polygons where this condition isn’t met.
When viewed over the original raster, the areas should overlap perfectly:
4. You can save this layer by right-clicking on the all_terrain layer in the Layers panel and choosing Save As…,
then continue as per the instructions.
Back to text
You may notice that some of the buildings in your new_solution layer have been “sliced” by the Intersection tool.
This shows that only part of the building - and therefore only part of the property - lies on suitable terrain. We can
therefore sensibly eliminate those buildings from our dataset.
Back to text
If it is greater than 100 meters in radius, then subtracting 100 meters from its size (from all directions) will result in
a part of it being left in the middle.
Therefore, you can run an interior buffer of 100 meters on your existing suitable_terrain vector layer. In the output
of the buffer function, whatever remains of the original layer will represent areas where there is suitable terrain for
100 meters beyond.
To demonstrate:
1. Go to Vector ► Geoprocessing Tools ► Buffer(s) to open the Buffer(s) dialog.
2. Set it up like this:
3. Use the suitable_terrain layer with 10 segments and a buffer distance of -100. (The distance is automatically
in meters because your map is using a projected CRS.)
4. Save the output in exercise_data/residential_development/ as
suitable_terrain_continuous100m.shp.
5. If necessary, move the new layer above your original suitable_terrain layer.
Your results will look like something like this:
6. Now use the Select by Location tool (Vector ► Research Tools ► Select by location).
7. Set up like this:
The yellow buildings are selected. Although some of the buildings fall partly outside the new suit-
able_terrain_continuous100m layer, they lie well within the original suitable_terrain layer and therefore meet
all of our requirements.
9. Save the selection under exercise_data/residential_development/ as final_answer.
shp.
Back to text
Your map should look like this (you may need to re-order the layers):
Back to text
• Use the same approach as before to add the new server and the appropriate layer as hosted on that server:
• If you zoom into the Swellendam area, you’ll notice that this dataset has a low resolution:
Therefore, it’s better not to use this data for the current map. The Blue Marble data is more suitable at global or
national scales.
Back to text
You may notice that many WMS servers are not always available. Sometimes this is temporary, sometimes it is
permanent. An example of a WMS server that worked at the time of writing is the World Mineral Deposits WMS at
http://apps1.gdr.nrcan.gc.ca/cgi-bin/worldmin_en-ca_ows. It does not require fees or have access constraints, and it
is global. Therefore, it does satisfy the requirements. Keep in mind, however, that this is merely an example. There
are many other WMS servers to choose from.
Back to text
You can add layers (both vector and raster) into a GRASS Mapset by drag and drop them in the Browser (see Follow
Along: Load data using the QGIS Browser) or by using the v.in.gdal.qgis for vector and r.in.gdal.qgis
for raster layers.
Back to text
To discover the maximum value of the raster run the r.info tool: in the console you will see that the maximum
value is 1699.
You are now ready to write the rules. Open a text editor and add the following rules:
0 thru 1000 = 1
1000 thru 1400 = 2
1400 thru 1699 = 3
save the file as a my_rules.txt file and close the text editor.
Run the r.reclass tool, choose the g_dem layer and load the file containing the rules you just have saved.
Click on Run and then on View Output. You can change the colors and the final result should look like the following
picture:
Back to text
For our theoretical address table, we might want to store the following properties:
House Number
Street Name
Suburb Name
City Name
Postcode
Country
When creating the table to represent an address object, we would create columns to represent each of these properties
and we would name them with SQL-compliant and possibly shortened names:
house_number
street_name
suburb
city
postcode
country
Back to text
The major problem with the people table is that there is a single address field which contains a person’s entire address.
Thinking about our theoretical address table earlier in this lesson, we know that an address is made up of many
different properties. By storing all these properties in one field, we make it much harder to update and query our
data. We therefore need to split the address field into the various properties. This would give us a table which has the
following structure:
Note: In the next section, you will learn about Foreign Key relationships which could be used in this example to
further improve our database’s structure.
Back to text
The street_id column represents a ‘one to many’ relationship between the people object and the related street
object, which is in the streets table.
One way to further normalise the table is to split the name field into first_name and last_name:
We can also create separate tables for the town or city name and country, linking them to our people table via ‘one to
many’ relationships:
Back to text
The schema for the table (enter \d people) looks like this:
Table "public.people"
Note: For illustration purposes, we have purposely omitted the fkey constraint.
Back to text
The reason the DROP command would not work in this case is because the people table has a Foreign Key constraint
to the streets table. This means that dropping (or deleting) the streets table would leave the people table with references
to non-existent streets data.
Note: It is possible to ‘force’ the streets table to be deleted by using the CASCADE command, but this would also
delete the people and any other table which had a relationship to the streets table. Use with caution!
Back to text
The SQL command you should use looks like this (you can replace the street name with a name of your choice):
Back to text
If you look at the streets table again (using a select statement as before), you’ll see that the id for the Main Road
entry is 2.
That’s why we could merely enter the number 2 above. Even though we’re not seeing Main Road written out fully
in the entry above, the database will be able to associate that with the street_id value of 2.
Note: If you have already added a new street object, you might find that the new Main Road has an ID of 3
not 2.
Back to text
Result:
count | name
------+-------------
1 | Low Street
2 | High street
1 | Main Road
(3 rows)
Note: You will notice that we have prefixed field names with table names (e.g. people.name and streets.name). This
needs to be done whenever the field name is ambiguous (i.e. not unique across all tables in the database).
Back to text
The units being used by the example query are degrees, because the CRS that the layer is using is WGS 84. This
is a Geographic CRS, which means that its units are in degrees. A Projected CRS, like the UTM projections, is in
meters.
Remember that when you write a query, you need to know which units the layer’s CRS is in. This will allow you to
write a query that will return the results that you expect.
Back to text
Back to text
Back to text
then it means that while experimenting with creating polygons for the cities table, you must have deleted some of
them and started over. Just check the entries in your cities table and use any id which exists.
Back to text
Back to text
Back to text
select people.name,
streets.name as street_name,
st_astext(people.the_geom) as geometry
from streets, people
where people.street_id=streets.id;
Result:
As you can see, our constraint allows nulls to be added into the database.
Back to text