Project

General

Profile

Wiki » History » Version 269

Giulio Di Anastasio, 05/05/2021 17:56

1 1 Philippe May
h1. %{color:BLUE}  Wiki%
2 227 Giulio Di Anastasio
3 232 Giulio Di Anastasio
h1. [[CSR Geomatics Team]]
4 231 Giulio Di Anastasio
5 229 Giulio Di Anastasio
h1. [[Collaborations]]
6 229 Giulio Di Anastasio
7 240 Giulio Di Anastasio
h1. [[Data Analysis]]
8 234 Giulio Di Anastasio
9 241 Giulio Di Anastasio
h1. [[CSR Geomatics Server Setup]]
10 234 Giulio Di Anastasio
11 245 Giulio Di Anastasio
h1. [[Database Backup and Restoration]]
12 243 Giulio Di Anastasio
13 243 Giulio Di Anastasio
h1. [[CAD to GIS Workflow]] %{color:RED}  - TO BE UPDATED%
14 248 Giulio Di Anastasio
15 246 Giulio Di Anastasio
h1. [[GIS Conventions]]
16 246 Giulio Di Anastasio
 
17 252 Giulio Di Anastasio
h1. [[Working with Gisaf]]
18 96 Selvarani C
19 92 Selvarani C
h1. [[Gisaf Workflow]]
20 252 Giulio Di Anastasio
21 255 Giulio Di Anastasio
h1. [[Categories - Survey codes]]
22 255 Giulio Di Anastasio
23 256 Giulio Di Anastasio
h1. [[GIS to CAD Workflow]] %{color:RED}  - TO BE UPDATED%
24 94 Selvarani C
25 257 Giulio Di Anastasio
h1. [[Weather Station]]
26 142 Selvarani C
27 259 Giulio Di Anastasio
h1. [[GDAL - Useful Tips]]
28 5 Philippe May
29 262 Giulio Di Anastasio
h1. [[Gisaf - Auxiliary Data (non-geographical data)]]
30 143 Selvarani C
31 264 Giulio Di Anastasio
h1. [[QGis - Useful Tips]]
32 264 Giulio Di Anastasio
33 266 Giulio Di Anastasio
h1. [[AutoCAD Civil 3D - Useful Tips]]
34 266 Giulio Di Anastasio
35 268 Giulio Di Anastasio
h1. [[Wells documentation]]
36 8 Philippe May
37 262 Giulio Di Anastasio
38 268 Giulio Di Anastasio
39 107 Selvarani C
h1. Plan
40 107 Selvarani C
41 107 Selvarani C
Some interesting projects that might be integrated:
42 107 Selvarani C
43 107 Selvarani C
* https://github.com/Oslandia/albion : Build 3D geological model from wells information
44 8 Philippe May
45 8 Philippe May
46 156 Selvarani C
47 16 Philippe May
48 109 Selvarani C
h1. Links
49 109 Selvarani C
50 109 Selvarani C
h2. Water management
51 109 Selvarani C
52 109 Selvarani C
h3. Modflow
53 109 Selvarani C
54 109 Selvarani C
* https://water.usgs.gov/ogw/modflow/
55 109 Selvarani C
56 109 Selvarani C
The reference software for underground water modelling and simulation.
57 109 Selvarani C
In conjunction with flopy (https://water.usgs.gov/ogw/flopy/) and Jupyter (https://jupyter.org/), it provides a _relatively easy_ to use interface.
58 109 Selvarani C
59 109 Selvarani C
60 109 Selvarani C
h3. Freewat
61 109 Selvarani C
62 109 Selvarani C
* http://www.freewat.eu/project
63 109 Selvarani C
64 109 Selvarani C
This project is partly based on modflow, and integrates with QGis.
65 109 Selvarani C
66 109 Selvarani C
h2. QGIS
67 109 Selvarani C
68 109 Selvarani C
* https://www.qgis.org/en/site/
69 109 Selvarani C
70 109 Selvarani C
* Tools for Geology
71 109 Selvarani C
Construction of geological cross sections in QGIS - http://www.geokincern.com/?p=1452
72 109 Selvarani C
73 109 Selvarani C
74 109 Selvarani C
h2. Autocad
75 109 Selvarani C
76 109 Selvarani C
* Overview of Converting Geospatial Data to Drawing Objects: 
77 109 Selvarani C
http://docs.autodesk.com/CIV3D/2013/ENU/index.html?url=filesMAPC3D/GUID-C38FD485-3CC2-4B52-8264-0D8C0F45422B.htm,topicNumber=MAPC3Dd30e41809
78 109 Selvarani C
79 109 Selvarani C
* CAD-DB connection:
80 109 Selvarani C
https://knowledge.autodesk.com/support/autocad-civil-3d/learn-explore/caas/video/youtube/watch-v-AQoB--nyUJA.html
81 109 Selvarani C
82 211 Selvarani C
h1. Orfeo
83 109 Selvarani C
84 109 Selvarani C
* https://www.orfeo-toolbox.org/
85 109 Selvarani C
86 109 Selvarani C
Remote sensing
87 158 Selvarani C
88 110 Selvarani C
89 110 Selvarani C
90 110 Selvarani C
91 163 Selvarani C
92 113 Selvarani C
93 113 Selvarani C
h1. Survey- Field to Finish
94 113 Selvarani C
95 113 Selvarani C
h2. Steps from field work 
96 113 Selvarani C
97 113 Selvarani C
# ?? To be added by Raj and Ram
98 113 Selvarani C
# Copy the .txt files from the equipment- Controller/Total station, to system using a pendrive (Storing the data- "D:"> "AVSM"> "Water Projects"> Respective project folder)> "TS"/"RTK")
99 113 Selvarani C
# Cleaning up the .txt files/removing errors (If any)
100 113 Selvarani C
101 113 Selvarani C
h2. Feeding the survey data into Civil 3D- by Surveyor
102 113 Selvarani C
103 113 Selvarani C
# After cleaning up of files, the files are stored in a desired location, to be used as import events into the Civil 3D file
104 113 Selvarani C
# Open up project in Civil 3D
105 113 Selvarani C
# Importing of Events (explain the step)
106 113 Selvarani C
107 113 Selvarani C
h2. Processing- by Surveyor
108 113 Selvarani C
109 113 Selvarani C
Initial line work is generated from survey points in the drawing. Points for reconciliation (Changing the point codes) are reported, if any. It is important that there is a fair knowledge of Autodesk Civil 3D for this work.
110 113 Selvarani C
111 113 Selvarani C
h2. Post-Processing
112 113 Selvarani C
113 113 Selvarani C
Final linework is generated on top of the processed linework. At this stage, a drawing is cleaned and prepared for sharing. problems like - overlaps in line-work, proper assigning of layers etc. Points for reconciliation are reported, if any. Post-Processing is crucial to generate correct and standardised survey drawings (in .dwg format) keeping in mind that those drawings will be used to generate shape files (.shp format). Therefore, it becomes important to follow a certain workflow based on compatibility of .dwg elements and .shp elements - for example for creating a shapefile of "Polygon" type, the elements in .dwg should be all "Polylines" of "closed" nature. All features should be in zero " 0 " elevation and the shapefile generated should be 3d type. This has been elaborated here < insert > At this stage, a good knowledge of Autodesk Civil 3D and GIS (to a certain extent) is a must.
114 113 Selvarani C
115 113 Selvarani C
h2. Creating shapefiles in AutoCAD
116 113 Selvarani C
117 217 Selvarani C
?? add by pavneet - *%{color:RED} to be written%*
118 113 Selvarani C
119 113 Selvarani C
h2. Sharing on WebGIS - "GISAF-  +gis.auroville.org.in+" 
120 113 Selvarani C
121 113 Selvarani C
After creating the shp files from AutoCAD, the shp files are ready to be shared on WebGIS platform. Following are the steps to do so.
122 113 Selvarani C
123 113 Selvarani C
124 113 Selvarani C
# *Upload and import Raw survey points to GISAF* - Before uploading and importing the shapefiles, it is necessary to upload and import the corresponding Raw survey points into GISAF.
125 113 Selvarani C
# *Auto-import of point shapefiles* - After the import of point files (RTK and TS), the next step is to Auto-import the points which are point type shp files. Go to Admin> Others> Projects> Select the corresponding project > With selected > Auto- import to GIS Database ( GISAF)
126 113 Selvarani C
# *Upload shp to basket* - Zip together all the types of files obtained after saving a shapefile on the system (shp, prj, dbf etc). Follow the same naming standards when creating this. Upload it to the basket in GISAF- Admin> Basket> Shapefiles> click on relevant project> click on relevant sub-project (if any)> upload file> select the zipped file from system> select the category from directory >save.
127 113 Selvarani C
# *Import to GISAF (Only with Authorization)* - Click on the import arrow.
128 113 Selvarani C
129 113 Selvarani C
h2. Adding new codes
130 113 Selvarani C
131 220 Selvarani C
ADD !! - *%{color:RED} to be written%*
132 113 Selvarani C
133 113 Selvarani C
h2. Reconciliation of points
134 113 Selvarani C
135 220 Selvarani C
The points are noted with their codes from and codes to reconcile into. ADD!! - *%{color:RED} to be written%*
136 119 Selvarani C
137 119 Selvarani C
h1. Survey Data Post-Processing
138 119 Selvarani C
139 119 Selvarani C
+Softwares used: Civil 3D, QGIS+
140 119 Selvarani C
141 119 Selvarani C
AutoCAD Civil 3D - C3D, 
142 119 Selvarani C
143 119 Selvarani C
C3D is being used for post processing of survey data. C3D offers a BIM solution for Land Surveyors. Basic knowledge about C3D can be obtained by following tutorials online though a pre-acquired knowledge of Autodesk AutoCAD is a plus point and sufficient enough to start working with C3D.
144 119 Selvarani C
145 119 Selvarani C
QGIS is an Open source GIS.
146 119 Selvarani C
147 119 Selvarani C
Getting Started:
148 119 Selvarani C
+Standards and Workflow for C3D+
149 119 Selvarani C
The layers (Nomenclature of layers is coming from standards- U.S. National CAD Standard Version-AIA) are pre-assigned a geometry type (Point, Line and Polygon) in their layers description (Use layer manager to check). This is done keeping in mind inter-operability with GIS (In shapefiles format), geometry type Shape files are of three kinds- points, lines and polygons.
150 119 Selvarani C
151 119 Selvarani C
+Geometry types-+
152 119 Selvarani C
Based on the description of Layers, if the layer Geometry is specified as 'Point', the raw survey data can be auto imported to webGIS - *GISAF*, no post processing is needed for 'Points'. For lines and polygons, We use Polylines (for 2D lines/Polygons) and 3Dpolylines (for 3D lines/polygons). In case of curved lines in 2D, Polylines command (PLINE/PL) is enough but its not possible to create curved lines in 3D using the 3Dpolylines, in such cases feature lines come into the picture. (*Important:* 2D polylines, splines, ellipses and circles are not exportable to shapefile format, they have to be always converted into Polylines).
153 119 Selvarani C
154 119 Selvarani C
*We are at the moment generating shapefiles (lines and polygons) in 2D (z=0) but keeping the format of files as 3D.
155 119 Selvarani C
156 119 Selvarani C
+Using Feature lines for creating Curved geometries in 3D-+
157 119 Selvarani C
There are a series of steps involved when creating curved lines using feature lines. You can follow two methods depending on the situation :-
158 119 Selvarani C
159 119 Selvarani C
Method 1(For curved objects in 3D using elevation of points):- Create the object using 3DPOLY. Now use the create feature lines from objects and select the objects to be converted to feature lines. You will not notice any difference in the geometry on the screen as such but in properties you will see the object type description of selected object as feature lines.
160 119 Selvarani C
161 119 Selvarani C
Method 2(For curved objects in 3D by draping the lines/curves on a surface):- Create the object using PLINE. You will notice all the lines are straight. Now use the create feature lines from objects and select the objects to be converted to feature lines. You will not notice any difference in the geometry on the screen as such but in properties you will see the object type description of selected object as feature lines.
162 119 Selvarani C
163 119 Selvarani C
Now modify tab is used to convert the straight lines to curved lines. There are many ways to do it and different methods can be adopted in different situations. The easiest and the most commonly used method is by using the smooth command in the modify tab. After using the smooth command, a curve would be visible. This is a curve in 3D. To view it, object viewer option can be used by selecting the object and right clicking.
164 119 Selvarani C
More complex methods have to be studied and each case has to be taken into consideration separatly when using - FITCURVEFEATURE In some cases to obtain a desired curve(Meaning more fragments) more PI's (Point of insertion) need to be added into the feature line. PI are the points where the feature lines gets fragmented when exploded.This step often becomes difficult to manage due to complexities involved in mathematical functions behind creation of feature lines.But it should be explored by all means.
165 119 Selvarani C
Because the feature lines are not exportable to shapefiles, the feature line has to converted back into a 3D polyline. This can be done simply by explolding the object. Once exploded into 3D polylines, you will see that the curve gets fragmented into smaller segments of straight lines. You can repeat the process of creating the 3Dpolyline object into feature line and then smoothening it till you get a desired geometry resembling the curve.
166 119 Selvarani C
Situations of sharing of points with different layers and proceeding with linework in such circumstances-
167 119 Selvarani C
There is always a best way to take the survey points taken in the field by the surveyor. For instance, in case of a road and a curb adjacent to it, the surveyor takes the points only once. It is only during the post processing that the lines are generated (You can create the lines in field while taking the survey points as well, but that is not the most feasible method majorly due to time constraints) and in this case, two line on the same position shall be generated, one under layer of roads and one under layer of curbs. 
168 119 Selvarani C
The line work becomes complex in case of generating 3d lines and 2d lines on the same place. This can arise due to having some layers as 2D (for example building outlines) and some as 3D (paved surfaces- <taking into consideration the future use of the layers. In this case, for the purpose of water management, it becomes essential to have survey of such surfaces as 3D. Survey of building outlines doesn't need to be 3D because the elevation points are not recorded while surveying them due to feasibility).
169 119 Selvarani C
So, in case of generating 3D linework from survey points with no elevation, Feature lines and SURFACES come into picture. The surfaces are generated by an interpolation method in C3D by giving a set of Point Groups. We have selected the triangulation method as the appropriate method due to availability of a dense set of points. 
170 119 Selvarani C
While creating the feature lines from objects (as explained above, check the box "assign elevation" and a dialog box appears to select the surface you want to select). Surfaces will have to be generated prior to using this. (add wiki for generating surface). Surface should be generated including the points of the layer in the point group of it. 
171 119 Selvarani C
172 119 Selvarani C
*+Purpose of Survey+*
173 119 Selvarani C
174 119 Selvarani C
# The survey is conducted for generating a Base Map which is representative of Topography, Infrastructure, Drainage, Buildings etc, with a focus on Water Management in Auroville. Furthermore this survey can be used as base map to build upon more detailed surveys for the various purposes such as Town planning, Land Surveys, Transportation Planning etc.
175 119 Selvarani C
176 119 Selvarani C
177 119 Selvarani C
+Use of Layers+
178 119 Selvarani C
179 119 Selvarani C
# *V-BLDG-SHED* (Shed) layer is used when the structure is not entirely enclosed, if At least one side is open (No walls/partition etc). One thumb rule is to answer the question if the building can be locked safely or not. If not, then it is a shed.
180 119 Selvarani C
# *V-BLDG-HUT* (Hut) is used when the building (For human activity/living space) is single storey with roof made up of perishable material such as keet, straw etc.
181 119 Selvarani C
# Use of *V-BLDG-ROOF* (Roof) is for buildings with permanent roofs extending out about more than 1 meter from the outline at ground level. It can also be used for complex roof structures for example Matrimandir Petals.
182 119 Selvarani C
# Use of *V-BLDG-OTLN* (Building outline) is for depicting the outer line of walls of a structure on ground level. This is used when the roof of the building is more or less of the same profile.
183 119 Selvarani C
# *V-BLDG-RTWL* (Retaining Wall) is for walls with the function of retaining either earth/water and the side of the wall should be visible. In case of very thin walls and no side visible, it comes as *V-BLDG-RWLL* (Retaining wall line). This is depicted as a single line in drawing.
184 119 Selvarani C
# Use of *V-ROAD-CYCP* is for designated cycle path as a single line.
185 119 Selvarani C
# Use of *V-ROAD-FPAT* is for pedestrian paths as a single line. It is used when there is a path of very small width. If the need is to represent a path/road which is unpaved in nature, *V-ROAD-UPVD* is used, which is polygon type. To represent a path/road of paved nature *V-ROAD-PAVD* is used, which is also a polygon type.
186 119 Selvarani C
# *V-WMNG-PIPP* for pipe points, *V-WMNG-PIPL*- for pipe lines.
187 119 Selvarani C
# *V-BLDG-BMRK* is for unidentified bench marks and *V-BLDG-MHOL* is for unidentified manholes.
188 119 Selvarani C
# *V-BLDG-PLTF* is for impervious surfaces. for example sand and gravel will not come under this layer. cemented paths etc can come.
189 119 Selvarani C
# *V-WMNG-POOL* is for water bodies made for leisure activities- like swimming pool etc.
190 119 Selvarani C
# *V-WMNG-SUMP* is collectively for artificial water retention structures.
191 119 Selvarani C
# *V-WATR-POND* is for top of natural water retention.
192 119 Selvarani C
# *V-WATR-PONB* is for bottom of natural water retention.
193 119 Selvarani C
# *V-WMNG-DRBA* is for bottom of artificial drains.
194 119 Selvarani C
# *V-WMNG-DRTA* is for top of artificial drains.
195 119 Selvarani C
# *V-WATR-DRBN* is for bottom of Natural drains.
196 119 Selvarani C
# *V-WATR-DRTN* is for top of Natural drains.
197 120 Selvarani C
# *V-WMNG-DRNC* is for drain covers.
198 1 Philippe May
# *V-WATR-DRAS* is for indicating slope of drainage, these are arrows.
199 120 Selvarani C
200 167 Selvarani C
201 121 Selvarani C
202 123 Selvarani C
203 169 Selvarani C
204 125 Selvarani C
205 125 Selvarani C
206 125 Selvarani C
207 170 Selvarani C
h1. *Reconcilation of Raw survey data using pgAdmin*
208 126 Selvarani C
209 126 Selvarani C
+For changing the layer codes, to be done using Pgadmin.+
210 126 Selvarani C
211 126 Selvarani C
h3.  Enter Schema> AVSM RAW Survey > Tables > select the table> Right click - View edit data > All rows. Apply filter to the original id and note the Database id's to be reconciled.
212 126 Selvarani C
213 126 Selvarani C
h3.  GISAf Admin> Other > Reconciliation. Create > Add the database (point) id and give the new target corresponding to the database id to be changed. (Use the Layer name in target not Raw layer name).
214 126 Selvarani C
215 126 Selvarani C
h3.  Other > Project > select the project > with selected> reconcile RAW survey points.
216 126 Selvarani C
217 127 Selvarani C
h1. Importing point data (TS and RTK) to GISAF 
218 127 Selvarani C
219 127 Selvarani C
# *Gisaf Admin > Basket > Survey data > "Project" > "surveyor" > TS/ RTK > upload > import.*
220 127 Selvarani C
# *Auto import of Raw points data* (changes from Raw to Shapefiles, the point files)
221 1 Philippe May
  In GISAF Admin > Other> Project > select the project for which you want to import the data > with selected > Auto import to GIS...
222 127 Selvarani C
223 172 Selvarani C
224 128 Selvarani C
225 128 Selvarani C
h1. Editing Z value of features in Shapefiles in QGIS
226 128 Selvarani C
227 128 Selvarani C
h2. using vertex editor tool - https://www.youtube.com/watch?v=8V8i1AtcA74&t=256s
228 128 Selvarani C
229 129 Selvarani C
h1. Miscellaneous- Civil 3D
230 129 Selvarani C
231 129 Selvarani C
*Autodesk civil 3D Geotechnical module- for borehole data :- To analyse borehole data, To make profiles and calculate volumes*
232 129 Selvarani C
233 129 Selvarani C
https://www.youtube.com/watch?v=0Be9kShBou0
234 129 Selvarani C
Reference videos
235 129 Selvarani C
Exploring:
236 129 Selvarani C
https://www.youtube.com/watch?v=gr-ISPzLcU0
237 129 Selvarani C
Modelling:
238 129 Selvarani C
https://www.youtube.com/watch?v=Pz0-HOoiBrs
239 129 Selvarani C
solids
240 129 Selvarani C
https://www.youtube.com/watch?v=mQ0Yeh6tZA8
241 129 Selvarani C
https://www.youtube.com/watch?v=4eMsUiYBhuE
242 129 Selvarani C
243 129 Selvarani C
244 129 Selvarani C
*CIVIL 3D Survey*
245 129 Selvarani C
Getting started- Always open a new drawing with a template. 
246 129 Selvarani C
247 129 Selvarani C
*Description key sets*- (till 18:30) https://www.youtube.com/watch?v=mmwkkRyBkS0
248 129 Selvarani C
As when the points come into the drawing, they are going to be filtered with description key sets and the description key sets will assign properties to the points.
249 129 Selvarani C
Tool space > settings > points > description key sets
250 129 Selvarani C
“Description key sets name”> edit key- to view the points in a list: 
251 129 Selvarani C
Automatic linework (18:30- till end)
252 129 Selvarani C
Survey > Linework code sets- for automatic linework
253 129 Selvarani C
254 129 Selvarani C
*Using Master view*
255 129 Selvarani C
Uses-
256 129 Selvarani C
copy styles from one drawing to other
257 129 Selvarani C
copy drawing data from one drawing to other (data referencing)
258 129 Selvarani C
259 129 Selvarani C
*Civil 3d surface model*- from points- break lines
260 129 Selvarani C
https://www.youtube.com/watch?v=wC40rdmDEMo
261 129 Selvarani C
moving for example- point groups under point groups- 
262 129 Selvarani C
263 129 Selvarani C
*Civil 3D Planning and Analysis*
264 129 Selvarani C
Workspace: Planning and Analysis
265 129 Selvarani C
1. Working with Object data (GIS Attributes)
266 129 Selvarani C
Map Setup> Define object data> New table> Define new object data table start defining fields
267 129 Selvarani C
268 129 Selvarani C
269 130 Selvarani C
270 130 Selvarani C
h1. Documentation- Rain Gauge
271 130 Selvarani C
272 130 Selvarani C
h2. Manual Rain Gauge
273 130 Selvarani C
274 130 Selvarani C
*Why it is important to comply to standards?*
275 130 Selvarani C
276 130 Selvarani C
1. Consistency for comparing rainfall data in different places within Auroville since rainfall varies in different parts of Auroville.
277 130 Selvarani C
278 130 Selvarani C
2. Making it possible to use for any kind of scientific analysis by contribution to the primary data in sustainable water management for Auroville. 
279 130 Selvarani C
280 130 Selvarani C
*Proposed standards and ethics:*
281 130 Selvarani C
282 130 Selvarani C
1. The time of taking the reading - 08:30 am. 
283 130 Selvarani C
The rain is recorded over a period of 24 hours- 8:30 of previous day till 8:30 of the present day, and the date is put as the present day. For example, if the rain is measured at 8:30 am on 10 dec 2017, then it is logged in as on 10 dec 2017.
284 130 Selvarani C
285 130 Selvarani C
2. Manual rain gauge typically used- green cylindrical and a collection jar.  
286 130 Selvarani C
  
287 130 Selvarani C
3. Measuring jar: 10 mm corresponding jar
288 130 Selvarani C
289 130 Selvarani C
 
290 130 Selvarani C
Area of the rim of manual rain gauge= 200 square cm
291 130 Selvarani C
Diameter of rim= approximately 16 cm
292 130 Selvarani C
*NOTE:* - If another kind of rain gauge is used, it should be used with the corresponding measuring jar as type of jar and calibration on jar depends on the area of rim. Any cases of different rain gauge other than above should be reported before use for recording purposes.
293 130 Selvarani C
294 130 Selvarani C
4. The minimum record-able unit is 0.2 mm (Least measure on the 10 mm cylinder). T is marked for below 1 mm.
295 130 Selvarani C
296 130 Selvarani C
5. The reading should be preferably submitted in an excel sheet (the data sheet will be provided). The frequency of sending data can be daily or weekly.
297 130 Selvarani C
6. The rain gauge should be kept in a safe and open to sky area clear from tree cover or objects in surrounding so that direct rain falls into it and not from trees/ objects etc. Preferably roof top or a higher place on ground.
298 130 Selvarani C
7. A check on the rain gauge should be kept when there is long period of gap in rainy days to make sure it was emptied out and there is no blockage. 
299 130 Selvarani C
300 130 Selvarani C
8. In case of doubt in reading or incorrect measure, "incorrect measure" should be marked
301 130 Selvarani C
302 130 Selvarani C
303 130 Selvarani C
*Ethics*
304 130 Selvarani C
1. Readings should not be missed. Time to time check on rain gauge is required during long periods of no rain (especially when the rain season is approaching). 
305 130 Selvarani C
This is important because firstly, if it rained in the night and it wasn’t recorded, reading for the day is lost; Secondly, if the jar was not emptied, it gives incorrect subsequent reading. 
306 130 Selvarani C
307 130 Selvarani C
2.  If the person is not going to be available temporarily where the rain gauge is kept, the responsibility should be passed on to someone they can rely on after explaining the standards. 
308 130 Selvarani C
309 130 Selvarani C
*Important-*
310 130 Selvarani C
Data won’t be published in case of non-compliance to standards. This is to maintain the sanctity of proper scientific data collection and to keep it reliable for sharing by publishing. Discussions regarding standards are welcomed.
311 130 Selvarani C
CSR Geomatics Team is placed on first floor in CSR, Auroshilpam.
312 130 Selvarani C
313 130 Selvarani C
*AV rain data publication*: (http://gis.auroville.org.in/measures/raingauge_av).
314 130 Selvarani C
315 130 Selvarani C
Adding Rain gauge to our web portal (GISAF), following information is needed:
316 130 Selvarani C
1. GPS co-ordinates of location of placing the rain gauge (can be obtained using mobile phones easily)
317 130 Selvarani C
2. Name, place of residence & contact number- Mobile & Landline
318 130 Selvarani C
319 130 Selvarani C
h2. Automatic Rain Gauge
320 130 Selvarani C
321 130 Selvarani C
There is a possibility of publishing rain data coming from Automatic rain gauges like (id 15, auro orchard) and Weather stations. 
322 130 Selvarani C
For Automatic rain gauges, we can upload the files coming from the rain gauge directly into GISAF.
323 130 Selvarani C
324 130 Selvarani C
325 130 Selvarani C
_Thank you for contribution towards a sustainable management of Water in Auroville through Data collection._
326 130 Selvarani C
327 130 Selvarani C
328 131 Selvarani C
329 131 Selvarani C
h1. Documentation- Wells Monitoring (Manual and Automatic / Piezometer by Bala)
330 131 Selvarani C
331 131 Selvarani C
h2. Manual- Using tape with a sensor
332 131 Selvarani C
333 131 Selvarani C
Timings: The person assigned the job of monitoring collects the readings in three slots.
334 131 Selvarani C
335 131 Selvarani C
1.	Between 6 am to 7 am till about 9 am to 10 am.
336 131 Selvarani C
2.	Between 11 am and 1 pm
337 131 Selvarani C
3.	Between 2 pm and 5 pm
338 131 Selvarani C
339 131 Selvarani C
Things required:
340 131 Selvarani C
•	Notebook
341 131 Selvarani C
•	Pen
342 131 Selvarani C
•	Measuring tape
343 131 Selvarani C
•	Vehicle for movement
344 131 Selvarani C
345 131 Selvarani C
346 131 Selvarani C
*Ethics*- 
347 131 Selvarani C
•	The monitoring should happen in coordination with the community members/ care taker (assigned by the person in charge from within the community). There should be a clear communication from monitor side as to which days the monitoring of a well has to happen and at around what time so that it can be made sure that the pump is not turned on before monitoring. In case a pump was turned on in a well, the monitor should have a gap of about 5 hours on the same day before going again for monitoring.
348 131 Selvarani C
•	The monitor should have contact numbers of the person in charge/ care taker for any communication.
349 131 Selvarani C
•	If the monitoring is stopped for any reason at any point, the monitor should communicate the same to the person concerned.
350 131 Selvarani C
•	The monitor shall take responsibility to inform any kind of changes in a well in terms of its functioning etc.
351 131 Selvarani C
•	The monitor should report to the CSR Geomatics Team who has responsibility to publish data.
352 131 Selvarani C
•	The monitor published the data to the website and works with the geomatics team.
353 131 Selvarani C
354 131 Selvarani C
355 131 Selvarani C
*Definitions*:
356 131 Selvarani C
A master file is maintained with the records of the wells from the field. It is updated when a new well is located. The following set of information are filled out in the Masterfile. 
357 131 Selvarani C
358 131 Selvarani C
*Well type*
359 131 Selvarani C
1.	Open
360 131 Selvarani C
2.	Borewell
361 131 Selvarani C
3.	Dug cum borewell
362 131 Selvarani C
363 131 Selvarani C
*Well status*
364 131 Selvarani C
1.	In use
365 131 Selvarani C
2.	Not in use
366 131 Selvarani C
3.	Closed
367 131 Selvarani C
368 131 Selvarani C
*Pump Status*
369 131 Selvarani C
1.	Functioning
370 131 Selvarani C
2.	Not functioning
371 131 Selvarani C
372 131 Selvarani C
*Pump Automation*
373 131 Selvarani C
1.	Manual 
374 131 Selvarani C
2.	Automatic
375 131 Selvarani C
376 131 Selvarani C
* Non-accessibility factors*
377 131 Selvarani C
1.	Dogs
378 131 Selvarani C
2.	Heavy slab
379 131 Selvarani C
3.	Narrow casing
380 131 Selvarani C
4.	enclosed/locked
381 131 Selvarani C
5.	permission
382 131 Selvarani C
383 131 Selvarani C
*Data Matching Accuracy (reconnecting with harvest wells data)*
384 131 Selvarani C
1.	High
385 131 Selvarani C
2.	Medium
386 131 Selvarani C
3.	Low
387 131 Selvarani C
388 131 Selvarani C
*Well coordinates*
389 131 Selvarani C
For a new well, coordinates of the well position are taken on a mobile GPS.
390 131 Selvarani C
Person In charge
391 131 Selvarani C
For communication purpose, contact the person in charge as recorded in directory.
392 131 Selvarani C
393 131 Selvarani C
h2. Automatic- Piezometer (by bala, to be edited) 
394 131 Selvarani C
395 131 Selvarani C
The calibrations and setting are already done by Azha
396 131 Selvarani C
The piezometer is taken to the site of unused well. First the depth and Water level  is checked manually using water meter
397 131 Selvarani C
Then the sensor of the piezometer is inserted into the well 1m above the bottom of the well, so the sensor does not get affected from mud or water inside
398 131 Selvarani C
The sensor sends the data to an electronic board which translates the signal into the proper output, and then it sends the signal to the transmitting device above, on the ground surface. The transmitter then sends it to the receiver at CSR, the signal is then routed to Talam office through Interneet, enters the software and the reading is processed.
399 131 Selvarani C
The piezometer sometimes does not have proper signal and so it would not be able to send it
400 131 Selvarani C
401 132 Selvarani C
h1. Documentation- Flow meter by Bala
402 132 Selvarani C
403 132 Selvarani C
Flow meter – for checking the flow of water in pipe
404 132 Selvarani C
405 132 Selvarani C
CSR bought ultrasonic flow meter from Chennai and the company (company name? )trained Bala and Vijai(CSR) on how to set it up.
406 132 Selvarani C
we tested in the west water system pump in csr. then we test in many more place .
407 132 Selvarani C
 ami, aurodam and buddha garden borewell pumps . we got request from the water service 
408 132 Selvarani C
Cross check they flow meters .
409 132 Selvarani C
 so before that  we want to know how our meter works. 
410 132 Selvarani C
so we tested in our tank . the pump pumping from our sump tank so the flow will be stranded.  when you pump in the bore well  the flow goes up and down. 
411 132 Selvarani C
we tested two times in  15 minutes.and one time 30 minutes,so we got variation between this three. 
412 132 Selvarani C
we find 1,5 % error but the flow meret they said  1 % error only.
413 132 Selvarani C
we cross checked the flow meter of the water service we find some error  in they meter also. 
414 132 Selvarani C
we tried they bore well flowmeter and they sump tank flow meter also.and we find some error also in they meters.  
415 132 Selvarani C
then we find some error in (AVWS) meter also.
416 132 Selvarani C
It is used to check the flow of water in pipe
417 132 Selvarani C
tools used 
418 132 Selvarani C
First the outer diameter of the pipe has to be entered in the device. It is measured using Vernier caliper
419 132 Selvarani C
Then the thickness of the pipe is set which is also measured using vernier
420 132 Selvarani C
Also the device asks for the material of the pipe. If the pipe material is know it can be set and if it not know then there is an option which is other (mostly PVC, HDPE, and  iron) 
421 132 Selvarani C
After entering these details the device gives the spacing for the sensors. There are 2 sensors up and down which has to be fixed accordingly
422 132 Selvarani C
When the sensors are fixed the motor is turned on and the sensors send reading to the display device
423 132 Selvarani C
This is noted down once every minute and taken for 15 to 30 minutes. Then the average of this is determined. This is done because of the variation in the flow. This gives the flow rate in 1 hour.
424 1 Philippe May
This was done in different places to check to flow rate
425 132 Selvarani C
426 177 Selvarani C
427 133 Selvarani C
428 133 Selvarani C
h1. Documentation- DST- Vegetation Indexing
429 133 Selvarani C
430 133 Selvarani C
h2. Steps for Dzetsaka Classification tool for Vegetation indexing in QGIS
431 133 Selvarani C
432 133 Selvarani C
 
433 133 Selvarani C
 1. Install the plugin Dzetsaka classfication tool.
434 133 Selvarani C
 2. Open the Raster from the Survey.
435 133 Selvarani C
 3. Create a polygon shapefile for index sampling. Mark polygons and give the ID's (1,2,3 for Tree, grass, bare land etc) Cover the variations in samples as much as possible. 
436 133 Selvarani C
     More the samples, better the indexing.
437 133 Selvarani C
 4. Apply Dzetsaka Classification tool, Select the base raster and the sample- index polygon shapefile created in step 3.
438 133 Selvarani C
 5. The result is a Raster with DN numbers specified in the Shapefile in step 3.
439 133 Selvarani C
 6. Apply the Sieve raster command (Raster> Analysis> Sieve)- Try different threshold numbers and view the results till the noise is removed from the Raster.
440 133 Selvarani C
 7. Polygonise the Raster to Vector (From processing)
441 133 Selvarani C
 8. Run the v.generalise tool on the shapefile. This tool removes the pixelated boundaries of the polygons in the Vector.
442 133 Selvarani C
443 134 Selvarani C
h1. Documentation- DST- Interpolation (Processing toolbox)
444 134 Selvarani C
445 134 Selvarani C
The following 4 tools have been mostly explored and the results were compared. The ones used for quick analysis are 1. Cubic Spline and 2. V.surf.spline . The rest of the tools are for further exploration and used depending on the need of the project. In some tools, the elevation values of points should be stored in the attribute table (Using field calculator and giving command - *Z($Geometry)* )
446 134 Selvarani C
447 134 Selvarani C
# Interpolate (Cubic spline) - SAGA
448 134 Selvarani C
# V.surf.bspline - GRASS. Parameters to set - cell size. Set this parameter above 0.001 ( 0.00001, 0.000001 etc) and check the results.
449 134 Selvarani C
# V.surf.rst - GRASS
450 134 Selvarani C
# Krigging - SAGA
451 1 Philippe May
452 181 Selvarani C
[[Documentation- DST- Survey- Office workflow]]  - *%{color:RED} to be written%*
453 135 Selvarani C
454 135 Selvarani C
h1. From CAD to GIS by Giulio
455 135 Selvarani C
456 135 Selvarani C
*FEATURES CREATION*
457 135 Selvarani C
1.	Assign a CRS to the drawing (TM-AUSPOS) (MAPCSLIBRARY command)
458 135 Selvarani C
2.	Create features in CAD (Points, lines, polygons)
459 135 Selvarani C
3.	Export shapefile (a) from CAD (Output > DWG to SDF) (Convert to LL84 – 3D)
460 135 Selvarani C
461 135 Selvarani C
*FEATURES IMPORT INTO DB FIRST TIME*
462 135 Selvarani C
4.	Create zip file of the shapefile
463 135 Selvarani C
5.	Upload into the GISAF Shapefiles Basket
464 135 Selvarani C
6.	Import the shapefile into DB
465 135 Selvarani C
7.	Save the shapefile on Local Machine
466 135 Selvarani C
467 135 Selvarani C
*FEATURES IMPORT INTO DB EVERYTIME*
468 135 Selvarani C
8.	Combine the new features to corresponding last shape files (Insert the process here).
469 135 Selvarani C
9.	Follow step 4-8 again
470 135 Selvarani C
471 135 Selvarani C
*FEATURES EDITING IN QGIS*
472 135 Selvarani C
10.	Open the table in QGis
473 135 Selvarani C
11.	Save as a shapefile (b) in TM AUSPOS CRS
474 135 Selvarani C
12.	In CAD, open a new drawing and assign AUSPOS CRS
475 135 Selvarani C
13.	Import the shapefile (b) (MapImport) with Object Data (Data tab > Create Object Data > OK), tick “Import polygons as closed polylines”, then press OK
476 135 Selvarani C
14.	Edit features
477 135 Selvarani C
15.	Change workspace into “Planning and analysis”
478 135 Selvarani C
16.	Export shapefile (a) from CAD (Output > DWG to SDF) with ONLY the id selected (Data Tab > Select Attributes > Object Data > Filename > id) (Convert to LL84 – 3D)
479 135 Selvarani C
480 135 Selvarani C
*FEATURES IMPORT INTO DB*
481 135 Selvarani C
17.	Create zip file of the shapefile
482 135 Selvarani C
18.	Upload into the GISAF Shapefiles Basket
483 135 Selvarani C
19.	Import the shapefile into DB
484 135 Selvarani C
20.	Delete the shapefile from Local Machine
485 135 Selvarani C
486 135 Selvarani C
487 182 Selvarani C
488 1 Philippe May
489 136 Selvarani C
h1. QGIS- Miscellaneous
490 136 Selvarani C
491 136 Selvarani C
*QGIS Introduction:*
492 136 Selvarani C
https://www.birdseyeviewgis.com/blog/2018/2/22/my-favorite-features-of-qgis-30to-date
493 136 Selvarani C
3D visualization of raster DEM- https://www.youtube.com/watch?v=2KrCsbP0kUs
494 136 Selvarani C
495 136 Selvarani C
*Spatial query:* 
496 136 Selvarani C
Spatial Query is selection of features that satisfies a certain condition which relates to other features in a space.
497 136 Selvarani C
Using plugin- Spatial query
498 136 Selvarani C
http://www.geodose.com/2018/03/spatial-query-in-qgis-3.html
499 136 Selvarani C
Labelling:
500 136 Selvarani C
Labelling with more than one field names and in different lines
501 136 Selvarani C
|| '\n' ||
502 136 Selvarani C
503 136 Selvarani C
504 136 Selvarani C
505 136 Selvarani C
*Hierarchy of extensions*
506 136 Selvarani C
507 136 Selvarani C
File levels and their uses.
508 136 Selvarani C
https://nathanw.net/2014/03/22/all-the-q-files/
509 136 Selvarani C
510 136 Selvarani C
+The Project file (.qgs)+
511 136 Selvarani C
It contains: Layer source pointer + Style information + Composers + a whole heap of other stuff
512 136 Selvarani C
513 136 Selvarani C
+The Layer Definition file (.qlr)+
514 136 Selvarani C
It contains: Layer source pointer + Style information
515 136 Selvarani C
516 136 Selvarani C
+The QML file (.qml)+
517 136 Selvarani C
It contains: Style information
518 136 Selvarani C
519 59 Giulio Di Anastasio
h2. Giulio's documentation
520 52 Giulio Di Anastasio
521 183 Selvarani C
522 137 Selvarani C
523 137 Selvarani C
h1. Documentation - Reconciliation of points using Gisaf
524 137 Selvarani C
525 137 Selvarani C
Reconciliation of points is a procedure used when a point is stored in a wrong table, because its category was either wrongly recorded in the field by the surveyor, or it has ben reviewed later by the surveyor or the data validator and found to be wrong.
526 137 Selvarani C
527 137 Selvarani C
h2. Definition: Raw points are all points coming from the field survey. Raw points can be points referring to a Point feature (e.g. trees, or elevation points, or floor level), or points measured in the field to draw a line (e.g. the vertices of a fence) or a polygon (e.g. the corners of a building outline).
528 137 Selvarani C
529 137 Selvarani C
In the overall workflow, *+reconciliation affects only raw points+*. It takes place after the field textfile is uploaded into the basket and its points imported (raw points stored in the raw survey tables). Here you can visualize the Workflow diagram: [[Survey_data]].
530 137 Selvarani C
531 137 Selvarani C
532 137 Selvarani C
If a raw point refers to a point feature, reconciling it means moving it to another category/table meant for point features, not for lines/polygons. So, *+only raw points of point features can be reconciled+*. Raw points pertaining to line features and/or polygon features cannot be reconciled, so these raw points will remain in their original wrong table.
533 137 Selvarani C
534 137 Selvarani C
535 137 Selvarani C
PLEASE NOTE: 
536 137 Selvarani C
The attributes of a line/polygon, which are derived from their defining raw points, will not be modified by any reconciliation, because *+only raw points of point features can be reconciled+*.
537 137 Selvarani C
538 137 Selvarani C
h2. How to perform Reconciliation
539 137 Selvarani C
540 137 Selvarani C
To perform reconciliation of points: Login to Gisaf -> click on the G icon on the upper-left corner of the website page -> Manage -> Reconciliation by orig.ID
541 137 Selvarani C
542 137 Selvarani C
On the right end side of the screen, clicking on the field "Destination" a list of all categories will appear: these categories refer not to the Raw survey tables, but to the V_ tables of the database (points, lines, polygons).
543 137 Selvarani C
544 137 Selvarani C
Under it, in the field "Original ID", the original point number of the point to be reconciled is to be entered.
545 137 Selvarani C
546 137 Selvarani C
Clicking on the "Search points" button, the result shows the database unique id of the point, its survey category, its survey date, its geometry type (point, line, polygon), and the Project the point belongs to. In case of multiple points with the same original id (in case of different Projects, the field number of points might be not unique if the numbering of points in the field has restarted) all points having that original id are displayed: thanks to their date or Project or type, it is easy to identify the correct point to be reconciled.
547 137 Selvarani C
548 137 Selvarani C
Once the point to be reconciled is identified, clicking on the button "Reconcile" will run the reconciliation, and a message will appear stating that it has been done successfully. An error message can appear if a reconciliation of a raw point of a line/polygon feature has been attempted: this type of points cannot in fact be reconciled.
549 137 Selvarani C
550 137 Selvarani C
Once a raw point has been reconciled, *+it cannot be reconciled again+*. In case a raw point has been wrongly reconciled, it cannot be reconciled again through the above procedure, but it has to be reconciled manually through QGis or pgadmin software.
551 137 Selvarani C
552 138 Selvarani C
h1. Documentation - Status and Status Changes
553 138 Selvarani C
554 138 Selvarani C
Status have been created to keep track og changes in surveyed features.
555 138 Selvarani C
It is an additional (though provided for in AIA standards), single digit value, at the end of the Gisaf Category/Cad layer name.
556 138 Selvarani C
Each Status need to have a corresponding CAD layer/Gisaf Category, with a short code associatedto it, so that field entries can be done easily.
557 138 Selvarani C
558 138 Selvarani C
Status have been defined as follows:
559 138 Selvarani C
N - New Work
560 138 Selvarani C
E - Existing o remain
561 138 Selvarani C
D - Existing to demolish, Demolished or Changed
562 138 Selvarani C
F- Future work, Proposed feature
563 138 Selvarani C
T - Temporary work
564 138 Selvarani C
M - Item to be moved
565 138 Selvarani C
X - Not in contract
566 138 Selvarani C
567 138 Selvarani C
568 138 Selvarani C
By default, Status is defined as E (Existing). Status can anyhow be changed later using gAdmin, or QGis (through the PostGis connection).
569 138 Selvarani C
It needs to be done manually, one feature (point, line, polygon) at a time.
570 138 Selvarani C
571 138 Selvarani C
572 1 Philippe May
In the future Status changes might be incorporated in the Admin panel.
573 138 Selvarani C
574 185 Selvarani C
575 67 Giulio Di Anastasio
576 139 Selvarani C
h1. Documentation - Tags retained after re-import of same geometry
577 139 Selvarani C
578 139 Selvarani C
Documentation - Tags retained after re-import of same geometry
579 139 Selvarani C
The linework for infrastructure survey carried out by Eric Chacra in May 2020 was originally imported with a problem of ambiguity in the "Accuracy" table and in the "Accuracy" table.
580 139 Selvarani C
The result was that lines did not inherit the attributes survey date, accuracy, equipment, surveyor.
581 139 Selvarani C
Nevertheless lines were displayed on the Gisaf map, without these attributes, and tags were given to some of these lines.
582 139 Selvarani C
583 139 Selvarani C
The values for the two tables ("Accuracy", "Accuracy") have been corrected, ambiguity resolved.
584 139 Selvarani C
The lines in the layers V-ELEC-UGND------E and V-COMM-CABL------E have been then reimported, the attributes have been properly assigned, and the tags have been retained.
585 139 Selvarani C
586 139 Selvarani C
4 August 2020
587 139 Selvarani C
588 67 Giulio Di Anastasio
h1. Access to data
589 67 Giulio Di Anastasio
590 67 Giulio Di Anastasio
h2. Connection to server directly from CSR
591 67 Giulio Di Anastasio
592 67 Giulio Di Anastasio
To connect to the server directly without going through Aurinoco server, the correct url is
593 67 Giulio Di Anastasio
http://gis.csr.av
594 67 Giulio Di Anastasio
595 67 Giulio Di Anastasio
h2. Connection to Gisaf via QGis through WFS / OGC API
596 67 Giulio Di Anastasio
597 67 Giulio Di Anastasio
This works only on QGis from version 3.14.15 onward
598 67 Giulio Di Anastasio
599 67 Giulio Di Anastasio
In the browser, click on WFS/OGC API, then right-click to create a new connection
600 67 Giulio Di Anastasio
Give a name (e.g. OGC API Qgis Gisaf)
601 67 Giulio Di Anastasio
Give the url https://gis.auroville.org.in/ogcapi
602 67 Giulio Di Anastasio
603 67 Giulio Di Anastasio
Under the WFS Options box, on Version dropdown, the default option "Maximum" works just fine
604 67 Giulio Di Anastasio
Click on OK
605 67 Giulio Di Anastasio
The list of layers will appear in the Browser under WFS/OGC API.
606 68 Giulio Di Anastasio
607 68 Giulio Di Anastasio
608 68 Giulio Di Anastasio
h1. How to create a new projection in QGis
609 68 Giulio Di Anastasio
610 68 Giulio Di Anastasio
To create a new projection in QGis, go to menu "Settings", and click on "Custom Projections".
611 68 Giulio Di Anastasio
A pop-up window appears with a list of all projections defined in QGis projects used by the user so far.
612 68 Giulio Di Anastasio
Click on the green "+" sign on the right top part of the window to create a new projection.
613 68 Giulio Di Anastasio
In the "Name" box, type "TM CSRAUSPOS SF1" (which means TM = Transverse Mercator projection; CSRAUSPOS = theparameters for this projection are derived from the processing of DGPS raw data by AUSPOS -  Online GPS Processing Service - https://www.ga.gov.au/scientific-topics/positioning-navigation/geodesy/auspos; SF1 = Scale Factor is 1).
614 68 Giulio Di Anastasio
In the "Format" dropdown list, select "Proj String (legacy - Not Recommended)"
615 68 Giulio Di Anastasio
In the "Parameters" box, paste the following "+proj=tmerc +lat_0=12.01605433+lon_0=79.80998934 +k=1 +x_0=370455.630 +y_0=1328608.994 +ellps=WGS84+towgs84=0,0,0,0,0,0,0 +units=m +no_defs".
616 68 Giulio Di Anastasio
617 68 Giulio Di Anastasio
Finally, click on OK.
618 68 Giulio Di Anastasio
619 68 Giulio Di Anastasio
In a more explicit  way, the parameters mean the following:
620 68 Giulio Di Anastasio
Map Projection:        TransverseMercator (TM)
621 68 Giulio Di Anastasio
False Easting:          370455.6300
622 68 Giulio Di Anastasio
False Northing:        1328608.9940
623 68 Giulio Di Anastasio
Latitude of Origin:    12°00'57.79560" (DMS)   12.01605433 (DD)
624 68 Giulio Di Anastasio
Central Meridian:     79°48'35.96164"  (DMS)   79.80998934 (DD)
625 68 Giulio Di Anastasio
Scale Factor:             1.00000000
626 68 Giulio Di Anastasio
Zone Width:              6.0°
627 69 Giulio Di Anastasio
628 69 Giulio Di Anastasio
h1. Elimination of Duplicate points – General criteria
629 69 Giulio Di Anastasio
630 69 Giulio Di Anastasio
It might happen that the same physical feature (e.g. a tree, or a pole) is surveyed more than once: this can happen because there are many physical features in an area, and the survey needs more than one station. So, for example a tree is surveyed from a station, and gets a serial number on that date. When the station is then changed, it might happen that the same tree is resurveyed: another serial number is given, and possibly a different date, if the survey from the second station happened on a different day.
631 69 Giulio Di Anastasio
It is clear that the same tree is then represented with two different points, which means that two different trees exist: but only one tree really exist in the physical reality.
632 69 Giulio Di Anastasio
It is clear that one of the two points is redundant and needs to be removed. If this is noted by the surveyor directly in the field, then the issue is solved by the surveyor himself during processing time.
633 69 Giulio Di Anastasio
If instead, due to various reasons, it was not noted by the surveyor in the field, it will need to be cleaned after the processing, possibly by post-processing staff.
634 69 Giulio Di Anastasio
How to identify duplicate points?
635 69 Giulio Di Anastasio
The following criteria can be used:
636 69 Giulio Di Anastasio
1.	The distance between the two points is less than 30 cm (trees are surveyed if their trunk diameter is at least about 20 cm, so in 30 cm cannot exist two of them)
637 69 Giulio Di Anastasio
2.	The orig_id (serial number) of the points are not in series
638 69 Giulio Di Anastasio
3.	The survey date is not the same
639 69 Giulio Di Anastasio
4.	In case of trees, the species of trees is the same
640 69 Giulio Di Anastasio
5.	5. In case of trees, the tree type is not TDEF (because TDEF are mapped irrespective of their diameter, so they can actually have a small trunk, and two of them might exist in 30 cm), not OT (many TDEF species are surveyed as OT if not otherwise indicated by a botanist)
641 69 Giulio Di Anastasio
6.	The context needs to be evaluated: if one tree is deleted in an area where many trees exist in a limited space, then loosing one in the map is not a big error. If instead one tree is deleted where there are very few trees, then it might be a big loss.
642 70 Giulio Di Anastasio
643 70 Giulio Di Anastasio
644 70 Giulio Di Anastasio
h1. Linework for the Survey Area
645 70 Giulio Di Anastasio
646 70 Giulio Di Anastasio
h2. 1.	Creation of Initial Linework in QGIS using Survey points import - (Ram, System 4)
647 70 Giulio Di Anastasio
648 70 Giulio Di Anastasio
Initial Linework in QGIS is started by surveyor with the knowledge from the Field. For this step, points are simply imported into the QGIS from the field text file (.csv or .txt). CRS needs to be TM-AUSPOS. The box of “First record has field names” shall not be ticked. In Point Coordinates, select the correct field for x, for y and for z (usually “field_2” for x, “field_3” for y and “field_4” for z). Points can be styled using the “Categorized” style in “Symbology”, using “Field_5” as value, or using a Rule-based symbology using the category (field 5) as filter.
649 74 Selvarani C
Linework is created by connecting points having same description and belonging to the same physical feature. *All line and polygon features are created as lines*.
650 70 Giulio Di Anastasio
The Initial Linework for the Survey Area is also stored temporarily in 
651 70 Giulio Di Anastasio
652 74 Selvarani C
+D: > AVSM > Zone-Survey number (eg RZ-01) > Survey Area (eg J) > Temporary WD+
653 70 Giulio Di Anastasio
654 70 Giulio Di Anastasio
h2. Note: The line shapefiles / Geopackages shall be in CRS: TM AUSPOS
655 70 Giulio Di Anastasio
656 70 Giulio Di Anastasio
h2. 2.	Creation of final working drawing Shapefiles / Geopackages - (Selvarani, System 1)
657 1 Philippe May
658 1 Philippe May
Final working drawing Shapefiles / Geopackages are created from the Initial Linework of Survey Area.
659 70 Giulio Di Anastasio
As the Surveyor draws all features as lines (both for lines and polygons features), the following actions shall be done:
660 74 Selvarani C
1.	*If features are lines:*
661 70 Giulio Di Anastasio
•	Export the shapefile / geopackage into the final working drawing folder (Final WD), in separate folders according to its type (e.g. BLDG, FENC, ROAD, etc).
662 70 Giulio Di Anastasio
663 70 Giulio Di Anastasio
h2. The CRS for the export shall be EPSG:4326 - WGS 84
664 70 Giulio Di Anastasio
665 74 Selvarani C
2.	*If features are polygons:*
666 1 Philippe May
•	Lines shall be converted into polygons:
667 74 Selvarani C
668 1 Philippe May
to do it, first click on the layer to be converted to make it active (e.g. WD-CZ-01-F-LL84_V-BLDG-MHOL------E), then go to “Vector” Menu, click on Geometry Tools, click on Line to Polygons:
669 87 Selvarani C
670 84 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9760/Line%20to%20Polygon%20Menu.png!
671 70 Giulio Di Anastasio
672 86 Selvarani C
673 1 Philippe May
The new window for “Lines to Polygons” conversion will appear:
674 86 Selvarani C
675 86 Selvarani C
676 83 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9762/Lines%20to%20Polygon%20Window.png!
677 1 Philippe May
678 71 Giulio Di Anastasio
•	Always cross check the input layer, to make sure that the input layer is the active one
679 71 Giulio Di Anastasio
•	Save the output in a temporary layer
680 74 Selvarani C
•	The temporary layer will be listed in the list of layers, it shall be exported to the saving location as +D: > Survey > Zone-Survey Number > Final WD > Survey Area SHP+ (eg . D: > Survey > GB-01 > Final WD > A-Shp)
681 72 Giulio Di Anastasio
682 74 Selvarani C
h2. The CRS for the export shall be EPSG:4326 - WGS 84
683 74 Selvarani C
684 72 Giulio Di Anastasio
Once all the shapefiles / geopackages are exported in Final WD, for each of the newly exported layers the Topology Checker Tool shall be used.
685 1 Philippe May
686 74 Selvarani C
h2. Linework for the whole Survey Zone
687 74 Selvarani C
688 74 Selvarani C
h2. 1.	Merging Shapefiles / Geopackages - (Selvarani, System 1)
689 74 Selvarani C
690 72 Giulio Di Anastasio
A copy of the Zone Master shapefiles / geopackages are taken from System 4 and stored in Temp Folder on Desktop in System 1.
691 1 Philippe May
Master shapefiles / geopackages are merged with the Survey Area shapefiles / geopackages:
692 72 Giulio Di Anastasio
•	To do it, go to “Vector” Menu, click on Geoprocessing Tools, then click on Union:
693 72 Giulio Di Anastasio
694 85 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9763/Union%20Menu.png!
695 1 Philippe May
696 1 Philippe May
697 85 Selvarani C
The new window for “Union” will appear:
698 1 Philippe May
699 86 Selvarani C
700 86 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9764/Union%20Window.png!
701 73 Giulio Di Anastasio
702 74 Selvarani C
•	To make sure that the right geometry is generated by this process (“line” type, not “Multiline”, and similarly “Polygon” type, not “Multipolygon), we need to always keep the *Master shapefile* (e.g. Final-CZ-01-2021-02-05-LL84_V-BLDG-MHOL------E) *as Input layer*, and the Survey Area shapefile as Overlay Layer (e.g. WD-CZ-01-F-LL84_V-BLDG-MHOL------E).
703 73 Giulio Di Anastasio
•	(The output can be saved to a file, as the CRS should already be EPSG4326 – WGS84.)
704 73 Giulio Di Anastasio
705 74 Selvarani C
h2. 2.	Storing Shapefiles / Geopackages - (Selvarani, System 1)
706 74 Selvarani C
707 74 Selvarani C
Save the merged shape file in the correct location in Final folder as +D: > Survey > Zone-Survey Number > Final+ (eg . D: > Survey > GB-01 > Final)
708 73 Giulio Di Anastasio
Date in the name of Final Shapefile / Geopackage needs to be updated.
709 73 Giulio Di Anastasio
Once the merging operation is completed, the copy of Master shapefile / geopackage is deleted from the Temp folder.
710 73 Giulio Di Anastasio
711 74 Selvarani C
h2. 3.	Topology check of merged shapefiles
712 74 Selvarani C
713 73 Giulio Di Anastasio
The topology checker is applied again on the merged shapefiles / geopackages.
714 73 Giulio Di Anastasio
The “id_field” shall be removed from the attribute table.
715 73 Giulio Di Anastasio
716 74 Selvarani C
h2. 4.	Archive and replace the Master Shapefiles / Geopackages (Ram, System 4)
717 74 Selvarani C
718 73 Giulio Di Anastasio
Archive the previous master shapefiles / geopackages on system 4, and copy the new merged shapefiles / geopackages in its place.
719 74 Selvarani C
*Then delete the Merged Shapefile / Geopackage folder from System 1.
720 74 Selvarani C
*
721 73 Giulio Di Anastasio
722 74 Selvarani C
h2. 5.	Note about Shapefiles and Geopackages
723 73 Giulio Di Anastasio
724 73 Giulio Di Anastasio
All the above works are usually done using shapefile format, in QGIS latest version (3.16.3).
725 221 Selvarani C
The Geopackage export is done in QGis versions older than 3.12 (e.g. 3.4, 3.6, 3.8, 3.10) so that the lines are not saved as “Multilines” but as “Lines”and polygons are not saved as “Multipolygons” but as “Polygons”. This is very important to be noted, as Gisaf database does not accept the Multipolygon and Multiline geometry types.
726 221 Selvarani C
A different way to create "Polygons" is to use the command Vector -> Geometry Tools -> Multipart to Single Parts and apply it to the layer: from "Multipolygon" it will become "Polygon" (check in layer Properties).
727 222 Selvarani C
As on 13 March 2021, Gisaf can accept Multipolygon layers, because the command "Multipart to Single parts" has been integrated into the importing command (see Redmine ticket #11691)
728 223 Selvarani C
729 223 Selvarani C
h1. Creating 3D Shapefile/Geopackage
730 223 Selvarani C
731 223 Selvarani C
While creating a Shapefile/Geopackage, the File name/Database-table name, Geometry type and CRS have to be entered.
732 223 Selvarani C
In order to create a 3D Shapefile/Geopackage, the additional dimensions *"Z(+M values)"/ "Include Z dimension"* has to be ticked: this way the 3D Shapefile/Geopackage is accepted by Gisaf without errors, otherwise the Shapefile/Geopackage can't be imported in Gisaf because the Z dimension is missing (the geometries in the database are all 3D).
733 224 Giulio Di Anastasio
734 224 Giulio Di Anastasio
h1. Exporting from QGis (shapefiles and/or geopackages) to CAD dxf format
735 224 Giulio Di Anastasio
736 226 Giulio Di Anastasio
An algorithm has been created by Selvarani, to see the whole process click here:
737 226 Giulio Di Anastasio
https://redmine.auroville.org.in/projects/gis/wiki/Automatic_export_from_QGis_to_dxf