Project

General

Profile

Wiki » History » Version 237

Giulio Di Anastasio, 03/05/2021 10:46

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