Differences

This shows you the differences between two versions of the page.

--- tutorial:verification [2013/08/21 14:14]
leoame [Remove small lines]
+++ tutorial:verification [2013/10/01 17:28] (current)
leoame [Look for lines without attribution]
@@ Line 6: / Line 6: @@
 Anyway following this step-by-step verification workflow shall help you to  progressively erase the different errors to stay, at the end, with a legible project.
-<WRAP 75%><note important>Remember to frequently back up your project before modifying it. We want to avoid as many hair torn off as possible</note></WRAP>
+<WRAP 75%><note important>
+Remember to frequently back up your project before modifying it. We want to avoid as many hair torn off as possible.
+</note></WRAP>
 ===== Lines =====
@@ Line 17: / Line 20: @@
   - The line has a length, its vertices have different coordinates even if close.
-To quickly identify those irregularities we will create a query.
+To quickly identify those irregularities, create a query.
-**//Validation// -> //New query...// -> //by length//**
+**Validation -> [[man:validation#semantic_validation|New query...]] -> by length**
 {{tutorial-query-length.png?nolink}}
-You will have to edit the length you want to check, in our case: 1. Feel free to check also lines smaller than 2,3,4,5... But remember that a line with distinct vertices may be correct while the other case is allways useless.
+You will have to edit the length you want to check, in your case: 1. Feel free to check also lines smaller than 2,3,4,5... But remember that a line with distinct vertices may be correct while the other case is always useless.
 {{tutorial-query-length2.png?nolink}}
-As we can see on the status bar at the bottom of our window, our query has selected 5 features with a length smaller than 1. Before deleting them, let's have a look with the [[http://www.crealp.ch/toolmap/documentation/doku.php?id=man:funct#information_window|Information window]].
+As you can see on the status bar at the bottom of the window, the query selected 5 features with a length smaller than 1. Before deleting them, let's have a look with the Information window.
 {{tutorial-query-length3.png?nolink}}
-**//Window// -> //Information window//**
+**Window -> [[man:funct#information_window|Information window]]**
-The information window displays all the selected features and displays the data of each one. From there, we can find out their location using the option //move to// accessible via the contextual menu. I recommand you to work with a very small scale as ToolMap cannot zoom on features without geometrical meaning. This step has a real importance if checking lines bigger than 0; knowing they may not be mistakes.
+The information window displays all the selected features and displays the data of each of them. From there, you can find out their location using the option //move to// accessible via the contextual menu. I recommand you to work with a very small scale as ToolMap cannot zoom on features without geometrical meaning. This step has a real importance if checking lines bigger than 0; knowing they may not be mistakes.
-**//right-click on feature// -> //Move to//**
+**Right-click on feature -> Move to**
 {{tutorial-query-length4.png?nolink}}
-When i'm certain tha my lines are indeed errors I can delete them. I then increase the value of my query to look for bigger lines. I'll directly check for lines smaller than 5. As for that I can either create a new query or edit my actual one.
+When you are certain your lines are indeed errors, you can delete them. Then, increase the value of the query to look for bigger lines. Directly check for lines smaller than 5. As for that you can either create a new query or edit your actual one.
-**//Right-click on query// -> //Edit query SQL...//**
+**Right-click on query -> Edit query SQL...**
 {{tutorial-query-length5.png?nolink}}
-My query selected me one new feature, but while I check it, it seems to be legitimate. There is a remaining question though. Was this small line intentionnal? is it necessary? or can I avoid it by drawing the nearby lines differently?
+The query selected one new feature, but while checking it, it seems to be legitimate. There is a remaining question though. Was this small line intentionnal? is it necessary? or can you avoid it by redrawing the nearby lines differently?
 {{tutorial-query-length6.png?nolink}}
 ==== Check geometries ====
-After removing the small lines we can now check for the geometry of the other lines. We will use therfor the tool **check geometries validity**.
+After removing the small lines you can now check for the geometry of the other lines. Therfor use the tool **check geometries validity**.
-**//Validation// -> //Check geometries validity//**
+**Validation -> Check geometries validity**
-This tool will sort out every geometry with inconsistencies from your selected layer (In the table of content). As we already removed the 0 length lines, this tool will mainly search for lines overlapping themselves.
+This tool will sort out every geometry with inconsistencies from your selected layer (In the table of content). As you already removed the 0 length lines, this tool will mainly search for lines overlapping themselves.
 {{tutorial-geometry.png?nolink}}
-As you can see my line have a strange behaviour. The main cause of this mistake is an unwanted double-click while drawing the line. By deleting one of the vertices or by moving them the problem is solved.
+As you can see the line have a strange behaviour. The main cause of this mistake is an unwanted double-click while drawing the line. By deleting one of the vertices or by moving them the problem can be solved.
+You may want to directly use this tool instead of the query in the previous step ([[tutorial:verification&#remove_small_lines|remove small lines]]), but I hardly disencourage you to do that. The reason is that this tool can select overlapping lines which you just want to correct instead of deleting.
-You may want to directly use this tool instead of the query in the previous step ([[http://www.crealp.ch/toolmap/documentation/doku.php?id=tutorial:verification&#remove_small_lines|remove small lines]]), but I hardly disencourage you to do that. The reason is that this tool can select overlapping lines which you just want to correct instead of deleting.
 ==== Looking fo duplicates ====
-One more error we can easily find are the duplicated lines. With the help of a query we will sort out the lines which have identical geometry. A line shall never be drawn twice in ToolMap as we just add more object attribute to one line if she has more than one purpose.
+One more error you can easily find are the duplicated lines. With the help of a query sort out the lines which have identical geometry. A line shall never be drawn twice in ToolMap as you just add more object attributes to one line if she has more than one purpose.
-**//Validation// -> //New query...// -> //Look for duplicate//**
+**Validation -> New query... -> Look for duplicate**
 {{tutorial-duplicates.png?nolink}}
-The query selected me one line, using the [[http://www.crealp.ch/toolmap/documentation/doku.php?id=man:visualization#lines|multiple symbology]] and the **information window** I can isolate the problem. In my case there is a second line without any attribution, i'll simply erase it. But if both lines had an attribution I should have considered to give the full attribution to one of the two before cleaning the duplicate.
+The query selected one line, using the [[man:visualization#lines|multiple symbology]] and the **information window** you can isolate the problem. In this case there is a second line without any attribution, simply erase it. But if both lines had an attribution you should have considered to give the full attribution to one of the two before cleaning the duplicate.
 {{tutorial-duplicates2.png?nolink}}
@@ Line 78: / Line 81: @@
 ==== Look for lines without attribution ====
-Well this case is, I'm sure, kind of obvious for everybody but a line without attribution in ToolMap is more than useless. The query panel originaly contains 3 queries which are **lines, points and labels without attribution**. Using this query and the **multiple symbology** we will highlight every line without attribution and give them their right attribution (because I don't usually draw lines for nothing).
+Well this case is, I'm sure, kind of obvious for everybody but a line without attribution in ToolMap is more than useless. The query panel originaly contains 3 queries which are **lines, points and labels without attribution**. Using those queries and the **multiple symbology** you can highlight every line without attribution and give it its right attribution (because people don't usually draw lines for nothing).
 {{tutorial-noattrib.png?nolink}}
@@ Line 84: / Line 87: @@
 ==== Dangling nodes ====
-At this stage our lines shall be pretty much clear. What we want to avoid now are the problems related to the polygons. First of all we will check the integrity of our borders of polygon. To do that we have the tool called Dangling nodes.
+At this stage your lines shall be pretty much clear. What you want to avoid now are the problems related to the polygons. First of all, check the integrity of your borders of polygon. To do that you have the tool called Dangling nodes.
-**//Validation// -> //Dangling Nodes...//**
+**Validation -> [[man:validation#geometrical_validation|Dangling Nodes...]]**
 {{tutorial-danglingnodes.png?nolink}}
-I recommend to use the tool once for each layer instead of searching on all polygon layers. It is easier to identify the mistakes when you already know which layer lies the problem on.
+I recommend you to use the tool once for each layer instead of searching on all polygon layers. It is easier to identify the mistakes when you already know which layer lies the problem on.
 {{tutorial-danglingnodes2.png?nolink}}
@@ Line 99: / Line 102: @@
   - bad snapping: The vertices are not snapped.\\ {{tutorial-danglingnodes4.png?nolink}}
-The solutions are then simple. For a missing attribution we attribute the line, for a bad snapping we modify the line with a big enough snapping radius.
+The solutions are then simple. For a missing attribution, attribute the line; for a bad snapping, modify the line with a big enough snapping radius.
 ==== Attribution ====
-This is the most simple yet harder part to check. The only way for you to control if all your attributions are correctly made before exporting is with the **multiple symbology**. I can only recommand you to check every layer individually by hiding the other lines and search for a missing structure.
+This is the most simple yet harder part to check. The only way for you to control if all your attributions are correctly made before exporting is with the **multiple symbology**. I can only recommand you to check every layer individually by hiding the other lines and search for a forgotten attribution.
 ===== Labels =====
-Even if labels, like points, have little chance (no chance at all) to have geometrical errors, we make use of them to build the polygons. It is also important to verify them.
+Even if labels, like points, have little chance (no chance at all) to have geometrical errors, ToolMap makes use of them to build the polygons. It is also important to verify them.
 ==== Look for labels without attribution ====
-A label without attribution means a polygon without attribution. Using the query **Labels without attribution** and the **multiple symbology** we can highlight the labels which are not attributed.
+A label without attribution means a polygon without attribution. Using the query **Labels without attribution** and the **multiple symbology** you can highlight the labels which are not attributed.
 {{tutorial-labels-noattrib.png?nolink}}
-We can then correctly assign them their objects/attributes.
+You can then correctly assign them their objects/attributes.
 ==== Look for missing/additionnal labels ====
-Depending on the complexity of your map, you may forget to draw a label or you may draw two or more labels in the same polygon. To check those mistakes we will use the **redactor mode**. The **redactor mode** allows you to export a specific layer and directly reimport it into toolmap as a support theme.
+Depending on the complexity of your map, you may forget to draw a label or you may draw two or more labels in the same polygon. To check those mistakes, use the **redactor mode**. The **redactor mode** allows you to export a specific layer and directly reimport it into ToolMap as a support theme.
-I recommand to create a special export folder for this operation as you will most likely export a large quantity of the same layers.
+I recommand you to create a special export folder for this operation as you will most likely export more than once the same layers.
-**//Project// -> //Export layer...//**
+**Project -> [[man:validation#redactor_mode|Export layer...]]**
 {{tutorial-creator.png?nolink}}
-The layer will now be imported in ToolMap as a shapefile. It allows us to use the **multiple symbology** and to classify the polygons by **number of labels**.
+The layer will now be imported in ToolMap as a shapefile. It allows you to use the **multiple symbology** and to classify the polygons by **number of labels**.
 {{tutorial-creator2.png?nolink}}
-By using the **multiple symbology** on the labels related to our layer as well, we have a clear view of the different polygons created.
+By using the **multiple symbology** on the labels related to your layer as well, you can have a clear view of the different polygons created.
 {{tutorial-creator3.png?nolink}}
-I can now clearly see that I have a polygon with two labels. Obviously I can identify the missing labels if a polygon is not drawn. The goal is now to correct those mistakes and directly reimport the layer. Due to the option **replace existing layer**, the settings of your symbology will remain, but your layer will be updated according to your modifications.
+You can now clearly see that there is a polygon with two labels. Obviously you can identify the missing labels if a polygon is not drawn. The goal is now to correct those mistakes and directly reimport the layer. Due to the option **replace existing layer**, the settings of your symbology will remain, but your layer will be updated according to your modifications.
 {{tutorial-creator4.png?nolink}}

ToolMap Wiki

Site Tools

User Tools

Differences

Page Tools