Project

General

Profile

Wiki » History » Version 270

Giulio Di Anastasio, 06/05/2021 10:53

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 220 Selvarani C
h2. Reconciliation of points
92 113 Selvarani C
93 113 Selvarani C
The points are noted with their codes from and codes to reconcile into. ADD!! - *%{color:RED} to be written%*
94 270 Giulio Di Anastasio
95 270 Giulio Di Anastasio
96 119 Selvarani C
97 119 Selvarani C
h1. Survey Data Post-Processing
98 119 Selvarani C
99 119 Selvarani C
+Softwares used: Civil 3D, QGIS+
100 119 Selvarani C
101 119 Selvarani C
AutoCAD Civil 3D - C3D, 
102 119 Selvarani C
103 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.
104 119 Selvarani C
105 119 Selvarani C
QGIS is an Open source GIS.
106 119 Selvarani C
107 119 Selvarani C
Getting Started:
108 119 Selvarani C
+Standards and Workflow for C3D+
109 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.
110 119 Selvarani C
111 119 Selvarani C
+Geometry types-+
112 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).
113 119 Selvarani C
114 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.
115 119 Selvarani C
116 119 Selvarani C
+Using Feature lines for creating Curved geometries in 3D-+
117 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 :-
118 119 Selvarani C
119 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.
120 119 Selvarani C
121 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.
122 119 Selvarani C
123 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.
124 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.
125 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.
126 119 Selvarani C
Situations of sharing of points with different layers and proceeding with linework in such circumstances-
127 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. 
128 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).
129 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. 
130 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. 
131 119 Selvarani C
132 119 Selvarani C
*+Purpose of Survey+*
133 119 Selvarani C
134 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.
135 119 Selvarani C
136 119 Selvarani C
137 119 Selvarani C
+Use of Layers+
138 119 Selvarani C
139 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.
140 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.
141 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.
142 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.
143 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.
144 119 Selvarani C
# Use of *V-ROAD-CYCP* is for designated cycle path as a single line.
145 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.
146 119 Selvarani C
# *V-WMNG-PIPP* for pipe points, *V-WMNG-PIPL*- for pipe lines.
147 119 Selvarani C
# *V-BLDG-BMRK* is for unidentified bench marks and *V-BLDG-MHOL* is for unidentified manholes.
148 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.
149 119 Selvarani C
# *V-WMNG-POOL* is for water bodies made for leisure activities- like swimming pool etc.
150 119 Selvarani C
# *V-WMNG-SUMP* is collectively for artificial water retention structures.
151 119 Selvarani C
# *V-WATR-POND* is for top of natural water retention.
152 119 Selvarani C
# *V-WATR-PONB* is for bottom of natural water retention.
153 119 Selvarani C
# *V-WMNG-DRBA* is for bottom of artificial drains.
154 119 Selvarani C
# *V-WMNG-DRTA* is for top of artificial drains.
155 119 Selvarani C
# *V-WATR-DRBN* is for bottom of Natural drains.
156 119 Selvarani C
# *V-WATR-DRTN* is for top of Natural drains.
157 120 Selvarani C
# *V-WMNG-DRNC* is for drain covers.
158 1 Philippe May
# *V-WATR-DRAS* is for indicating slope of drainage, these are arrows.
159 120 Selvarani C
160 167 Selvarani C
161 121 Selvarani C
162 123 Selvarani C
163 169 Selvarani C
164 125 Selvarani C
165 125 Selvarani C
166 125 Selvarani C
167 170 Selvarani C
h1. *Reconcilation of Raw survey data using pgAdmin*
168 126 Selvarani C
169 126 Selvarani C
+For changing the layer codes, to be done using Pgadmin.+
170 126 Selvarani C
171 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.
172 126 Selvarani C
173 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).
174 126 Selvarani C
175 126 Selvarani C
h3.  Other > Project > select the project > with selected> reconcile RAW survey points.
176 126 Selvarani C
177 127 Selvarani C
h1. Importing point data (TS and RTK) to GISAF 
178 127 Selvarani C
179 127 Selvarani C
# *Gisaf Admin > Basket > Survey data > "Project" > "surveyor" > TS/ RTK > upload > import.*
180 127 Selvarani C
# *Auto import of Raw points data* (changes from Raw to Shapefiles, the point files)
181 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...
182 127 Selvarani C
183 172 Selvarani C
184 128 Selvarani C
185 128 Selvarani C
h1. Editing Z value of features in Shapefiles in QGIS
186 128 Selvarani C
187 128 Selvarani C
h2. using vertex editor tool - https://www.youtube.com/watch?v=8V8i1AtcA74&t=256s
188 128 Selvarani C
189 129 Selvarani C
h1. Miscellaneous- Civil 3D
190 129 Selvarani C
191 129 Selvarani C
*Autodesk civil 3D Geotechnical module- for borehole data :- To analyse borehole data, To make profiles and calculate volumes*
192 129 Selvarani C
193 129 Selvarani C
https://www.youtube.com/watch?v=0Be9kShBou0
194 129 Selvarani C
Reference videos
195 129 Selvarani C
Exploring:
196 129 Selvarani C
https://www.youtube.com/watch?v=gr-ISPzLcU0
197 129 Selvarani C
Modelling:
198 129 Selvarani C
https://www.youtube.com/watch?v=Pz0-HOoiBrs
199 129 Selvarani C
solids
200 129 Selvarani C
https://www.youtube.com/watch?v=mQ0Yeh6tZA8
201 129 Selvarani C
https://www.youtube.com/watch?v=4eMsUiYBhuE
202 129 Selvarani C
203 129 Selvarani C
204 129 Selvarani C
*CIVIL 3D Survey*
205 129 Selvarani C
Getting started- Always open a new drawing with a template. 
206 129 Selvarani C
207 129 Selvarani C
*Description key sets*- (till 18:30) https://www.youtube.com/watch?v=mmwkkRyBkS0
208 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.
209 129 Selvarani C
Tool space > settings > points > description key sets
210 129 Selvarani C
“Description key sets name”> edit key- to view the points in a list: 
211 129 Selvarani C
Automatic linework (18:30- till end)
212 129 Selvarani C
Survey > Linework code sets- for automatic linework
213 129 Selvarani C
214 129 Selvarani C
*Using Master view*
215 129 Selvarani C
Uses-
216 129 Selvarani C
copy styles from one drawing to other
217 129 Selvarani C
copy drawing data from one drawing to other (data referencing)
218 129 Selvarani C
219 129 Selvarani C
*Civil 3d surface model*- from points- break lines
220 129 Selvarani C
https://www.youtube.com/watch?v=wC40rdmDEMo
221 129 Selvarani C
moving for example- point groups under point groups- 
222 129 Selvarani C
223 129 Selvarani C
*Civil 3D Planning and Analysis*
224 129 Selvarani C
Workspace: Planning and Analysis
225 129 Selvarani C
1. Working with Object data (GIS Attributes)
226 129 Selvarani C
Map Setup> Define object data> New table> Define new object data table start defining fields
227 129 Selvarani C
228 129 Selvarani C
229 130 Selvarani C
230 130 Selvarani C
h1. Documentation- Rain Gauge
231 130 Selvarani C
232 130 Selvarani C
h2. Manual Rain Gauge
233 130 Selvarani C
234 130 Selvarani C
*Why it is important to comply to standards?*
235 130 Selvarani C
236 130 Selvarani C
1. Consistency for comparing rainfall data in different places within Auroville since rainfall varies in different parts of Auroville.
237 130 Selvarani C
238 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. 
239 130 Selvarani C
240 130 Selvarani C
*Proposed standards and ethics:*
241 130 Selvarani C
242 130 Selvarani C
1. The time of taking the reading - 08:30 am. 
243 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.
244 130 Selvarani C
245 130 Selvarani C
2. Manual rain gauge typically used- green cylindrical and a collection jar.  
246 130 Selvarani C
  
247 130 Selvarani C
3. Measuring jar: 10 mm corresponding jar
248 130 Selvarani C
249 130 Selvarani C
 
250 130 Selvarani C
Area of the rim of manual rain gauge= 200 square cm
251 130 Selvarani C
Diameter of rim= approximately 16 cm
252 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.
253 130 Selvarani C
254 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.
255 130 Selvarani C
256 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.
257 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.
258 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. 
259 130 Selvarani C
260 130 Selvarani C
8. In case of doubt in reading or incorrect measure, "incorrect measure" should be marked
261 130 Selvarani C
262 130 Selvarani C
263 130 Selvarani C
*Ethics*
264 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). 
265 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. 
266 130 Selvarani C
267 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. 
268 130 Selvarani C
269 130 Selvarani C
*Important-*
270 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.
271 130 Selvarani C
CSR Geomatics Team is placed on first floor in CSR, Auroshilpam.
272 130 Selvarani C
273 130 Selvarani C
*AV rain data publication*: (http://gis.auroville.org.in/measures/raingauge_av).
274 130 Selvarani C
275 130 Selvarani C
Adding Rain gauge to our web portal (GISAF), following information is needed:
276 130 Selvarani C
1. GPS co-ordinates of location of placing the rain gauge (can be obtained using mobile phones easily)
277 130 Selvarani C
2. Name, place of residence & contact number- Mobile & Landline
278 130 Selvarani C
279 130 Selvarani C
h2. Automatic Rain Gauge
280 130 Selvarani C
281 130 Selvarani C
There is a possibility of publishing rain data coming from Automatic rain gauges like (id 15, auro orchard) and Weather stations. 
282 130 Selvarani C
For Automatic rain gauges, we can upload the files coming from the rain gauge directly into GISAF.
283 130 Selvarani C
284 130 Selvarani C
285 130 Selvarani C
_Thank you for contribution towards a sustainable management of Water in Auroville through Data collection._
286 130 Selvarani C
287 130 Selvarani C
288 131 Selvarani C
289 131 Selvarani C
h1. Documentation- Wells Monitoring (Manual and Automatic / Piezometer by Bala)
290 131 Selvarani C
291 131 Selvarani C
h2. Manual- Using tape with a sensor
292 131 Selvarani C
293 131 Selvarani C
Timings: The person assigned the job of monitoring collects the readings in three slots.
294 131 Selvarani C
295 131 Selvarani C
1.	Between 6 am to 7 am till about 9 am to 10 am.
296 131 Selvarani C
2.	Between 11 am and 1 pm
297 131 Selvarani C
3.	Between 2 pm and 5 pm
298 131 Selvarani C
299 131 Selvarani C
Things required:
300 131 Selvarani C
•	Notebook
301 131 Selvarani C
•	Pen
302 131 Selvarani C
•	Measuring tape
303 131 Selvarani C
•	Vehicle for movement
304 131 Selvarani C
305 131 Selvarani C
306 131 Selvarani C
*Ethics*- 
307 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.
308 131 Selvarani C
•	The monitor should have contact numbers of the person in charge/ care taker for any communication.
309 131 Selvarani C
•	If the monitoring is stopped for any reason at any point, the monitor should communicate the same to the person concerned.
310 131 Selvarani C
•	The monitor shall take responsibility to inform any kind of changes in a well in terms of its functioning etc.
311 131 Selvarani C
•	The monitor should report to the CSR Geomatics Team who has responsibility to publish data.
312 131 Selvarani C
•	The monitor published the data to the website and works with the geomatics team.
313 131 Selvarani C
314 131 Selvarani C
315 131 Selvarani C
*Definitions*:
316 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. 
317 131 Selvarani C
318 131 Selvarani C
*Well type*
319 131 Selvarani C
1.	Open
320 131 Selvarani C
2.	Borewell
321 131 Selvarani C
3.	Dug cum borewell
322 131 Selvarani C
323 131 Selvarani C
*Well status*
324 131 Selvarani C
1.	In use
325 131 Selvarani C
2.	Not in use
326 131 Selvarani C
3.	Closed
327 131 Selvarani C
328 131 Selvarani C
*Pump Status*
329 131 Selvarani C
1.	Functioning
330 131 Selvarani C
2.	Not functioning
331 131 Selvarani C
332 131 Selvarani C
*Pump Automation*
333 131 Selvarani C
1.	Manual 
334 131 Selvarani C
2.	Automatic
335 131 Selvarani C
336 131 Selvarani C
* Non-accessibility factors*
337 131 Selvarani C
1.	Dogs
338 131 Selvarani C
2.	Heavy slab
339 131 Selvarani C
3.	Narrow casing
340 131 Selvarani C
4.	enclosed/locked
341 131 Selvarani C
5.	permission
342 131 Selvarani C
343 131 Selvarani C
*Data Matching Accuracy (reconnecting with harvest wells data)*
344 131 Selvarani C
1.	High
345 131 Selvarani C
2.	Medium
346 131 Selvarani C
3.	Low
347 131 Selvarani C
348 131 Selvarani C
*Well coordinates*
349 131 Selvarani C
For a new well, coordinates of the well position are taken on a mobile GPS.
350 131 Selvarani C
Person In charge
351 131 Selvarani C
For communication purpose, contact the person in charge as recorded in directory.
352 131 Selvarani C
353 131 Selvarani C
h2. Automatic- Piezometer (by bala, to be edited) 
354 131 Selvarani C
355 131 Selvarani C
The calibrations and setting are already done by Azha
356 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
357 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
358 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.
359 131 Selvarani C
The piezometer sometimes does not have proper signal and so it would not be able to send it
360 131 Selvarani C
361 132 Selvarani C
h1. Documentation- Flow meter by Bala
362 132 Selvarani C
363 132 Selvarani C
Flow meter – for checking the flow of water in pipe
364 132 Selvarani C
365 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.
366 132 Selvarani C
we tested in the west water system pump in csr. then we test in many more place .
367 132 Selvarani C
 ami, aurodam and buddha garden borewell pumps . we got request from the water service 
368 132 Selvarani C
Cross check they flow meters .
369 132 Selvarani C
 so before that  we want to know how our meter works. 
370 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. 
371 132 Selvarani C
we tested two times in  15 minutes.and one time 30 minutes,so we got variation between this three. 
372 132 Selvarani C
we find 1,5 % error but the flow meret they said  1 % error only.
373 132 Selvarani C
we cross checked the flow meter of the water service we find some error  in they meter also. 
374 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.  
375 132 Selvarani C
then we find some error in (AVWS) meter also.
376 132 Selvarani C
It is used to check the flow of water in pipe
377 132 Selvarani C
tools used 
378 132 Selvarani C
First the outer diameter of the pipe has to be entered in the device. It is measured using Vernier caliper
379 132 Selvarani C
Then the thickness of the pipe is set which is also measured using vernier
380 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) 
381 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
382 132 Selvarani C
When the sensors are fixed the motor is turned on and the sensors send reading to the display device
383 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.
384 1 Philippe May
This was done in different places to check to flow rate
385 132 Selvarani C
386 177 Selvarani C
387 133 Selvarani C
388 133 Selvarani C
h1. Documentation- DST- Vegetation Indexing
389 133 Selvarani C
390 133 Selvarani C
h2. Steps for Dzetsaka Classification tool for Vegetation indexing in QGIS
391 133 Selvarani C
392 133 Selvarani C
 
393 133 Selvarani C
 1. Install the plugin Dzetsaka classfication tool.
394 133 Selvarani C
 2. Open the Raster from the Survey.
395 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. 
396 133 Selvarani C
     More the samples, better the indexing.
397 133 Selvarani C
 4. Apply Dzetsaka Classification tool, Select the base raster and the sample- index polygon shapefile created in step 3.
398 133 Selvarani C
 5. The result is a Raster with DN numbers specified in the Shapefile in step 3.
399 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.
400 133 Selvarani C
 7. Polygonise the Raster to Vector (From processing)
401 133 Selvarani C
 8. Run the v.generalise tool on the shapefile. This tool removes the pixelated boundaries of the polygons in the Vector.
402 133 Selvarani C
403 134 Selvarani C
h1. Documentation- DST- Interpolation (Processing toolbox)
404 134 Selvarani C
405 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)* )
406 134 Selvarani C
407 134 Selvarani C
# Interpolate (Cubic spline) - SAGA
408 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.
409 134 Selvarani C
# V.surf.rst - GRASS
410 134 Selvarani C
# Krigging - SAGA
411 1 Philippe May
412 181 Selvarani C
[[Documentation- DST- Survey- Office workflow]]  - *%{color:RED} to be written%*
413 135 Selvarani C
414 135 Selvarani C
h1. From CAD to GIS by Giulio
415 135 Selvarani C
416 135 Selvarani C
*FEATURES CREATION*
417 135 Selvarani C
1.	Assign a CRS to the drawing (TM-AUSPOS) (MAPCSLIBRARY command)
418 135 Selvarani C
2.	Create features in CAD (Points, lines, polygons)
419 135 Selvarani C
3.	Export shapefile (a) from CAD (Output > DWG to SDF) (Convert to LL84 – 3D)
420 135 Selvarani C
421 135 Selvarani C
*FEATURES IMPORT INTO DB FIRST TIME*
422 135 Selvarani C
4.	Create zip file of the shapefile
423 135 Selvarani C
5.	Upload into the GISAF Shapefiles Basket
424 135 Selvarani C
6.	Import the shapefile into DB
425 135 Selvarani C
7.	Save the shapefile on Local Machine
426 135 Selvarani C
427 135 Selvarani C
*FEATURES IMPORT INTO DB EVERYTIME*
428 135 Selvarani C
8.	Combine the new features to corresponding last shape files (Insert the process here).
429 135 Selvarani C
9.	Follow step 4-8 again
430 135 Selvarani C
431 135 Selvarani C
*FEATURES EDITING IN QGIS*
432 135 Selvarani C
10.	Open the table in QGis
433 135 Selvarani C
11.	Save as a shapefile (b) in TM AUSPOS CRS
434 135 Selvarani C
12.	In CAD, open a new drawing and assign AUSPOS CRS
435 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
436 135 Selvarani C
14.	Edit features
437 135 Selvarani C
15.	Change workspace into “Planning and analysis”
438 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)
439 135 Selvarani C
440 135 Selvarani C
*FEATURES IMPORT INTO DB*
441 135 Selvarani C
17.	Create zip file of the shapefile
442 135 Selvarani C
18.	Upload into the GISAF Shapefiles Basket
443 135 Selvarani C
19.	Import the shapefile into DB
444 135 Selvarani C
20.	Delete the shapefile from Local Machine
445 135 Selvarani C
446 135 Selvarani C
447 182 Selvarani C
448 1 Philippe May
449 136 Selvarani C
h1. QGIS- Miscellaneous
450 136 Selvarani C
451 136 Selvarani C
*QGIS Introduction:*
452 136 Selvarani C
https://www.birdseyeviewgis.com/blog/2018/2/22/my-favorite-features-of-qgis-30to-date
453 136 Selvarani C
3D visualization of raster DEM- https://www.youtube.com/watch?v=2KrCsbP0kUs
454 136 Selvarani C
455 136 Selvarani C
*Spatial query:* 
456 136 Selvarani C
Spatial Query is selection of features that satisfies a certain condition which relates to other features in a space.
457 136 Selvarani C
Using plugin- Spatial query
458 136 Selvarani C
http://www.geodose.com/2018/03/spatial-query-in-qgis-3.html
459 136 Selvarani C
Labelling:
460 136 Selvarani C
Labelling with more than one field names and in different lines
461 136 Selvarani C
|| '\n' ||
462 136 Selvarani C
463 136 Selvarani C
464 136 Selvarani C
465 136 Selvarani C
*Hierarchy of extensions*
466 136 Selvarani C
467 136 Selvarani C
File levels and their uses.
468 136 Selvarani C
https://nathanw.net/2014/03/22/all-the-q-files/
469 136 Selvarani C
470 136 Selvarani C
+The Project file (.qgs)+
471 136 Selvarani C
It contains: Layer source pointer + Style information + Composers + a whole heap of other stuff
472 136 Selvarani C
473 136 Selvarani C
+The Layer Definition file (.qlr)+
474 136 Selvarani C
It contains: Layer source pointer + Style information
475 136 Selvarani C
476 136 Selvarani C
+The QML file (.qml)+
477 136 Selvarani C
It contains: Style information
478 136 Selvarani C
479 59 Giulio Di Anastasio
h2. Giulio's documentation
480 52 Giulio Di Anastasio
481 183 Selvarani C
482 137 Selvarani C
483 137 Selvarani C
h1. Documentation - Reconciliation of points using Gisaf
484 137 Selvarani C
485 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.
486 137 Selvarani C
487 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).
488 137 Selvarani C
489 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]].
490 137 Selvarani C
491 137 Selvarani C
492 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.
493 137 Selvarani C
494 137 Selvarani C
495 137 Selvarani C
PLEASE NOTE: 
496 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+*.
497 137 Selvarani C
498 137 Selvarani C
h2. How to perform Reconciliation
499 137 Selvarani C
500 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
501 137 Selvarani C
502 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).
503 137 Selvarani C
504 137 Selvarani C
Under it, in the field "Original ID", the original point number of the point to be reconciled is to be entered.
505 137 Selvarani C
506 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.
507 137 Selvarani C
508 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.
509 137 Selvarani C
510 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.
511 137 Selvarani C
512 138 Selvarani C
h1. Documentation - Status and Status Changes
513 138 Selvarani C
514 138 Selvarani C
Status have been created to keep track og changes in surveyed features.
515 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.
516 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.
517 138 Selvarani C
518 138 Selvarani C
Status have been defined as follows:
519 138 Selvarani C
N - New Work
520 138 Selvarani C
E - Existing o remain
521 138 Selvarani C
D - Existing to demolish, Demolished or Changed
522 138 Selvarani C
F- Future work, Proposed feature
523 138 Selvarani C
T - Temporary work
524 138 Selvarani C
M - Item to be moved
525 138 Selvarani C
X - Not in contract
526 138 Selvarani C
527 138 Selvarani C
528 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).
529 138 Selvarani C
It needs to be done manually, one feature (point, line, polygon) at a time.
530 138 Selvarani C
531 138 Selvarani C
532 1 Philippe May
In the future Status changes might be incorporated in the Admin panel.
533 138 Selvarani C
534 185 Selvarani C
535 67 Giulio Di Anastasio
536 139 Selvarani C
h1. Documentation - Tags retained after re-import of same geometry
537 139 Selvarani C
538 139 Selvarani C
Documentation - Tags retained after re-import of same geometry
539 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.
540 139 Selvarani C
The result was that lines did not inherit the attributes survey date, accuracy, equipment, surveyor.
541 139 Selvarani C
Nevertheless lines were displayed on the Gisaf map, without these attributes, and tags were given to some of these lines.
542 139 Selvarani C
543 139 Selvarani C
The values for the two tables ("Accuracy", "Accuracy") have been corrected, ambiguity resolved.
544 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.
545 139 Selvarani C
546 139 Selvarani C
4 August 2020
547 139 Selvarani C
548 67 Giulio Di Anastasio
h1. Access to data
549 67 Giulio Di Anastasio
550 67 Giulio Di Anastasio
h2. Connection to server directly from CSR
551 67 Giulio Di Anastasio
552 67 Giulio Di Anastasio
To connect to the server directly without going through Aurinoco server, the correct url is
553 67 Giulio Di Anastasio
http://gis.csr.av
554 67 Giulio Di Anastasio
555 67 Giulio Di Anastasio
h2. Connection to Gisaf via QGis through WFS / OGC API
556 67 Giulio Di Anastasio
557 67 Giulio Di Anastasio
This works only on QGis from version 3.14.15 onward
558 67 Giulio Di Anastasio
559 67 Giulio Di Anastasio
In the browser, click on WFS/OGC API, then right-click to create a new connection
560 67 Giulio Di Anastasio
Give a name (e.g. OGC API Qgis Gisaf)
561 67 Giulio Di Anastasio
Give the url https://gis.auroville.org.in/ogcapi
562 67 Giulio Di Anastasio
563 67 Giulio Di Anastasio
Under the WFS Options box, on Version dropdown, the default option "Maximum" works just fine
564 67 Giulio Di Anastasio
Click on OK
565 67 Giulio Di Anastasio
The list of layers will appear in the Browser under WFS/OGC API.
566 68 Giulio Di Anastasio
567 68 Giulio Di Anastasio
568 68 Giulio Di Anastasio
h1. How to create a new projection in QGis
569 68 Giulio Di Anastasio
570 68 Giulio Di Anastasio
To create a new projection in QGis, go to menu "Settings", and click on "Custom Projections".
571 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.
572 68 Giulio Di Anastasio
Click on the green "+" sign on the right top part of the window to create a new projection.
573 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).
574 68 Giulio Di Anastasio
In the "Format" dropdown list, select "Proj String (legacy - Not Recommended)"
575 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".
576 68 Giulio Di Anastasio
577 68 Giulio Di Anastasio
Finally, click on OK.
578 68 Giulio Di Anastasio
579 68 Giulio Di Anastasio
In a more explicit  way, the parameters mean the following:
580 68 Giulio Di Anastasio
Map Projection:        TransverseMercator (TM)
581 68 Giulio Di Anastasio
False Easting:          370455.6300
582 68 Giulio Di Anastasio
False Northing:        1328608.9940
583 68 Giulio Di Anastasio
Latitude of Origin:    12°00'57.79560" (DMS)   12.01605433 (DD)
584 68 Giulio Di Anastasio
Central Meridian:     79°48'35.96164"  (DMS)   79.80998934 (DD)
585 68 Giulio Di Anastasio
Scale Factor:             1.00000000
586 68 Giulio Di Anastasio
Zone Width:              6.0°
587 69 Giulio Di Anastasio
588 69 Giulio Di Anastasio
h1. Elimination of Duplicate points – General criteria
589 69 Giulio Di Anastasio
590 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.
591 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.
592 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.
593 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.
594 69 Giulio Di Anastasio
How to identify duplicate points?
595 69 Giulio Di Anastasio
The following criteria can be used:
596 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)
597 69 Giulio Di Anastasio
2.	The orig_id (serial number) of the points are not in series
598 69 Giulio Di Anastasio
3.	The survey date is not the same
599 69 Giulio Di Anastasio
4.	In case of trees, the species of trees is the same
600 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)
601 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.
602 70 Giulio Di Anastasio
603 70 Giulio Di Anastasio
604 70 Giulio Di Anastasio
h1. Linework for the Survey Area
605 70 Giulio Di Anastasio
606 70 Giulio Di Anastasio
h2. 1.	Creation of Initial Linework in QGIS using Survey points import - (Ram, System 4)
607 70 Giulio Di Anastasio
608 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.
609 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*.
610 70 Giulio Di Anastasio
The Initial Linework for the Survey Area is also stored temporarily in 
611 70 Giulio Di Anastasio
612 74 Selvarani C
+D: > AVSM > Zone-Survey number (eg RZ-01) > Survey Area (eg J) > Temporary WD+
613 70 Giulio Di Anastasio
614 70 Giulio Di Anastasio
h2. Note: The line shapefiles / Geopackages shall be in CRS: TM AUSPOS
615 70 Giulio Di Anastasio
616 70 Giulio Di Anastasio
h2. 2.	Creation of final working drawing Shapefiles / Geopackages - (Selvarani, System 1)
617 1 Philippe May
618 1 Philippe May
Final working drawing Shapefiles / Geopackages are created from the Initial Linework of Survey Area.
619 70 Giulio Di Anastasio
As the Surveyor draws all features as lines (both for lines and polygons features), the following actions shall be done:
620 74 Selvarani C
1.	*If features are lines:*
621 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).
622 70 Giulio Di Anastasio
623 70 Giulio Di Anastasio
h2. The CRS for the export shall be EPSG:4326 - WGS 84
624 70 Giulio Di Anastasio
625 74 Selvarani C
2.	*If features are polygons:*
626 1 Philippe May
•	Lines shall be converted into polygons:
627 74 Selvarani C
628 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:
629 87 Selvarani C
630 84 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9760/Line%20to%20Polygon%20Menu.png!
631 70 Giulio Di Anastasio
632 86 Selvarani C
633 1 Philippe May
The new window for “Lines to Polygons” conversion will appear:
634 86 Selvarani C
635 86 Selvarani C
636 83 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9762/Lines%20to%20Polygon%20Window.png!
637 1 Philippe May
638 71 Giulio Di Anastasio
•	Always cross check the input layer, to make sure that the input layer is the active one
639 71 Giulio Di Anastasio
•	Save the output in a temporary layer
640 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)
641 72 Giulio Di Anastasio
642 74 Selvarani C
h2. The CRS for the export shall be EPSG:4326 - WGS 84
643 74 Selvarani C
644 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.
645 1 Philippe May
646 74 Selvarani C
h2. Linework for the whole Survey Zone
647 74 Selvarani C
648 74 Selvarani C
h2. 1.	Merging Shapefiles / Geopackages - (Selvarani, System 1)
649 74 Selvarani C
650 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.
651 1 Philippe May
Master shapefiles / geopackages are merged with the Survey Area shapefiles / geopackages:
652 72 Giulio Di Anastasio
•	To do it, go to “Vector” Menu, click on Geoprocessing Tools, then click on Union:
653 72 Giulio Di Anastasio
654 85 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9763/Union%20Menu.png!
655 1 Philippe May
656 1 Philippe May
657 85 Selvarani C
The new window for “Union” will appear:
658 1 Philippe May
659 86 Selvarani C
660 86 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9764/Union%20Window.png!
661 73 Giulio Di Anastasio
662 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).
663 73 Giulio Di Anastasio
•	(The output can be saved to a file, as the CRS should already be EPSG4326 – WGS84.)
664 73 Giulio Di Anastasio
665 74 Selvarani C
h2. 2.	Storing Shapefiles / Geopackages - (Selvarani, System 1)
666 74 Selvarani C
667 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)
668 73 Giulio Di Anastasio
Date in the name of Final Shapefile / Geopackage needs to be updated.
669 73 Giulio Di Anastasio
Once the merging operation is completed, the copy of Master shapefile / geopackage is deleted from the Temp folder.
670 73 Giulio Di Anastasio
671 74 Selvarani C
h2. 3.	Topology check of merged shapefiles
672 74 Selvarani C
673 73 Giulio Di Anastasio
The topology checker is applied again on the merged shapefiles / geopackages.
674 73 Giulio Di Anastasio
The “id_field” shall be removed from the attribute table.
675 73 Giulio Di Anastasio
676 74 Selvarani C
h2. 4.	Archive and replace the Master Shapefiles / Geopackages (Ram, System 4)
677 74 Selvarani C
678 73 Giulio Di Anastasio
Archive the previous master shapefiles / geopackages on system 4, and copy the new merged shapefiles / geopackages in its place.
679 74 Selvarani C
*Then delete the Merged Shapefile / Geopackage folder from System 1.
680 74 Selvarani C
*
681 73 Giulio Di Anastasio
682 74 Selvarani C
h2. 5.	Note about Shapefiles and Geopackages
683 73 Giulio Di Anastasio
684 73 Giulio Di Anastasio
All the above works are usually done using shapefile format, in QGIS latest version (3.16.3).
685 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.
686 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).
687 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)
688 223 Selvarani C
689 223 Selvarani C
h1. Creating 3D Shapefile/Geopackage
690 223 Selvarani C
691 223 Selvarani C
While creating a Shapefile/Geopackage, the File name/Database-table name, Geometry type and CRS have to be entered.
692 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).
693 224 Giulio Di Anastasio
694 224 Giulio Di Anastasio
h1. Exporting from QGis (shapefiles and/or geopackages) to CAD dxf format
695 224 Giulio Di Anastasio
696 226 Giulio Di Anastasio
An algorithm has been created by Selvarani, to see the whole process click here:
697 226 Giulio Di Anastasio
https://redmine.auroville.org.in/projects/gis/wiki/Automatic_export_from_QGis_to_dxf