Project

General

Profile

Wiki » History » Version 224

Giulio Di Anastasio, 29/04/2021 16:55

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