Project

General

Profile

Wiki » History » Version 230

Giulio Di Anastasio, 03/05/2021 09:57

1 1 Philippe May
h1. %{color:BLUE}  Wiki%
2 227 Giulio Di Anastasio
3 227 Giulio Di Anastasio
h1. [[CSR Geomatics Team]]
4 2 Philippe May
5 229 Giulio Di Anastasio
h1. [[Collaborations]]
6 229 Giulio Di Anastasio
7 48 Philippe May
8 48 Philippe May
9 88 Selvarani C
10 186 Selvarani C
h1. Our workflow
11 92 Selvarani C
12 92 Selvarani C
h2. Surveys
13 92 Selvarani C
14 92 Selvarani C
Most field surveys are executed by our team of surveyors, using advanced DGPS equipment.
15 92 Selvarani C
Other surveyors might also be contracted.
16 92 Selvarani C
17 92 Selvarani C
18 92 Selvarani C
h2. CAD
19 92 Selvarani C
20 92 Selvarani C
The survey data are imported to a CAD software (Aurocad/Civil 3D).
21 93 Selvarani C
22 187 Selvarani C
h2. Editing shapefiles in Autocad
23 93 Selvarani C
24 93 Selvarani C
h2. FEATURES CREATION
25 93 Selvarani C
26 93 Selvarani C
1.	Assign a CRS to the drawing (TM-AUSPOS) (MAPCSLIBRARY command)
27 93 Selvarani C
2.	Create features in CAD (Points, lines, polygons)
28 93 Selvarani C
3.	Export shapefile (a) from CAD (Output > DWG to SDF) (Convert to LL84 – 3D)
29 93 Selvarani C
30 93 Selvarani C
h2. FEATURES IMPORT INTO DB
31 93 Selvarani C
32 93 Selvarani C
4.	Create zip file of the shapefile
33 93 Selvarani C
5.	Upload into the GISAF Shapefiles Basket
34 93 Selvarani C
6.	Import the shapefile into DB
35 93 Selvarani C
7.	Delete the shapefile from Local Machine
36 93 Selvarani C
37 93 Selvarani C
38 93 Selvarani C
h2. FEATURES EDITING
39 93 Selvarani C
40 93 Selvarani C
8.	Open the table in QGis
41 93 Selvarani C
9.	Save as a shapefile (b) in TM AUSPOS CRS
42 93 Selvarani C
10.	In CAD, open a new drawing and assign ASUPOS CRS
43 93 Selvarani C
11.	Import the shapefile (b) (MapImport) with all Object Data
44 93 Selvarani C
12.	Edit features
45 93 Selvarani C
13.	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)
46 93 Selvarani C
47 93 Selvarani C
48 93 Selvarani C
h2. FEATURES IMPORT INTO DB
49 93 Selvarani C
50 93 Selvarani C
14.	Create zip file of the shapefile
51 93 Selvarani C
15.	Upload into the GISAF Shapefiles Basket
52 93 Selvarani C
16.	Import the shapefile into DB
53 93 Selvarani C
17.	Delete the shapefile from Local Machine
54 92 Selvarani C
55 96 Selvarani C
 
56 92 Selvarani C
57 92 Selvarani C
h2. QGis
58 92 Selvarani C
59 2 Philippe May
h3. Conventions
60 3 Philippe May
61 94 Selvarani C
h1. Shapefiles
62 94 Selvarani C
63 94 Selvarani C
We work with "QGis":https://en.wikipedia.org/wiki/QGIS , a widely used open source, free software for working on maps and geographical data.
64 94 Selvarani C
65 94 Selvarani C
"Shapefile":https://en.wikipedia.org/wiki/Shapefile is a standard file format for mapping, that Gisaf can import. QGis can open and save *shapefiles*.
66 94 Selvarani C
67 94 Selvarani C
We have defined some simple norms about these shapefiles for integration with Gisaf.
68 94 Selvarani C
69 94 Selvarani C
70 94 Selvarani C
71 94 Selvarani C
h2. Coordinate system
72 94 Selvarani C
73 94 Selvarani C
We use CRS SRID 32644.
74 94 Selvarani C
75 94 Selvarani C
76 94 Selvarani C
77 94 Selvarani C
h2. Column (attributes)
78 94 Selvarani C
79 94 Selvarani C
* All objects in a shapefile (layer) have a unique identifier named "id": numerical value.
80 94 Selvarani C
81 94 Selvarani C
82 94 Selvarani C
83 94 Selvarani C
h3. Field (attribute) names
84 94 Selvarani C
85 94 Selvarani C
* All fields are lower case (-UpperCase-, use: @lowercase@)
86 94 Selvarani C
87 94 Selvarani C
* They do not contain spaces, but underscores (-not this-, use: @but_that@)
88 94 Selvarani C
89 94 Selvarani C
* The field names cannot have more than 8 characters (-this_is_too_long-, use: @this_short@)
90 94 Selvarani C
91 94 Selvarani C
92 94 Selvarani C
h3. Attribute types
93 94 Selvarani C
94 94 Selvarani C
* The dates are written in ISO format: @YYYY-MM-DD@ (eg. @1968-02-25@)
95 94 Selvarani C
96 94 Selvarani C
h3. Fields to remove
97 94 Selvarani C
98 94 Selvarani C
* Eventually, remove the fields containing the coordinates: northing, easting, elevation, latitude, longitude, area, length, etc (these might be present when the data is imported from speadsheet)
99 94 Selvarani C
100 94 Selvarani C
h2. Foreign keys
101 94 Selvarani C
102 94 Selvarani C
We often deal with labels or categories of objects in a layer.
103 94 Selvarani C
104 94 Selvarani C
A common use case to explain: Alice creates a layer of stones, and wants to *tag* each stone with a rating: these are picked from a list of choices, like: _Beautiful_, _Interesting_, _Pretty_, etc.
105 94 Selvarani C
106 94 Selvarani C
For these kind of attribute: define a column like @rating_id@ (_something_ ending with @_id@) as a numerical value, and assign values 1, 2, 3, etc. The text is defined in another table (typically a CSV file), that looks like:
107 94 Selvarani C
108 94 Selvarani C
|_. id |_. name |
109 94 Selvarani C
| 1 | Beautiful |
110 94 Selvarani C
| 2 | Interesting |
111 94 Selvarani C
| 3 | Pretty |
112 94 Selvarani C
113 94 Selvarani C
h2. Code
114 94 Selvarani C
115 94 Selvarani C
We have defined a standard set of codes, that defines the type of data. They can be found here (TODO: add link).
116 94 Selvarani C
117 94 Selvarani C
Add a column @code_name@, matching with one the code, eg. @V25@ for TDEF.
118 94 Selvarani C
119 94 Selvarani C
h2. Surveyor
120 94 Selvarani C
121 94 Selvarani C
We keep a record of the people who realized the surveys (the _surveyors_).
122 94 Selvarani C
The shapefiles must contain an attribute @srvyr_id@, which refers to this table (TODO: add link).
123 94 Selvarani C
124 94 Selvarani C
h2. Accuracy
125 94 Selvarani C
126 94 Selvarani C
We keep a record of the accuracy of the surveys.
127 94 Selvarani C
The shapefiles must contain an attribute @accur_id@, which refers to this table (TODO: add link).
128 94 Selvarani C
129 94 Selvarani C
130 94 Selvarani C
h2. Date of survey
131 94 Selvarani C
132 94 Selvarani C
As nothing is absolutely permanent, it's also important to keep track of the date of the surveys: the shapefiles must contain an attribute @date@.
133 94 Selvarani C
134 188 Selvarani C
h1. Working with Gisaf
135 3 Philippe May
136 6 Philippe May
h3. Survey data
137 6 Philippe May
138 12 Philippe May
Raw survey data are contained in CSV files, typically downloaded from surveying instruments.
139 12 Philippe May
140 144 Selvarani C
See more information of the process for the survey data (including a flow diagram)
141 12 Philippe May
142 97 Selvarani C
h1. Survey data
143 97 Selvarani C
144 97 Selvarani C
h2. Workflow summary
145 97 Selvarani C
146 190 Selvarani C
p=. !https://redmine.auroville.org.in/attachments/download/9839/Survey_data.jpg!
147 97 Selvarani C
148 97 Selvarani C
h2. Import basket
149 97 Selvarani C
150 97 Selvarani C
Gisaf provides an "import basket" dedicated for raw survey data, which is generated by land survey equipment (Leica's Total Station and RTK). 
151 97 Selvarani C
152 97 Selvarani C
These are CSV files, like:
153 97 Selvarani C
<pre>
154 97 Selvarani C
100081,370633.969,1327742.157,51.187,,,
155 97 Selvarani C
100083,370628.876,1327702.913,51.565,T52,,
156 97 Selvarani C
100082,370628.729,1327720.019,51.261,T52,,
157 97 Selvarani C
100081,370633.969,1327742.154,51.179,,,
158 97 Selvarani C
100083,370628.876,1327702.913,51.565,T52,,
159 97 Selvarani C
20800,370633.969,1327742.154,51.180,,,
160 97 Selvarani C
20801,370618.795,1327713.172,52.817,E30,,
161 97 Selvarani C
20802,370623.674,1327711.436,51.283,B35,,
162 97 Selvarani C
20803,370619.314,1327713.407,51.383,B35,,
163 97 Selvarani C
</pre>
164 97 Selvarani C
165 97 Selvarani C
Each category (5th column) must be defined in the Category table (see [[Categories]]).
166 97 Selvarani C
167 97 Selvarani C
168 97 Selvarani C
h2. Organization of the raw survey data basket
169 97 Selvarani C
170 97 Selvarani C
The basket should be organized in a directory structure:
171 97 Selvarani C
172 97 Selvarani C
- Project name (these can be themselves put in a hierarchy of (sub)directories)
173 97 Selvarani C
174 97 Selvarani C
- Surveyor's organization
175 97 Selvarani C
176 97 Selvarani C
- Equipment (eg. TS, RTK)
177 97 Selvarani C
178 97 Selvarani C
- Survey files (eg. @Our_project-Some_comment-2018-02-23.txt@)
179 97 Selvarani C
180 97 Selvarani C
h3. Format of the survey file names
181 97 Selvarani C
182 97 Selvarani C
<pre>
183 97 Selvarani C
Our_project-Some_comment-2018-02-23.txt
184 97 Selvarani C
</pre>
185 97 Selvarani C
186 97 Selvarani C
The date of the survey follows the ISO date standard: @YYYY-MM-DD@.
187 97 Selvarani C
188 97 Selvarani C
189 97 Selvarani C
h2. Import to the database
190 97 Selvarani C
191 97 Selvarani C
When importing raw survey data files to the database, Gisaf does 2 steps as described below.
192 97 Selvarani C
It's worth noting that, in this process, no reprojection is done.
193 97 Selvarani C
194 97 Selvarani C
195 97 Selvarani C
h3. Feed the raw_survey table
196 97 Selvarani C
197 97 Selvarani C
Each point of the imported raw survey data file is inserted to the raw_survey table:
198 97 Selvarani C
199 97 Selvarani C
# Creation of a Point geometry: the raw_survey table has a geometry column for a single point (@geom@) with x,y and z coordinates
200 97 Selvarani C
# Save the @id@ of the original point *to the @orig_id@ column*
201 97 Selvarani C
# *A unique @id@ is computed* from the following fields: @id@, @project@, @equipment@, @date@
202 97 Selvarani C
# The project is saved in the @project_id@ column
203 97 Selvarani C
# The surveyor identification in @srvyr_id@
204 97 Selvarani C
# The date of survey is saved in the @date@ column
205 97 Selvarani C
# The accuracy is tagged in the @accur_id@, according to a mapping defined in the @accuracyequimentsurveyormapping@ table, which depends on the surveyor and equipment
206 97 Selvarani C
# The category of the point
207 97 Selvarani C
208 97 Selvarani C
209 97 Selvarani C
h3. Feed the @RAW_V_*@ tables
210 97 Selvarani C
211 97 Selvarani C
From the @raw_survey@ table, each point is then copied to its respective @RAW_V_@ table, with basically the same information.
212 97 Selvarani C
213 97 Selvarani C
These tables (which should be created manually or with the admin notebook called @create_tables@, as of today's writing), only contain points.
214 97 Selvarani C
215 97 Selvarani C
The project is saved along: see below.
216 97 Selvarani C
217 97 Selvarani C
218 97 Selvarani C
h2. Import the points
219 97 Selvarani C
220 97 Selvarani C
For categories that define points (opposite to lines and polygons, which require _line work_ carried over in CAD or in a GIS software, see [[Line work]]), the points can be imported automatically to their final destination: the @V_*@ tables.
221 97 Selvarani C
222 97 Selvarani C
Note: in this process, the geometries are reprojected.
223 97 Selvarani C
224 191 Selvarani C
h2. Auto import of the points
225 97 Selvarani C
226 97 Selvarani C
The points found in the @RAW_V_*@ tables can be imported automatically, project per project, the project page of the admin interface.
227 97 Selvarani C
228 192 Selvarani C
h2. Import of the line work (lines and polygons)
229 97 Selvarani C
230 142 Selvarani C
h2. See [[Line work]] - *%{color:RED} to be written%*
231 97 Selvarani C
232 97 Selvarani C
The shapefiles generated manually (line work) should be put in the project's basket, and imported from it.
233 97 Selvarani C
234 148 Selvarani C
h1. Categories
235 12 Philippe May
236 102 Selvarani C
The categories define the types of the geographical features and they are mapped according to ISO standard layer naming conventions: see https://www.nationalcadstandard.org/ncs5/pdfs/ncs5_clg_lnf.pdf
237 101 Selvarani C
238 101 Selvarani C
Gisaf uses:
239 101 Selvarani C
240 101 Selvarani C
* a table @category@ where the layers are defined
241 101 Selvarani C
* a table per category
242 101 Selvarani C
243 101 Selvarani C
h2. Fields for the categories
244 101 Selvarani C
245 194 Selvarani C
*%{color:RED} to be written%* - TODO
246 101 Selvarani C
247 101 Selvarani C
h2. Creation of the RAW_* tables
248 101 Selvarani C
249 101 Selvarani C
This step must be done manually (as of today's date of writing).
250 101 Selvarani C
251 195 Selvarani C
h1. QGis: work on shapefiles
252 1 Philippe May
253 142 Selvarani C
h2. Go to [[shapefiles]] - *%{color:RED} to be written%*
254 5 Philippe May
255 103 Selvarani C
h1. Data analysis
256 18 Philippe May
257 103 Selvarani C
We use "Jupyter":https://jupyter.org , "Pandas":https://pandas.pydata.org/ and "GeoPandas":http://geopandas.org/ , accessible at http://gis.auroville.org.in/notebooks .
258 18 Philippe May
259 103 Selvarani C
For integration in the processes (execution of notebooks), there's "papermill":https://github.com/nteract/papermill . Systemd "timers":https://wiki.archlinux.org/index.php/Systemd/Timers are used to automatically schedule the notebooks on the server, ie. for the dashboards.
260 1 Philippe May
261 103 Selvarani C
There's a dedicated virtual machine for Jupyter, accessible from our local network at @jupyter.csr.av@.
262 103 Selvarani C
263 103 Selvarani C
h2. Organization of notebooks
264 103 Selvarani C
265 103 Selvarani C
The setup is organized in 2 parts, that are run with 2 instances of Jupyter for security reasons.
266 103 Selvarani C
267 196 Selvarani C
h3. *Admin*
268 103 Selvarani C
269 103 Selvarani C
The notebooks in the admin are mostly for maintenance: operations on the database, etc.
270 103 Selvarani C
271 198 Selvarani C
h3. *Users*
272 198 Selvarani C
273 103 Selvarani C
The notebooks are organized in folders, all under Gisaf's source code git repository, except the "Sandbox" one.
274 103 Selvarani C
275 103 Selvarani C
This notebook server connects to the database with a specific user (@jupyter@), which has been set on the database server with permissions to read all data (@readonly@) plus has write access to some tables dedicated to store analysis results.
276 103 Selvarani C
277 103 Selvarani C
h2. Integration with Gisaf
278 103 Selvarani C
279 103 Selvarani C
The notebook in @Templates@ demonstrates the usage of notebook in relation with Gisaf: mostly, how to use the @gisad.ipynb_tools@ module to access Gisaf models and the data from the database.
280 103 Selvarani C
281 103 Selvarani C
This module is part of gisaf: https://redmine.auroville.org.in/projects/gisaf/repository/revisions/master/entry/gisaf/ipynb_tools.py
282 103 Selvarani C
283 103 Selvarani C
h2. References
284 103 Selvarani C
285 103 Selvarani C
h3. Geopandas
286 103 Selvarani C
287 103 Selvarani C
Some nice examples of processing, using water shed and rain: https://geohackweek.github.io/vector/06-geopandas-advanced/
288 103 Selvarani C
289 103 Selvarani C
h3. Integration
290 103 Selvarani C
291 103 Selvarani C
A good example of how a company has integrated the same tools: https://medium.com/netflix-techblog/scheduling-notebooks-348e6c14cfd6
292 103 Selvarani C
293 103 Selvarani C
h2. Other docs
294 103 Selvarani C
295 200 Selvarani C
h3. *%{color:RED} From Swathi%*
296 5 Philippe May
297 201 Selvarani C
h1. Hosting
298 5 Philippe May
299 5 Philippe May
The team is located in the CSR of Auroville.
300 5 Philippe May
301 202 Selvarani C
We have setup a server for hosting the software and database. *CSR_server* for technical information about the setup.
302 1 Philippe May
303 104 Selvarani C
h1. CSR server
304 1 Philippe May
305 104 Selvarani C
dream.csr.av (192.168.0.12)
306 104 Selvarani C
307 104 Selvarani C
- Debian 9
308 104 Selvarani C
- Xen hypervisor
309 104 Selvarani C
- libvirt for the orchestration of VMs
310 104 Selvarani C
- management with ansible
311 104 Selvarani C
312 104 Selvarani C
313 104 Selvarani C
h2. Dom0
314 104 Selvarani C
315 104 Selvarani C
h3. Installation
316 104 Selvarani C
317 104 Selvarani C
Found minor issues with the installation (eg. issues with HDDs, Dell EFI boot).
318 104 Selvarani C
This document starts from a working Debian Xen server.
319 104 Selvarani C
320 104 Selvarani C
-Installed on a mirror of 2*2TB drives with btrfs.-
321 104 Selvarani C
322 104 Selvarani C
Update (see #7156): re-installed the OS on /dev/sdc2, ext4, without RAID/LVM.
323 104 Selvarani C
324 104 Selvarani C
h3. Storage for domUs
325 104 Selvarani C
326 104 Selvarani C
A LVM dream.csr has been created for the domUs.
327 104 Selvarani C
328 104 Selvarani C
329 104 Selvarani C
h3. Networking
330 104 Selvarani C
331 104 Selvarani C
With systemd.networkd: bridge "br0" to the physical ethernet.
332 104 Selvarani C
333 104 Selvarani C
h3. Create a VM
334 104 Selvarani C
335 104 Selvarani C
Adjust the parameters from:
336 104 Selvarani C
337 104 Selvarani C
<pre>
338 104 Selvarani C
export vm_name=infra.csr.av
339 104 Selvarani C
export vm_ip_addr=172.16.0.3
340 104 Selvarani C
export vm_password=foobar
341 104 Selvarani C
</pre>
342 104 Selvarani C
343 104 Selvarani C
Create the domU:
344 104 Selvarani C
345 104 Selvarani C
<pre>
346 104 Selvarani C
root@dream:~# xen-create-image --broadcast=172.16.0.255 --dist=stretch --fs=ext4 --gateway=172.16.0.1 --hostname ${vm_name} --ip=${vm_ip_addr} --lvm=dream.csr --maxmem=512M --memory=256M --mirror=http://ftp.de.debian.org/debian/ --netmask=255.255.255.0 --password=${vm_password} --size=10G --swap=1G --vcpus=1 --bridge=br0
347 104 Selvarani C
</pre>
348 104 Selvarani C
349 104 Selvarani C
Note that IP address will be set in the VM, and the vm_ip_addr isn't actually used.
350 104 Selvarani C
351 104 Selvarani C
h2. DomUs
352 104 Selvarani C
353 104 Selvarani C
h3. Migrate XL to libvirt
354 104 Selvarani C
355 104 Selvarani C
After creation using xen-create-image, migrate the definition of the domU to libvirt:
356 104 Selvarani C
357 104 Selvarani C
<pre>
358 104 Selvarani C
virsh -c xen:/// domxml-from-native xen-xm /etc/xen/${vm_name}.cfg > /tmp/${vm_name}.xml
359 104 Selvarani C
virsh define /tmp/${vm_name}.xml
360 104 Selvarani C
</pre>
361 104 Selvarani C
362 104 Selvarani C
363 104 Selvarani C
From this point onward, one can log out from the dom0's console and use virsh or "Virtual Machine Manager" from your computer to administer the VM, eg:
364 104 Selvarani C
365 104 Selvarani C
* Set "Auto start" on dom0 boot
366 104 Selvarani C
* Set memory limits, etc
367 104 Selvarani C
368 104 Selvarani C
h3. Start the domU
369 104 Selvarani C
370 104 Selvarani C
Use "Virtual Machine Manager" or the command:
371 104 Selvarani C
372 104 Selvarani C
<pre>
373 104 Selvarani C
virsh -c xen+ssh://root@dream.csr.av/ start ${vm_name}
374 104 Selvarani C
</pre>
375 104 Selvarani C
376 104 Selvarani C
377 104 Selvarani C
h3. To do in a libvirt shell
378 104 Selvarani C
379 104 Selvarani C
Start a libvirt shell, with "Virtual Machine Manager" or with the command:
380 104 Selvarani C
381 104 Selvarani C
<pre>
382 104 Selvarani C
virsh -c xen+ssh://root@dream.csr.av/ console ${vm_name}
383 104 Selvarani C
</pre>
384 104 Selvarani C
385 104 Selvarani C
Log in as root in the libvirt console.
386 104 Selvarani C
387 104 Selvarani C
388 104 Selvarani C
h4. Network config
389 104 Selvarani C
390 104 Selvarani C
Add @/etc/systemd/network/50-wired.network@ (adjust the IP):
391 104 Selvarani C
392 104 Selvarani C
<pre>
393 104 Selvarani C
[Match]
394 104 Selvarani C
Name=eth0
395 104 Selvarani C
396 104 Selvarani C
[Network]
397 104 Selvarani C
Address=192.168.0.14/24
398 104 Selvarani C
Gateway=192.168.0.10
399 104 Selvarani C
DNS=192.168.0.10
400 104 Selvarani C
</pre>
401 104 Selvarani C
402 104 Selvarani C
Then:
403 104 Selvarani C
<pre>
404 104 Selvarani C
systemctl enable --now systemd-networkd.socket
405 104 Selvarani C
systemctl enable --now systemd-networkd.service
406 104 Selvarani C
systemctl disable --now networking.service
407 104 Selvarani C
</pre>
408 104 Selvarani C
409 104 Selvarani C
h4. Post-install ssh config
410 104 Selvarani C
411 104 Selvarani C
Allow ssh root login with password in @/etc/ssh/sshd_config@:
412 104 Selvarani C
413 104 Selvarani C
<pre>
414 104 Selvarani C
sed -i -e 's/#PermitRootLogin prohibit-password/PermitRootLogin yes/' /etc/ssh/sshd_config
415 104 Selvarani C
systemctl restart ssh.service
416 104 Selvarani C
</pre>
417 104 Selvarani C
418 104 Selvarani C
From this point onwards, one can close the console session opened via @libvirt@.
419 104 Selvarani C
420 104 Selvarani C
h3. DNS
421 104 Selvarani C
422 104 Selvarani C
Log in to the local DNS server with:
423 104 Selvarani C
424 104 Selvarani C
<pre>
425 104 Selvarani C
ssh root@infra.csr.av
426 104 Selvarani C
</pre>
427 104 Selvarani C
428 104 Selvarani C
Update the 2 files in @/etc/bind/zones@ (@zones/db.csr.av@ @zones/db.192.168.0@) and reload the DNS with:
429 104 Selvarani C
<pre>
430 104 Selvarani C
rndc reload
431 104 Selvarani C
</pre>
432 104 Selvarani C
433 104 Selvarani C
h3. DNS
434 104 Selvarani C
435 104 Selvarani C
Log in to the local DNS server, *update the 2 files in @/etc/bind9/zones@*, and run:
436 104 Selvarani C
<pre>
437 104 Selvarani C
rndc reload
438 104 Selvarani C
</pre>
439 104 Selvarani C
440 104 Selvarani C
h3. Allow yourself to log in easily with your ssh key
441 104 Selvarani C
442 104 Selvarani C
Copy your ssh key to the domU: run from your own computer:
443 104 Selvarani C
<pre>
444 104 Selvarani C
ssh-copy-id root@${ip_addr}
445 104 Selvarani C
</pre>
446 104 Selvarani C
447 104 Selvarani C
448 104 Selvarani C
h2. Ansible
449 104 Selvarani C
450 104 Selvarani C
Using the Ansible project developed in Blue Light: https://redmine.bluelightav.org/projects/ansible
451 104 Selvarani C
452 104 Selvarani C
h3. Prepare the host
453 104 Selvarani C
454 104 Selvarani C
Install Python
455 104 Selvarani C
456 104 Selvarani C
<pre>
457 104 Selvarani C
apt install -y python
458 104 Selvarani C
</pre>
459 104 Selvarani C
460 104 Selvarani C
461 104 Selvarani C
h2. Database
462 104 Selvarani C
463 104 Selvarani C
The Postgis database runs on its specific domU (gisdb.csr.av, 192.168.0.18).
464 104 Selvarani C
465 104 Selvarani C
h3. Installation
466 104 Selvarani C
467 104 Selvarani C
After installing the Postgis package (eg. assign the "postgis" Ansible's role), follow up to [[Db-support]]
468 104 Selvarani C
469 104 Selvarani C
470 104 Selvarani C
h2. Jupyter
471 104 Selvarani C
472 104 Selvarani C
The Jupyter server runs on its specific domU (jupyter.csr.av, 192.168.0.19).
473 104 Selvarani C
474 104 Selvarani C
h3. Installation
475 104 Selvarani C
476 104 Selvarani C
See #6990 .
477 105 Selvarani C
478 150 Selvarani C
h1. Backup and restoration of the database
479 1 Philippe May
480 105 Selvarani C
h1. Database
481 105 Selvarani C
482 105 Selvarani C
h2. Troubleshooting
483 105 Selvarani C
484 105 Selvarani C
h3. Layers missing in the map's tree
485 105 Selvarani C
486 105 Selvarani C
Gisaf relies on counting features through Postgres statistics collector subsystem.
487 105 Selvarani C
488 105 Selvarani C
In case the server is restarted *dirty* (eg. without clean shutdown), then the count of the tables might be wrong or just 0, leaving the layers apparently empty and thus not even appearing.
489 105 Selvarani C
490 105 Selvarani C
The fix is as easy as:
491 105 Selvarani C
492 105 Selvarani C
<pre>
493 105 Selvarani C
sudo -u postgres psql avgis -c VACUUM
494 105 Selvarani C
</pre>
495 105 Selvarani C
496 105 Selvarani C
h2. Installation
497 105 Selvarani C
498 105 Selvarani C
This documentation assumes that the Postgis package has been installed (see [[CSR_server#Database]]).
499 105 Selvarani C
500 203 Selvarani C
h1. Configure the server
501 105 Selvarani C
502 105 Selvarani C
h4. Allow connections from other hosts in the local network
503 105 Selvarani C
504 105 Selvarani C
Set the server to listen to addresses, set listen_addresses to @*@ in @/etc/postgresql/9.6/main/postgresql.conf@.
505 105 Selvarani C
506 105 Selvarani C
507 105 Selvarani C
Allow the connections, add in @/etc/postgresql/9.6/main/pg_hba.conf@:
508 105 Selvarani C
509 105 Selvarani C
<pre>
510 105 Selvarani C
host all all 192.168.0.0/24 md5
511 105 Selvarani C
</pre>
512 105 Selvarani C
513 105 Selvarani C
h2. Creation of the database
514 105 Selvarani C
515 105 Selvarani C
As @postgres@ user:
516 105 Selvarani C
517 105 Selvarani C
<pre>
518 105 Selvarani C
createdb -E utf8 -T template0 avgis
519 105 Selvarani C
</pre>
520 105 Selvarani C
521 105 Selvarani C
h2. Backups
522 105 Selvarani C
523 105 Selvarani C
h3. Primary
524 105 Selvarani C
525 105 Selvarani C
The database is backed up every day at midnight. The dump file is located in @/var/backups/postgres/@.
526 105 Selvarani C
527 105 Selvarani C
h3. Secondary
528 105 Selvarani C
529 105 Selvarani C
There are other backups (daily, weekly, monthly) thanks to Debian package @autopostgresqlbackup@), located (default) in @/var/lib/autopostgresqlbackup@.
530 105 Selvarani C
531 105 Selvarani C
h3. Tertiary (dom0)
532 105 Selvarani C
533 105 Selvarani C
The whole virtual machine is backed up by BackupNinja on the "dom0" controller, using:
534 105 Selvarani C
- rdiff backups every day
535 105 Selvarani C
- tar files on Saturdays.
536 105 Selvarani C
537 105 Selvarani C
See @/etc/backups.d@ on the dom0 (192.168.0.12).
538 105 Selvarani C
539 208 Selvarani C
h1. Remote
540 105 Selvarani C
541 208 Selvarani C
*%{color:RED} TODO: remote backup to be written%*
542 105 Selvarani C
543 209 Selvarani C
h1. Restoration
544 105 Selvarani C
545 105 Selvarani C
If the VM is not shutdown properly, there's a chance that the database is corrupt, and needs to be restored from one of the backups.
546 105 Selvarani C
547 209 Selvarani C
h2. After the restoration, restart gisaf:
548 105 Selvarani C
<pre>
549 105 Selvarani C
systemctl restart uwsgi.service
550 105 Selvarani C
</pre>
551 105 Selvarani C
552 210 Selvarani C
h1. From primary backup
553 105 Selvarani C
554 105 Selvarani C
*Note*: the roles aren't restored with this method.
555 105 Selvarani C
556 105 Selvarani C
With user @postgres@:
557 105 Selvarani C
<pre>
558 105 Selvarani C
# Optionally, rename the corrupt database (selecting a name for a database like "avgis_c2")...
559 105 Selvarani C
psql -c "ALTER DATABASE avgis RENAME TO avgis_c2;"
560 105 Selvarani C
# ... or drop the existing database
561 105 Selvarani C
psql -c "drop database avgis;"
562 105 Selvarani C
# Create a new database:
563 105 Selvarani C
createdb -E utf8 -T template0 avgis
564 105 Selvarani C
# Restore the database
565 105 Selvarani C
pg_restore -d avgis /var/backups/postgres/avgis.pg_dump
566 105 Selvarani C
</pre>
567 105 Selvarani C
568 105 Selvarani C
h3. From secondary backup
569 105 Selvarani C
570 105 Selvarani C
@autopostgresqlbackup@ backs up the roles in @postgres_globals@.
571 105 Selvarani C
572 105 Selvarani C
<pre>
573 105 Selvarani C
zcat /var/lib/autopostgresqlbackup/daily/postgres_globals/postgres_globals_2018-10-24_06h25m.Wednesday.sql.gz | psql
574 105 Selvarani C
zcat /var/lib/autopostgresqlbackup/daily/avgis/avgis_2018-10-24_06h25m.Wednesday.sql.gz | psql
575 105 Selvarani C
</pre>
576 17 Philippe May
577 17 Philippe May
h2. Gear
578 17 Philippe May
579 17 Philippe May
h3. Survey equipment
580 17 Philippe May
581 143 Selvarani C
h2. See [[survey equipment]] - *%{color:RED} to be written%*
582 17 Philippe May
583 152 Selvarani C
h1. Weather station
584 17 Philippe May
585 152 Selvarani C
586 11 Philippe May
587 106 Selvarani C
h1. Ambient Weather weather station
588 106 Selvarani C
589 106 Selvarani C
We have purchased a WS2902A weather station (https://www.ambientweather.com/amws2902.html).
590 106 Selvarani C
Firmware version: 4.0.2.
591 106 Selvarani C
592 106 Selvarani C
h2. Manual
593 106 Selvarani C
594 106 Selvarani C
The operating manual of the weather station can be found at https://p10.secure.hostingprod.com/@site.ambientweatherstore.com/ssl/Manuals/WS-2902C.pdf
595 106 Selvarani C
596 106 Selvarani C
h2. Connection
597 106 Selvarani C
598 106 Selvarani C
h3. Wifi
599 106 Selvarani C
600 106 Selvarani C
Set up the wifi of the console using the "Ambient Tool" phone application. IP address given by DHCP on the router is: 192.168.1.101
601 106 Selvarani C
602 106 Selvarani C
h3. Local communication
603 106 Selvarani C
604 106 Selvarani C
Fail so far: the only exposed port is TCP/45000. Telnet doesn't show any activity. Nothing found on Internet on this protocol.
605 106 Selvarani C
606 106 Selvarani C
One interesting project may come, hijacking the connection to cloud services: https://www.wxforum.net/index.php?topic=35033.0
607 106 Selvarani C
608 106 Selvarani C
609 106 Selvarani C
h3. Cloud connection
610 106 Selvarani C
611 106 Selvarani C
We'll create an account on AmbientWeather.net (and eventually on WUnderground.net and/or weathercloud.net), and:
612 106 Selvarani C
613 106 Selvarani C
* have the console upload data to there
614 106 Selvarani C
* gisaf to retrieve our WS data from there
615 106 Selvarani C
616 106 Selvarani C
h1. Notes on Console
617 106 Selvarani C
618 106 Selvarani C
The daily rainfall data displayed in  the console resets at 00.30 every night
619 11 Philippe May
620 7 Philippe May
h2. Plan for future
621 7 Philippe May
622 154 Selvarani C
Beside living well, 
623 8 Philippe May
624 107 Selvarani C
h1. Plan
625 107 Selvarani C
626 107 Selvarani C
Some interesting projects that might be integrated:
627 107 Selvarani C
628 107 Selvarani C
* https://github.com/Oslandia/albion : Build 3D geological model from wells information
629 107 Selvarani C
630 49 Philippe May
h2. Other
631 1 Philippe May
632 155 Selvarani C
633 49 Philippe May
634 108 Selvarani C
h1. GDAL (OGR) tools
635 108 Selvarani C
636 108 Selvarani C
"GDAL":https://gdal.org/ is a translator library for raster and vector geospatial data formats. It is used by many software (including QGIS and many other open source ones, including Gisaf). Some command line utilities are supplied, like:
637 108 Selvarani C
638 108 Selvarani C
* @ogr2ogr@ can easily convert one data format to another
639 108 Selvarani C
* @ogrinfo@ displays information about files.
640 108 Selvarani C
641 108 Selvarani C
h2. Using Windows
642 108 Selvarani C
643 108 Selvarani C
On a computer with Windows and GQIS installed:
644 108 Selvarani C
645 108 Selvarani C
1. Open a command line console (eg. <Windows Key> to display the Start menu, then just type @cmd@ and <Enter>)
646 108 Selvarani C
2. In the console window, type (adjust with the QGIS version and location, this seems to be the standard one):
647 108 Selvarani C
648 108 Selvarani C
<pre>
649 108 Selvarani C
"c:\Program Files\QGis 3.10\OSGeo4W.bat"
650 108 Selvarani C
</pre>
651 108 Selvarani C
652 108 Selvarani C
3. GDAL utilities can be used: @ogr2ogr@, etc.
653 108 Selvarani C
654 108 Selvarani C
h2. Example: convert Geopackage to Shapefiles
655 108 Selvarani C
656 108 Selvarani C
Output the content of the geopackage @9wdoogfr_2019-11-13_12_26_07.gpkg@ to the folder @shapefiles@:
657 108 Selvarani C
658 108 Selvarani C
<pre>
659 108 Selvarani C
ogr2ogr -progress -f "ESRI Shapefile" shapefiles 9wdoogfr_2019-11-13_12_26_07.gpkg
660 108 Selvarani C
</pre>
661 108 Selvarani C
662 108 Selvarani C
To output the content of the geopackage @9wdoogfr_2019-11-13_12_26_07.gpkg@ to the @root@ folder:
663 108 Selvarani C
664 108 Selvarani C
<pre>
665 108 Selvarani C
ogr2ogr -progress -f "ESRI Shapefile" c:\shapefiles 9wdoogfr_2019-11-13_12_26_07.gpkg
666 108 Selvarani C
</pre>
667 108 Selvarani C
668 108 Selvarani C
h2. With reprojection
669 108 Selvarani C
670 108 Selvarani C
Same as above, reprojecting to UTM44N: 
671 108 Selvarani C
672 108 Selvarani C
<pre>
673 108 Selvarani C
ogr2ogr -progress -f "ESRI Shapefile" -t_srs EPSG:32644 c:\shapefiles 9wdoogfr_2019-11-13_12_26_07.gpkg
674 108 Selvarani C
</pre>
675 108 Selvarani C
676 8 Philippe May
h2. Links and references
677 8 Philippe May
678 156 Selvarani C
679 16 Philippe May
680 109 Selvarani C
h1. Links
681 109 Selvarani C
682 109 Selvarani C
h2. Water management
683 109 Selvarani C
684 109 Selvarani C
h3. Modflow
685 109 Selvarani C
686 109 Selvarani C
* https://water.usgs.gov/ogw/modflow/
687 109 Selvarani C
688 109 Selvarani C
The reference software for underground water modelling and simulation.
689 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.
690 109 Selvarani C
691 109 Selvarani C
692 109 Selvarani C
h3. Freewat
693 109 Selvarani C
694 109 Selvarani C
* http://www.freewat.eu/project
695 109 Selvarani C
696 109 Selvarani C
This project is partly based on modflow, and integrates with QGis.
697 109 Selvarani C
698 109 Selvarani C
h2. QGIS
699 109 Selvarani C
700 109 Selvarani C
* https://www.qgis.org/en/site/
701 109 Selvarani C
702 109 Selvarani C
* Tools for Geology
703 109 Selvarani C
Construction of geological cross sections in QGIS - http://www.geokincern.com/?p=1452
704 109 Selvarani C
705 109 Selvarani C
706 109 Selvarani C
h2. Autocad
707 109 Selvarani C
708 109 Selvarani C
* Overview of Converting Geospatial Data to Drawing Objects: 
709 109 Selvarani C
http://docs.autodesk.com/CIV3D/2013/ENU/index.html?url=filesMAPC3D/GUID-C38FD485-3CC2-4B52-8264-0D8C0F45422B.htm,topicNumber=MAPC3Dd30e41809
710 109 Selvarani C
711 109 Selvarani C
* CAD-DB connection:
712 109 Selvarani C
https://knowledge.autodesk.com/support/autocad-civil-3d/learn-explore/caas/video/youtube/watch-v-AQoB--nyUJA.html
713 109 Selvarani C
714 211 Selvarani C
h1. Orfeo
715 109 Selvarani C
716 109 Selvarani C
* https://www.orfeo-toolbox.org/
717 109 Selvarani C
718 109 Selvarani C
Remote sensing
719 16 Philippe May
720 16 Philippe May
h2. Old docs
721 16 Philippe May
722 157 Selvarani C
[[Shapefiles]] - *%{color:RED} to be written%*
723 158 Selvarani C
724 110 Selvarani C
h1. Data (measurements auxiliary tables)
725 110 Selvarani C
726 110 Selvarani C
Besides the importation of [[shapefiles]], Gisaf can import non-geophical information: auxiliary data (typically categories like the list of locations names, well types, etc), and temporal informations (well levels, etc).
727 110 Selvarani C
728 110 Selvarani C
h2. Command line
729 110 Selvarani C
730 110 Selvarani C
The @import_to_db.py@ script imports files, fetched from a set of URLs (typically, in the Redmine Files section of this project), formats and pre-process, and imports to the database.
731 110 Selvarani C
732 110 Selvarani C
@import_to_db.py@ is a support tool, that is planned to be integrated with the web interface.
733 110 Selvarani C
734 110 Selvarani C
Import all with:
735 110 Selvarani C
736 110 Selvarani C
<pre>
737 110 Selvarani C
phil@phil-mbp:~/BlueLight/gisaf_src/gisaf$ python import_to_db.py
738 110 Selvarani C
</pre>
739 110 Selvarani C
740 110 Selvarani C
The script currently accepts an argument for filtering the URLs to import.
741 110 Selvarani C
742 212 Selvarani C
h1. Pavneet's docs (imported from gisaf's wiki)
743 111 Selvarani C
744 111 Selvarani C
h1. Basic Rules of Map making
745 111 Selvarani C
746 111 Selvarani C
Regardless of the cartographic style or content, most maps have the following common elements.
747 111 Selvarani C
748 111 Selvarani C
749 111 Selvarani C
h2. TITLE
750 111 Selvarani C
751 111 Selvarani C
The title should be in a large font, easily identifiable as the title of the map and should include descriptive text as to the location and purpose of the map. If the map is thematic, the theme should be included in the title. For example: Corn Production in Washington, 1990. The title is usually the largest font size of all lettering on the layout, however, it should not dominate the map graphic itself. The title may or may not be in a box and does not need to be at the top of the page (though it often is). For published materials (e.g., books or articles) the title may be included in a figure caption instead.
752 111 Selvarani C
753 111 Selvarani C
 
754 111 Selvarani C
755 111 Selvarani C
h2. SCALE INDICATOR
756 111 Selvarani C
757 111 Selvarani C
The scale of the map is typically indicated by a graphic bar scale, a representative fraction or a verbal scale. The reader must be able to determine the relationship between a unit of measure on the map and a unit of measure in the real world.
758 111 Selvarani C
759 111 Selvarani C
 
760 111 Selvarani C
761 111 Selvarani C
h2. ORIENTATION
762 111 Selvarani C
763 111 Selvarani C
A map should indicate which way is north (and/or south, east and west). Commonly this is done by a north arrow or compass rose. Orientation may also be shown by graticule or grid marks (e.g. lines of latitude and longitude). By convention north is towards the top of the page (thus some maps do not have north arrows), but the orientation must still be given for a 'proper' map. North does not have to be at the top of the page and a north arrow is essential in maps where it is not.
764 111 Selvarani C
765 111 Selvarani C
h2. BORDER(s)
766 111 Selvarani C
767 111 Selvarani C
A border identifies exactly where the mapped area stops. The border is often the thickest line on the map and should be close to the edges of the mapped area. The distance between the map and the border should be the same on all sides (balanced).
768 111 Selvarani C
769 111 Selvarani C
There can also be a border around the entire map layout (enclosing and grouping the title, legend, text boxes, etc.). 
770 111 Selvarani C
771 111 Selvarani C
Both of these borders are sometimes referred to as a 'neatline.' In addition, there is sometimes a thin additional line just outside of a border (accentuating it and ideally making it more visually appealing) that may also be referred to as a neatline.
772 111 Selvarani C
773 111 Selvarani C
h2. LEGEND
774 111 Selvarani C
775 111 Selvarani C
A legend defines the symbols or colors (including shades of gray and patterns) used on the map. Maps do not need legends if the symbology is so common or simple as to be easily understood by the reader. However, it must be clear what each marker or line type, weight and pattern represents. The legend does not need to be labeled "Legend." The more complicated the symbology on a map the more important the legend becomes.
776 111 Selvarani C
777 111 Selvarani C
h2. MAP CREDITS
778 111 Selvarani C
779 111 Selvarani C
* SOURCE OF DATA (especially on thematic maps)
780 111 Selvarani C
* NAME of the cartographer  
781 111 Selvarani C
* DATE of the map creation/publication 
782 111 Selvarani C
* DATE of the map data 
783 111 Selvarani C
* PROJECTION of the map (especially small-scale maps)
784 111 Selvarani C
785 111 Selvarani C
h2. LOCATOR MAP (INSET)
786 111 Selvarani C
787 111 Selvarani C
A locator map is needed if the area of the map is not easily recognizable or is of large scale. For example, if you map Whatcom County, there should be an inset map of Washington, showing the location of Whatcom County.  Inset DETAIL map(s) may also be used to show an area of the map in greater detail (larger scale).
788 111 Selvarani C
789 111 Selvarani C
h2. EFFECTIVE GRAPHICAL DESIGN
790 111 Selvarani C
791 111 Selvarani C
The layout design is as important as effective sentence structure is to written text. Layout design refers to the planning and decision making processes involved in the visual display of the spatial data. You can achieve balance by rearranging the map elements (north arrow, legend, scale, title, etc.) and changing size of the text, border. etc. The map and map elements should be:
792 111 Selvarani C
793 111 Selvarani C
* Neatly drawn
794 111 Selvarani C
* Appropriately and consistently generalized
795 111 Selvarani C
* Symmetrically balanced (avoid crowding or large blank areas)
796 111 Selvarani C
* Without unnecessary clutter (keep it simple, be wary of 'artistic' details)
797 111 Selvarani C
798 111 Selvarani C
h2. VISUAL HIERARCHY
799 111 Selvarani C
800 111 Selvarani C
A hierarchy of symbology should be used for the lettering, line weights and shading. More important features are typically larger and/or darker, less important/background information should be smaller and/or lighter. At the same time, do not "over weight" or "under weight" features.
801 111 Selvarani C
802 111 Selvarani C
h2. PURPOSE
803 111 Selvarani C
804 111 Selvarani C
All maps have a purpose which should influence every element of the map and the map layout. A cartographer should be able to clearly articulate the purpose of their map and should keep the audience (who the map is going to be used by) and the client (who the maps is being produced for) in mind.
805 1 Philippe May
806 214 Selvarani C
h3. NOTE: Any, or all, of the above 'rules' can be (and frequently have been) violated at the discretion of the cartographer IF doing so produces a better map (better serving its purpose and audience).
807 111 Selvarani C
808 111 Selvarani C
*In general, with cartography, less is more (avoid excessive clutter).*
809 1 Philippe May
810 161 Selvarani C
h1. GIS - Survey_Database
811 112 Selvarani C
812 112 Selvarani C
DB- Database
813 112 Selvarani C
C3D- Civil 3D
814 112 Selvarani C
815 215 Selvarani C
h1. How to create Survey database in Civil 3D
816 112 Selvarani C
817 215 Selvarani C
h2. 1. Setting up the Working Folder
818 112 Selvarani C
819 112 Selvarani C
A working folder needs to be created where the survey databases gets stored. In the *Toolbox* > Right click on *Survey databases* > Set the working folder - Save the folder in the desired location. We are setting the Working Folder for the Civil 3D databases in C:
820 112 Selvarani C
821 117 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9783/working%20folder%20image.jpg!
822 116 Selvarani C
823 215 Selvarani C
h2. 2. Creating a database
824 112 Selvarani C
825 112 Selvarani C
Right click on *Survey databases* > *New local Survey database* - Enter the name> click ok. A survey DB is created (It is in bold which signifies it is the current DB under use). Multiple DB's can be created. A survey DB can be opened for editing by right click > *open for edit*. It can be closed by right click > *close for edits*. A survey DB can also be opened as *read-only* by same procedures.
826 112 Selvarani C
827 215 Selvarani C
h2. 3. Setting up the database
828 112 Selvarani C
829 112 Selvarani C
Survey Database(abc) > Right click + Survey Database Settings > Specify co-ordinate Zone > Distance- Metre > Temperature - Celsius > Pressure - Millibars > Distance type - Horizontal > Vertical type - Vertical Distance.
830 112 Selvarani C
831 112 Selvarani C
Then the next step is to create the Networks under which the point data gets uploaded. For example in our case we have - TS and RTK
832 112 Selvarani C
833 112 Selvarani C
h2. Components of Survey Database
834 112 Selvarani C
835 112 Selvarani C
Survey database in civil 3D has the following components when expanded. 
836 112 Selvarani C
# Import Events
837 112 Selvarani C
# Survey Queries
838 112 Selvarani C
# Networks
839 112 Selvarani C
# Network Groups
840 112 Selvarani C
# Figures
841 112 Selvarani C
# Figure Groups
842 112 Selvarani C
# Survey Points
843 112 Selvarani C
# Survey point Groups
844 112 Selvarani C
845 118 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9782/Survey_db.png!
846 163 Selvarani C
847 113 Selvarani C
848 113 Selvarani C
h1. Survey- Field to Finish
849 113 Selvarani C
850 113 Selvarani C
h2. Steps from field work 
851 113 Selvarani C
852 113 Selvarani C
# ?? To be added by Raj and Ram
853 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")
854 113 Selvarani C
# Cleaning up the .txt files/removing errors (If any)
855 113 Selvarani C
856 113 Selvarani C
h2. Feeding the survey data into Civil 3D- by Surveyor
857 113 Selvarani C
858 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
859 113 Selvarani C
# Open up project in Civil 3D
860 113 Selvarani C
# Importing of Events (explain the step)
861 113 Selvarani C
862 113 Selvarani C
h2. Processing- by Surveyor
863 113 Selvarani C
864 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.
865 113 Selvarani C
866 113 Selvarani C
h2. Post-Processing
867 113 Selvarani C
868 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.
869 113 Selvarani C
870 113 Selvarani C
h2. Creating shapefiles in AutoCAD
871 113 Selvarani C
872 217 Selvarani C
?? add by pavneet - *%{color:RED} to be written%*
873 113 Selvarani C
874 113 Selvarani C
h2. Sharing on WebGIS - "GISAF-  +gis.auroville.org.in+" 
875 113 Selvarani C
876 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.
877 113 Selvarani C
878 113 Selvarani C
879 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.
880 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)
881 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.
882 113 Selvarani C
# *Import to GISAF (Only with Authorization)* - Click on the import arrow.
883 113 Selvarani C
884 113 Selvarani C
h2. Adding new codes
885 113 Selvarani C
886 220 Selvarani C
ADD !! - *%{color:RED} to be written%*
887 113 Selvarani C
888 113 Selvarani C
h2. Reconciliation of points
889 113 Selvarani C
890 220 Selvarani C
The points are noted with their codes from and codes to reconcile into. ADD!! - *%{color:RED} to be written%*
891 119 Selvarani C
892 119 Selvarani C
h1. Survey Data Post-Processing
893 119 Selvarani C
894 119 Selvarani C
+Softwares used: Civil 3D, QGIS+
895 119 Selvarani C
896 119 Selvarani C
AutoCAD Civil 3D - C3D, 
897 119 Selvarani C
898 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.
899 119 Selvarani C
900 119 Selvarani C
QGIS is an Open source GIS.
901 119 Selvarani C
902 119 Selvarani C
Getting Started:
903 119 Selvarani C
+Standards and Workflow for C3D+
904 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.
905 119 Selvarani C
906 119 Selvarani C
+Geometry types-+
907 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).
908 119 Selvarani C
909 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.
910 119 Selvarani C
911 119 Selvarani C
+Using Feature lines for creating Curved geometries in 3D-+
912 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 :-
913 119 Selvarani C
914 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.
915 119 Selvarani C
916 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.
917 119 Selvarani C
918 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.
919 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.
920 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.
921 119 Selvarani C
Situations of sharing of points with different layers and proceeding with linework in such circumstances-
922 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. 
923 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).
924 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. 
925 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. 
926 119 Selvarani C
927 119 Selvarani C
*+Purpose of Survey+*
928 119 Selvarani C
929 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.
930 119 Selvarani C
931 119 Selvarani C
932 119 Selvarani C
+Use of Layers+
933 119 Selvarani C
934 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.
935 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.
936 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.
937 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.
938 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.
939 119 Selvarani C
# Use of *V-ROAD-CYCP* is for designated cycle path as a single line.
940 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.
941 119 Selvarani C
# *V-WMNG-PIPP* for pipe points, *V-WMNG-PIPL*- for pipe lines.
942 119 Selvarani C
# *V-BLDG-BMRK* is for unidentified bench marks and *V-BLDG-MHOL* is for unidentified manholes.
943 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.
944 119 Selvarani C
# *V-WMNG-POOL* is for water bodies made for leisure activities- like swimming pool etc.
945 119 Selvarani C
# *V-WMNG-SUMP* is collectively for artificial water retention structures.
946 119 Selvarani C
# *V-WATR-POND* is for top of natural water retention.
947 119 Selvarani C
# *V-WATR-PONB* is for bottom of natural water retention.
948 119 Selvarani C
# *V-WMNG-DRBA* is for bottom of artificial drains.
949 119 Selvarani C
# *V-WMNG-DRTA* is for top of artificial drains.
950 119 Selvarani C
# *V-WATR-DRBN* is for bottom of Natural drains.
951 119 Selvarani C
# *V-WATR-DRTN* is for top of Natural drains.
952 119 Selvarani C
# *V-WMNG-DRNC* is for drain covers.
953 1 Philippe May
# *V-WATR-DRAS* is for indicating slope of drainage, these are arrows.
954 119 Selvarani C
955 120 Selvarani C
h1. Wells Documentation
956 120 Selvarani C
957 120 Selvarani C
Documentation of the wells in Auroville started afresh in September 2017 by Bala working with the *Water Group*. He used a mobile GPS to record co-ordinates and took pictures along with other data related to a well. An effort was made to reconcile data by identification  of the wells with existing data from *Auroville Water Harvest* which ceased to exist around 2007/2009. In some cases the codes on the well on location (sometimes there is a code on the pump, on the casing or on a nearby wall) helped in reconciliation but mostly by spatial mapping using QGIS. Some wells could not be reconciled due to absence of any nearby well in old data. However, we are publishing all the wells we have documented so far.
958 120 Selvarani C
959 120 Selvarani C
*Terms of reference*
960 120 Selvarani C
961 120 Selvarani C
+Well status+ 
962 120 Selvarani C
	
963 120 Selvarani C
# *In use*      Well is equipped with functioning a pump	
964 120 Selvarani C
# *Not in use*  Well is not equipped with a functioning pump. (Special case- well is equipped with a non functioning pump)
965 120 Selvarani C
# *Closed*      Well is closed/ sealed/ abandoned, (Historical reference)
966 120 Selvarani C
967 1 Philippe May
Note: Wells with pump under repair (temporary measure) at the time of survey are treated as *In use*.
968 120 Selvarani C
969 167 Selvarani C
970 121 Selvarani C
971 121 Selvarani C
h1. Civil 3D useful commands
972 121 Selvarani C
973 121 Selvarani C
974 121 Selvarani C
h2. Making Feature line to polyline-
975 121 Selvarani C
976 121 Selvarani C
Select the feature line> go to elevation editor (under feature line tab> edit elevations)> select all the points in table, give elevation(this will give same elevation to all the points thereby making it possible to retain the curves in the polyline) > explode the feature line (use X enter)
977 121 Selvarani C
978 121 Selvarani C
h2. Converting Circle to polyline-
979 121 Selvarani C
980 121 Selvarani C
BR > enter > break the circle at two points to obtain a part of circle. 
981 121 Selvarani C
PEDIT> enter> select the part of leftover circle> J > enter> Close> enter.
982 121 Selvarani C
983 121 Selvarani C
h2. Converting 2DPOLYLINE to POLYLINE
984 121 Selvarani C
985 121 Selvarani C
Explode the 2D polyline, and use the PEDIT command to convert the segments to polylines. Then join the polylines.
986 121 Selvarani C
987 121 Selvarani C
h2. Viewing only the used layer in ACAD-
988 121 Selvarani C
989 121 Selvarani C
Set the value of SHOWLAYERUSAGE from 0 to 1
990 121 Selvarani C
991 121 Selvarani C
h2. Convert 3d polyline to polyline- 
992 121 Selvarani C
993 121 Selvarani C
COVERT3DPOLYS (Change the elevation of the polyline using properties manager to 0 in our case)
994 121 Selvarani C
995 121 Selvarani C
h2. Generating contours from a Surface in Civil 3D
996 121 Selvarani C
997 121 Selvarani C
# In prospector, Create a point group of points needed to generate the contours from for example- TOPO elevation points or BLDG floor levels. If the point group is already present, then proceed to next step.
998 121 Selvarani C
# Create a surface in the prospector> when creating the new surface, give the name and styling in the dialog box- styling used by us is "Triangles and surface- 0.1 and 0.5"> Assign the point groups in the surface as created in previous step.
999 121 Selvarani C
# Go to the surface created in prospector and right click > Edit surface style> Turn on the Major and Minor contour.
1000 121 Selvarani C
# Turn on the layers for Major and Minor contours in Layers Manager (LA > enter)
1001 121 Selvarani C
1002 121 Selvarani C
h2. Shortcuts:
1003 121 Selvarani C
1004 121 Selvarani C
• Properties manager - ctrl + 1
1005 121 Selvarani C
• To view 3D- Select and right click> object Viewer.
1006 121 Selvarani C
• To copy the Line - Copy and select the line enter 
1007 121 Selvarani C
• To convert spline to polyline >Splinedit
1008 121 Selvarani C
• To export shapefile - Mapexport > follow the process.
1009 121 Selvarani C
• To assign coordinate system to the drawing - MAPCSLIBRARY
1010 121 Selvarani C
• To check coordinate system of the drawing- > TOOLSPACE> Settings> Right click on the drawing name > Edit settings
1011 121 Selvarani C
1012 122 Selvarani C
h1. Online references for Civil 3D
1013 122 Selvarani C
1014 123 Selvarani C
*Description Key Sets*
1015 122 Selvarani C
1016 122 Selvarani C
https://www.youtube.com/watch?v=Von8oCwYcTk
1017 122 Selvarani C
1018 124 Selvarani C
*Autodesk civil 3D Geotechnical module- for borehole data*
1019 122 Selvarani C
1020 122 Selvarani C
https://www.youtube.com/watch?v=0Be9kShBou0
1021 122 Selvarani C
1022 123 Selvarani C
*Civil 3D for Surveyors*
1023 122 Selvarani C
1024 122 Selvarani C
https://www.youtube.com/playlist?list=PL1EzH8XlwSxuxCMdeLvzqfgsAlmeeHMv2
1025 122 Selvarani C
1026 123 Selvarani C
*Civil 3D: Survey - Survey Database*
1027 1 Philippe May
1028 122 Selvarani C
https://www.youtube.com/watch?v=VPWdAfYJt5Y 
1029 123 Selvarani C
1030 169 Selvarani C
1031 125 Selvarani C
1032 125 Selvarani C
h1. Connections in QGIS- Using browser panel and Add postGIS
1033 125 Selvarani C
1034 125 Selvarani C
Working using QGIS as interface using PostGIS connections.
1035 125 Selvarani C
1036 125 Selvarani C
* Server: @gisdb.csr.av@
1037 125 Selvarani C
1038 125 Selvarani C
* Database: @avgis@
1039 125 Selvarani C
1040 125 Selvarani C
* Leave @Service@ empty
1041 125 Selvarani C
1042 125 Selvarani C
1043 125 Selvarani C
h2. Adding tables (With geometries) in form of shape files from database using Browser panel-
1044 125 Selvarani C
1045 125 Selvarani C
Go to QGIS> view> Panels> Browser panel> PostGIS> Expand the connection> give credentials> add the desired file by double clicking on it.
1046 125 Selvarani C
1047 125 Selvarani C
1048 125 Selvarani C
h2. Adding tables (For non-geometry type) using PostGIS connections-
1049 125 Selvarani C
1050 125 Selvarani C
Add PostGIS Layers > Give credentials > select "Also list tables with no geometry" > expand public > click on the desired table> add.
1051 125 Selvarani C
1052 125 Selvarani C
h2. Joining tables
1053 125 Selvarani C
1054 125 Selvarani C
Right click/double click on file> go to Join > perform the desired joins - add/subtract the joins. 
1055 125 Selvarani C
1056 125 Selvarani C
1057 170 Selvarani C
h1. *Reconcilation of Raw survey data using pgAdmin*
1058 126 Selvarani C
1059 126 Selvarani C
+For changing the layer codes, to be done using Pgadmin.+
1060 126 Selvarani C
1061 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.
1062 126 Selvarani C
1063 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).
1064 126 Selvarani C
1065 126 Selvarani C
h3.  Other > Project > select the project > with selected> reconcile RAW survey points.
1066 126 Selvarani C
1067 127 Selvarani C
h1. Importing point data (TS and RTK) to GISAF 
1068 127 Selvarani C
1069 127 Selvarani C
# *Gisaf Admin > Basket > Survey data > "Project" > "surveyor" > TS/ RTK > upload > import.*
1070 127 Selvarani C
# *Auto import of Raw points data* (changes from Raw to Shapefiles, the point files)
1071 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...
1072 127 Selvarani C
1073 172 Selvarani C
1074 128 Selvarani C
1075 128 Selvarani C
h1. Editing Z value of features in Shapefiles in QGIS
1076 128 Selvarani C
1077 128 Selvarani C
h2. using vertex editor tool - https://www.youtube.com/watch?v=8V8i1AtcA74&t=256s
1078 128 Selvarani C
1079 129 Selvarani C
h1. Miscellaneous- Civil 3D
1080 129 Selvarani C
1081 129 Selvarani C
*Autodesk civil 3D Geotechnical module- for borehole data :- To analyse borehole data, To make profiles and calculate volumes*
1082 129 Selvarani C
1083 129 Selvarani C
https://www.youtube.com/watch?v=0Be9kShBou0
1084 129 Selvarani C
Reference videos
1085 129 Selvarani C
Exploring:
1086 129 Selvarani C
https://www.youtube.com/watch?v=gr-ISPzLcU0
1087 129 Selvarani C
Modelling:
1088 129 Selvarani C
https://www.youtube.com/watch?v=Pz0-HOoiBrs
1089 129 Selvarani C
solids
1090 129 Selvarani C
https://www.youtube.com/watch?v=mQ0Yeh6tZA8
1091 129 Selvarani C
https://www.youtube.com/watch?v=4eMsUiYBhuE
1092 129 Selvarani C
1093 129 Selvarani C
1094 129 Selvarani C
*CIVIL 3D Survey*
1095 129 Selvarani C
Getting started- Always open a new drawing with a template. 
1096 129 Selvarani C
1097 129 Selvarani C
*Description key sets*- (till 18:30) https://www.youtube.com/watch?v=mmwkkRyBkS0
1098 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.
1099 129 Selvarani C
Tool space > settings > points > description key sets
1100 129 Selvarani C
“Description key sets name”> edit key- to view the points in a list: 
1101 129 Selvarani C
Automatic linework (18:30- till end)
1102 129 Selvarani C
Survey > Linework code sets- for automatic linework
1103 129 Selvarani C
1104 129 Selvarani C
*Using Master view*
1105 129 Selvarani C
Uses-
1106 129 Selvarani C
copy styles from one drawing to other
1107 129 Selvarani C
copy drawing data from one drawing to other (data referencing)
1108 129 Selvarani C
1109 129 Selvarani C
*Civil 3d surface model*- from points- break lines
1110 129 Selvarani C
https://www.youtube.com/watch?v=wC40rdmDEMo
1111 129 Selvarani C
moving for example- point groups under point groups- 
1112 129 Selvarani C
1113 129 Selvarani C
*Civil 3D Planning and Analysis*
1114 129 Selvarani C
Workspace: Planning and Analysis
1115 129 Selvarani C
1. Working with Object data (GIS Attributes)
1116 129 Selvarani C
Map Setup> Define object data> New table> Define new object data table start defining fields
1117 129 Selvarani C
1118 129 Selvarani C
1119 130 Selvarani C
1120 130 Selvarani C
h1. Documentation- Rain Gauge
1121 130 Selvarani C
1122 130 Selvarani C
h2. Manual Rain Gauge
1123 130 Selvarani C
1124 130 Selvarani C
*Why it is important to comply to standards?*
1125 130 Selvarani C
1126 130 Selvarani C
1. Consistency for comparing rainfall data in different places within Auroville since rainfall varies in different parts of Auroville.
1127 130 Selvarani C
1128 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. 
1129 130 Selvarani C
1130 130 Selvarani C
*Proposed standards and ethics:*
1131 130 Selvarani C
1132 130 Selvarani C
1. The time of taking the reading - 08:30 am. 
1133 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.
1134 130 Selvarani C
1135 130 Selvarani C
2. Manual rain gauge typically used- green cylindrical and a collection jar.  
1136 130 Selvarani C
  
1137 130 Selvarani C
3. Measuring jar: 10 mm corresponding jar
1138 130 Selvarani C
1139 130 Selvarani C
 
1140 130 Selvarani C
Area of the rim of manual rain gauge= 200 square cm
1141 130 Selvarani C
Diameter of rim= approximately 16 cm
1142 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.
1143 130 Selvarani C
1144 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.
1145 130 Selvarani C
1146 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.
1147 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.
1148 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. 
1149 130 Selvarani C
1150 130 Selvarani C
8. In case of doubt in reading or incorrect measure, "incorrect measure" should be marked
1151 130 Selvarani C
1152 130 Selvarani C
1153 130 Selvarani C
*Ethics*
1154 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). 
1155 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. 
1156 130 Selvarani C
1157 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. 
1158 130 Selvarani C
1159 130 Selvarani C
*Important-*
1160 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.
1161 130 Selvarani C
CSR Geomatics Team is placed on first floor in CSR, Auroshilpam.
1162 130 Selvarani C
1163 130 Selvarani C
*AV rain data publication*: (http://gis.auroville.org.in/measures/raingauge_av).
1164 130 Selvarani C
1165 130 Selvarani C
Adding Rain gauge to our web portal (GISAF), following information is needed:
1166 130 Selvarani C
1. GPS co-ordinates of location of placing the rain gauge (can be obtained using mobile phones easily)
1167 130 Selvarani C
2. Name, place of residence & contact number- Mobile & Landline
1168 130 Selvarani C
1169 130 Selvarani C
h2. Automatic Rain Gauge
1170 130 Selvarani C
1171 130 Selvarani C
There is a possibility of publishing rain data coming from Automatic rain gauges like (id 15, auro orchard) and Weather stations. 
1172 130 Selvarani C
For Automatic rain gauges, we can upload the files coming from the rain gauge directly into GISAF.
1173 130 Selvarani C
1174 130 Selvarani C
1175 130 Selvarani C
_Thank you for contribution towards a sustainable management of Water in Auroville through Data collection._
1176 130 Selvarani C
1177 130 Selvarani C
1178 131 Selvarani C
1179 131 Selvarani C
h1. Documentation- Wells Monitoring (Manual and Automatic / Piezometer by Bala)
1180 131 Selvarani C
1181 131 Selvarani C
h2. Manual- Using tape with a sensor
1182 131 Selvarani C
1183 131 Selvarani C
Timings: The person assigned the job of monitoring collects the readings in three slots.
1184 131 Selvarani C
1185 131 Selvarani C
1.	Between 6 am to 7 am till about 9 am to 10 am.
1186 131 Selvarani C
2.	Between 11 am and 1 pm
1187 131 Selvarani C
3.	Between 2 pm and 5 pm
1188 131 Selvarani C
1189 131 Selvarani C
Things required:
1190 131 Selvarani C
•	Notebook
1191 131 Selvarani C
•	Pen
1192 131 Selvarani C
•	Measuring tape
1193 131 Selvarani C
•	Vehicle for movement
1194 131 Selvarani C
1195 131 Selvarani C
1196 131 Selvarani C
*Ethics*- 
1197 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.
1198 131 Selvarani C
•	The monitor should have contact numbers of the person in charge/ care taker for any communication.
1199 131 Selvarani C
•	If the monitoring is stopped for any reason at any point, the monitor should communicate the same to the person concerned.
1200 131 Selvarani C
•	The monitor shall take responsibility to inform any kind of changes in a well in terms of its functioning etc.
1201 131 Selvarani C
•	The monitor should report to the CSR Geomatics Team who has responsibility to publish data.
1202 131 Selvarani C
•	The monitor published the data to the website and works with the geomatics team.
1203 131 Selvarani C
1204 131 Selvarani C
1205 131 Selvarani C
*Definitions*:
1206 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. 
1207 131 Selvarani C
1208 131 Selvarani C
*Well type*
1209 131 Selvarani C
1.	Open
1210 131 Selvarani C
2.	Borewell
1211 131 Selvarani C
3.	Dug cum borewell
1212 131 Selvarani C
1213 131 Selvarani C
*Well status*
1214 131 Selvarani C
1.	In use
1215 131 Selvarani C
2.	Not in use
1216 131 Selvarani C
3.	Closed
1217 131 Selvarani C
1218 131 Selvarani C
*Pump Status*
1219 131 Selvarani C
1.	Functioning
1220 131 Selvarani C
2.	Not functioning
1221 131 Selvarani C
1222 131 Selvarani C
*Pump Automation*
1223 131 Selvarani C
1.	Manual 
1224 131 Selvarani C
2.	Automatic
1225 131 Selvarani C
1226 131 Selvarani C
* Non-accessibility factors*
1227 131 Selvarani C
1.	Dogs
1228 131 Selvarani C
2.	Heavy slab
1229 131 Selvarani C
3.	Narrow casing
1230 131 Selvarani C
4.	enclosed/locked
1231 131 Selvarani C
5.	permission
1232 131 Selvarani C
1233 131 Selvarani C
*Data Matching Accuracy (reconnecting with harvest wells data)*
1234 131 Selvarani C
1.	High
1235 131 Selvarani C
2.	Medium
1236 131 Selvarani C
3.	Low
1237 131 Selvarani C
1238 131 Selvarani C
*Well coordinates*
1239 131 Selvarani C
For a new well, coordinates of the well position are taken on a mobile GPS.
1240 131 Selvarani C
Person In charge
1241 131 Selvarani C
For communication purpose, contact the person in charge as recorded in directory.
1242 131 Selvarani C
1243 131 Selvarani C
h2. Automatic- Piezometer (by bala, to be edited) 
1244 131 Selvarani C
1245 131 Selvarani C
The calibrations and setting are already done by Azha
1246 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
1247 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
1248 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.
1249 131 Selvarani C
The piezometer sometimes does not have proper signal and so it would not be able to send it
1250 131 Selvarani C
1251 132 Selvarani C
h1. Documentation- Flow meter by Bala
1252 132 Selvarani C
1253 132 Selvarani C
Flow meter – for checking the flow of water in pipe
1254 132 Selvarani C
1255 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.
1256 132 Selvarani C
we tested in the west water system pump in csr. then we test in many more place .
1257 132 Selvarani C
 ami, aurodam and buddha garden borewell pumps . we got request from the water service 
1258 132 Selvarani C
Cross check they flow meters .
1259 132 Selvarani C
 so before that  we want to know how our meter works. 
1260 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. 
1261 132 Selvarani C
we tested two times in  15 minutes.and one time 30 minutes,so we got variation between this three. 
1262 132 Selvarani C
we find 1,5 % error but the flow meret they said  1 % error only.
1263 132 Selvarani C
we cross checked the flow meter of the water service we find some error  in they meter also. 
1264 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.  
1265 132 Selvarani C
then we find some error in (AVWS) meter also.
1266 132 Selvarani C
It is used to check the flow of water in pipe
1267 132 Selvarani C
tools used 
1268 132 Selvarani C
First the outer diameter of the pipe has to be entered in the device. It is measured using Vernier caliper
1269 132 Selvarani C
Then the thickness of the pipe is set which is also measured using vernier
1270 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) 
1271 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
1272 132 Selvarani C
When the sensors are fixed the motor is turned on and the sensors send reading to the display device
1273 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.
1274 1 Philippe May
This was done in different places to check to flow rate
1275 132 Selvarani C
1276 177 Selvarani C
1277 133 Selvarani C
1278 133 Selvarani C
h1. Documentation- DST- Vegetation Indexing
1279 133 Selvarani C
1280 133 Selvarani C
h2. Steps for Dzetsaka Classification tool for Vegetation indexing in QGIS
1281 133 Selvarani C
1282 133 Selvarani C
 
1283 133 Selvarani C
 1. Install the plugin Dzetsaka classfication tool.
1284 133 Selvarani C
 2. Open the Raster from the Survey.
1285 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. 
1286 133 Selvarani C
     More the samples, better the indexing.
1287 133 Selvarani C
 4. Apply Dzetsaka Classification tool, Select the base raster and the sample- index polygon shapefile created in step 3.
1288 133 Selvarani C
 5. The result is a Raster with DN numbers specified in the Shapefile in step 3.
1289 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.
1290 133 Selvarani C
 7. Polygonise the Raster to Vector (From processing)
1291 133 Selvarani C
 8. Run the v.generalise tool on the shapefile. This tool removes the pixelated boundaries of the polygons in the Vector.
1292 133 Selvarani C
1293 134 Selvarani C
h1. Documentation- DST- Interpolation (Processing toolbox)
1294 134 Selvarani C
1295 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)* )
1296 134 Selvarani C
1297 134 Selvarani C
# Interpolate (Cubic spline) - SAGA
1298 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.
1299 134 Selvarani C
# V.surf.rst - GRASS
1300 134 Selvarani C
# Krigging - SAGA
1301 1 Philippe May
1302 181 Selvarani C
[[Documentation- DST- Survey- Office workflow]]  - *%{color:RED} to be written%*
1303 135 Selvarani C
1304 135 Selvarani C
h1. From CAD to GIS by Giulio
1305 135 Selvarani C
1306 135 Selvarani C
*FEATURES CREATION*
1307 135 Selvarani C
1.	Assign a CRS to the drawing (TM-AUSPOS) (MAPCSLIBRARY command)
1308 135 Selvarani C
2.	Create features in CAD (Points, lines, polygons)
1309 135 Selvarani C
3.	Export shapefile (a) from CAD (Output > DWG to SDF) (Convert to LL84 – 3D)
1310 135 Selvarani C
1311 135 Selvarani C
*FEATURES IMPORT INTO DB FIRST TIME*
1312 135 Selvarani C
4.	Create zip file of the shapefile
1313 135 Selvarani C
5.	Upload into the GISAF Shapefiles Basket
1314 135 Selvarani C
6.	Import the shapefile into DB
1315 135 Selvarani C
7.	Save the shapefile on Local Machine
1316 135 Selvarani C
1317 135 Selvarani C
*FEATURES IMPORT INTO DB EVERYTIME*
1318 135 Selvarani C
8.	Combine the new features to corresponding last shape files (Insert the process here).
1319 135 Selvarani C
9.	Follow step 4-8 again
1320 135 Selvarani C
1321 135 Selvarani C
*FEATURES EDITING IN QGIS*
1322 135 Selvarani C
10.	Open the table in QGis
1323 135 Selvarani C
11.	Save as a shapefile (b) in TM AUSPOS CRS
1324 135 Selvarani C
12.	In CAD, open a new drawing and assign AUSPOS CRS
1325 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
1326 135 Selvarani C
14.	Edit features
1327 135 Selvarani C
15.	Change workspace into “Planning and analysis”
1328 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)
1329 135 Selvarani C
1330 135 Selvarani C
*FEATURES IMPORT INTO DB*
1331 135 Selvarani C
17.	Create zip file of the shapefile
1332 135 Selvarani C
18.	Upload into the GISAF Shapefiles Basket
1333 135 Selvarani C
19.	Import the shapefile into DB
1334 135 Selvarani C
20.	Delete the shapefile from Local Machine
1335 135 Selvarani C
1336 135 Selvarani C
1337 182 Selvarani C
1338 1 Philippe May
1339 136 Selvarani C
h1. QGIS- Miscellaneous
1340 136 Selvarani C
1341 136 Selvarani C
*QGIS Introduction:*
1342 136 Selvarani C
https://www.birdseyeviewgis.com/blog/2018/2/22/my-favorite-features-of-qgis-30to-date
1343 136 Selvarani C
3D visualization of raster DEM- https://www.youtube.com/watch?v=2KrCsbP0kUs
1344 136 Selvarani C
1345 136 Selvarani C
*Spatial query:* 
1346 136 Selvarani C
Spatial Query is selection of features that satisfies a certain condition which relates to other features in a space.
1347 136 Selvarani C
Using plugin- Spatial query
1348 136 Selvarani C
http://www.geodose.com/2018/03/spatial-query-in-qgis-3.html
1349 136 Selvarani C
Labelling:
1350 136 Selvarani C
Labelling with more than one field names and in different lines
1351 136 Selvarani C
|| '\n' ||
1352 136 Selvarani C
1353 136 Selvarani C
1354 136 Selvarani C
1355 136 Selvarani C
*Hierarchy of extensions*
1356 136 Selvarani C
1357 136 Selvarani C
File levels and their uses.
1358 136 Selvarani C
https://nathanw.net/2014/03/22/all-the-q-files/
1359 136 Selvarani C
1360 136 Selvarani C
+The Project file (.qgs)+
1361 136 Selvarani C
It contains: Layer source pointer + Style information + Composers + a whole heap of other stuff
1362 136 Selvarani C
1363 136 Selvarani C
+The Layer Definition file (.qlr)+
1364 136 Selvarani C
It contains: Layer source pointer + Style information
1365 136 Selvarani C
1366 136 Selvarani C
+The QML file (.qml)+
1367 136 Selvarani C
It contains: Style information
1368 136 Selvarani C
1369 59 Giulio Di Anastasio
h2. Giulio's documentation
1370 52 Giulio Di Anastasio
1371 183 Selvarani C
1372 137 Selvarani C
1373 137 Selvarani C
h1. Documentation - Reconciliation of points using Gisaf
1374 137 Selvarani C
1375 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.
1376 137 Selvarani C
1377 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).
1378 137 Selvarani C
1379 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]].
1380 137 Selvarani C
1381 137 Selvarani C
1382 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.
1383 137 Selvarani C
1384 137 Selvarani C
1385 137 Selvarani C
PLEASE NOTE: 
1386 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+*.
1387 137 Selvarani C
1388 137 Selvarani C
h2. How to perform Reconciliation
1389 137 Selvarani C
1390 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
1391 137 Selvarani C
1392 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).
1393 137 Selvarani C
1394 137 Selvarani C
Under it, in the field "Original ID", the original point number of the point to be reconciled is to be entered.
1395 137 Selvarani C
1396 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.
1397 137 Selvarani C
1398 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.
1399 137 Selvarani C
1400 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.
1401 137 Selvarani C
1402 138 Selvarani C
h1. Documentation - Status and Status Changes
1403 138 Selvarani C
1404 138 Selvarani C
Status have been created to keep track og changes in surveyed features.
1405 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.
1406 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.
1407 138 Selvarani C
1408 138 Selvarani C
Status have been defined as follows:
1409 138 Selvarani C
N - New Work
1410 138 Selvarani C
E - Existing o remain
1411 138 Selvarani C
D - Existing to demolish, Demolished or Changed
1412 138 Selvarani C
F- Future work, Proposed feature
1413 138 Selvarani C
T - Temporary work
1414 138 Selvarani C
M - Item to be moved
1415 138 Selvarani C
X - Not in contract
1416 138 Selvarani C
1417 138 Selvarani C
1418 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).
1419 138 Selvarani C
It needs to be done manually, one feature (point, line, polygon) at a time.
1420 138 Selvarani C
1421 138 Selvarani C
1422 1 Philippe May
In the future Status changes might be incorporated in the Admin panel.
1423 138 Selvarani C
1424 185 Selvarani C
1425 67 Giulio Di Anastasio
1426 139 Selvarani C
h1. Documentation - Tags retained after re-import of same geometry
1427 139 Selvarani C
1428 139 Selvarani C
Documentation - Tags retained after re-import of same geometry
1429 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.
1430 139 Selvarani C
The result was that lines did not inherit the attributes survey date, accuracy, equipment, surveyor.
1431 139 Selvarani C
Nevertheless lines were displayed on the Gisaf map, without these attributes, and tags were given to some of these lines.
1432 139 Selvarani C
1433 139 Selvarani C
The values for the two tables ("Accuracy", "Accuracy") have been corrected, ambiguity resolved.
1434 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.
1435 139 Selvarani C
1436 139 Selvarani C
4 August 2020
1437 139 Selvarani C
1438 67 Giulio Di Anastasio
h1. Access to data
1439 67 Giulio Di Anastasio
1440 67 Giulio Di Anastasio
h2. Connection to server directly from CSR
1441 67 Giulio Di Anastasio
1442 67 Giulio Di Anastasio
To connect to the server directly without going through Aurinoco server, the correct url is
1443 67 Giulio Di Anastasio
http://gis.csr.av
1444 67 Giulio Di Anastasio
1445 67 Giulio Di Anastasio
h2. Connection to Gisaf via QGis through WFS / OGC API
1446 67 Giulio Di Anastasio
1447 67 Giulio Di Anastasio
This works only on QGis from version 3.14.15 onward
1448 67 Giulio Di Anastasio
1449 67 Giulio Di Anastasio
In the browser, click on WFS/OGC API, then right-click to create a new connection
1450 67 Giulio Di Anastasio
Give a name (e.g. OGC API Qgis Gisaf)
1451 67 Giulio Di Anastasio
Give the url https://gis.auroville.org.in/ogcapi
1452 67 Giulio Di Anastasio
1453 67 Giulio Di Anastasio
Under the WFS Options box, on Version dropdown, the default option "Maximum" works just fine
1454 67 Giulio Di Anastasio
Click on OK
1455 67 Giulio Di Anastasio
The list of layers will appear in the Browser under WFS/OGC API.
1456 68 Giulio Di Anastasio
1457 68 Giulio Di Anastasio
1458 68 Giulio Di Anastasio
h1. How to create a new projection in QGis
1459 68 Giulio Di Anastasio
1460 68 Giulio Di Anastasio
To create a new projection in QGis, go to menu "Settings", and click on "Custom Projections".
1461 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.
1462 68 Giulio Di Anastasio
Click on the green "+" sign on the right top part of the window to create a new projection.
1463 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).
1464 68 Giulio Di Anastasio
In the "Format" dropdown list, select "Proj String (legacy - Not Recommended)"
1465 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".
1466 68 Giulio Di Anastasio
1467 68 Giulio Di Anastasio
Finally, click on OK.
1468 68 Giulio Di Anastasio
1469 68 Giulio Di Anastasio
In a more explicit  way, the parameters mean the following:
1470 68 Giulio Di Anastasio
Map Projection:        TransverseMercator (TM)
1471 68 Giulio Di Anastasio
False Easting:          370455.6300
1472 68 Giulio Di Anastasio
False Northing:        1328608.9940
1473 68 Giulio Di Anastasio
Latitude of Origin:    12°00'57.79560" (DMS)   12.01605433 (DD)
1474 68 Giulio Di Anastasio
Central Meridian:     79°48'35.96164"  (DMS)   79.80998934 (DD)
1475 68 Giulio Di Anastasio
Scale Factor:             1.00000000
1476 68 Giulio Di Anastasio
Zone Width:              6.0°
1477 69 Giulio Di Anastasio
1478 69 Giulio Di Anastasio
h1. Elimination of Duplicate points – General criteria
1479 69 Giulio Di Anastasio
1480 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.
1481 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.
1482 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.
1483 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.
1484 69 Giulio Di Anastasio
How to identify duplicate points?
1485 69 Giulio Di Anastasio
The following criteria can be used:
1486 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)
1487 69 Giulio Di Anastasio
2.	The orig_id (serial number) of the points are not in series
1488 69 Giulio Di Anastasio
3.	The survey date is not the same
1489 69 Giulio Di Anastasio
4.	In case of trees, the species of trees is the same
1490 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)
1491 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.
1492 70 Giulio Di Anastasio
1493 70 Giulio Di Anastasio
1494 70 Giulio Di Anastasio
h1. Linework for the Survey Area
1495 70 Giulio Di Anastasio
1496 70 Giulio Di Anastasio
h2. 1.	Creation of Initial Linework in QGIS using Survey points import - (Ram, System 4)
1497 70 Giulio Di Anastasio
1498 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.
1499 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*.
1500 70 Giulio Di Anastasio
The Initial Linework for the Survey Area is also stored temporarily in 
1501 70 Giulio Di Anastasio
1502 74 Selvarani C
+D: > AVSM > Zone-Survey number (eg RZ-01) > Survey Area (eg J) > Temporary WD+
1503 70 Giulio Di Anastasio
1504 70 Giulio Di Anastasio
h2. Note: The line shapefiles / Geopackages shall be in CRS: TM AUSPOS
1505 70 Giulio Di Anastasio
1506 70 Giulio Di Anastasio
h2. 2.	Creation of final working drawing Shapefiles / Geopackages - (Selvarani, System 1)
1507 1 Philippe May
1508 1 Philippe May
Final working drawing Shapefiles / Geopackages are created from the Initial Linework of Survey Area.
1509 70 Giulio Di Anastasio
As the Surveyor draws all features as lines (both for lines and polygons features), the following actions shall be done:
1510 74 Selvarani C
1.	*If features are lines:*
1511 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).
1512 70 Giulio Di Anastasio
1513 70 Giulio Di Anastasio
h2. The CRS for the export shall be EPSG:4326 - WGS 84
1514 70 Giulio Di Anastasio
1515 74 Selvarani C
2.	*If features are polygons:*
1516 1 Philippe May
•	Lines shall be converted into polygons:
1517 74 Selvarani C
1518 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:
1519 87 Selvarani C
1520 84 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9760/Line%20to%20Polygon%20Menu.png!
1521 70 Giulio Di Anastasio
1522 86 Selvarani C
1523 1 Philippe May
The new window for “Lines to Polygons” conversion will appear:
1524 86 Selvarani C
1525 86 Selvarani C
1526 83 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9762/Lines%20to%20Polygon%20Window.png!
1527 1 Philippe May
1528 71 Giulio Di Anastasio
•	Always cross check the input layer, to make sure that the input layer is the active one
1529 71 Giulio Di Anastasio
•	Save the output in a temporary layer
1530 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)
1531 72 Giulio Di Anastasio
1532 74 Selvarani C
h2. The CRS for the export shall be EPSG:4326 - WGS 84
1533 74 Selvarani C
1534 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.
1535 1 Philippe May
1536 74 Selvarani C
h2. Linework for the whole Survey Zone
1537 74 Selvarani C
1538 74 Selvarani C
h2. 1.	Merging Shapefiles / Geopackages - (Selvarani, System 1)
1539 74 Selvarani C
1540 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.
1541 1 Philippe May
Master shapefiles / geopackages are merged with the Survey Area shapefiles / geopackages:
1542 72 Giulio Di Anastasio
•	To do it, go to “Vector” Menu, click on Geoprocessing Tools, then click on Union:
1543 72 Giulio Di Anastasio
1544 85 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9763/Union%20Menu.png!
1545 1 Philippe May
1546 1 Philippe May
1547 85 Selvarani C
The new window for “Union” will appear:
1548 1 Philippe May
1549 86 Selvarani C
1550 86 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9764/Union%20Window.png!
1551 73 Giulio Di Anastasio
1552 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).
1553 73 Giulio Di Anastasio
•	(The output can be saved to a file, as the CRS should already be EPSG4326 – WGS84.)
1554 73 Giulio Di Anastasio
1555 74 Selvarani C
h2. 2.	Storing Shapefiles / Geopackages - (Selvarani, System 1)
1556 74 Selvarani C
1557 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)
1558 73 Giulio Di Anastasio
Date in the name of Final Shapefile / Geopackage needs to be updated.
1559 73 Giulio Di Anastasio
Once the merging operation is completed, the copy of Master shapefile / geopackage is deleted from the Temp folder.
1560 73 Giulio Di Anastasio
1561 74 Selvarani C
h2. 3.	Topology check of merged shapefiles
1562 74 Selvarani C
1563 73 Giulio Di Anastasio
The topology checker is applied again on the merged shapefiles / geopackages.
1564 73 Giulio Di Anastasio
The “id_field” shall be removed from the attribute table.
1565 73 Giulio Di Anastasio
1566 74 Selvarani C
h2. 4.	Archive and replace the Master Shapefiles / Geopackages (Ram, System 4)
1567 74 Selvarani C
1568 73 Giulio Di Anastasio
Archive the previous master shapefiles / geopackages on system 4, and copy the new merged shapefiles / geopackages in its place.
1569 74 Selvarani C
*Then delete the Merged Shapefile / Geopackage folder from System 1.
1570 74 Selvarani C
*
1571 73 Giulio Di Anastasio
1572 74 Selvarani C
h2. 5.	Note about Shapefiles and Geopackages
1573 73 Giulio Di Anastasio
1574 73 Giulio Di Anastasio
All the above works are usually done using shapefile format, in QGIS latest version (3.16.3).
1575 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.
1576 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).
1577 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)
1578 223 Selvarani C
1579 223 Selvarani C
h1. Creating 3D Shapefile/Geopackage
1580 223 Selvarani C
1581 223 Selvarani C
While creating a Shapefile/Geopackage, the File name/Database-table name, Geometry type and CRS have to be entered.
1582 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).
1583 224 Giulio Di Anastasio
1584 224 Giulio Di Anastasio
h1. Exporting from QGis (shapefiles and/or geopackages) to CAD dxf format
1585 224 Giulio Di Anastasio
1586 226 Giulio Di Anastasio
An algorithm has been created by Selvarani, to see the whole process click here:
1587 226 Giulio Di Anastasio
https://redmine.auroville.org.in/projects/gis/wiki/Automatic_export_from_QGis_to_dxf