Project

General

Profile

Wiki » History » Version 96

Selvarani C, 26/02/2021 10:33

1 1 Philippe May
h1. Wiki
2 2 Philippe May
3 48 Philippe May
h2. About the Auroville CSR Geomatics Studio
4 48 Philippe May
5 48 Philippe May
We are a team working on geographical and related information with an engineering and scientific approach. The concept of *geomatics* is explained here: https://en.wikipedia.org/wiki/Geomatics.
6 48 Philippe May
7 48 Philippe May
We develop, maintain and publish data on this web site: https://gis.auroville.org.in.
8 48 Philippe May
9 48 Philippe May
h3. Team
10 48 Philippe May
11 48 Philippe May
Currently, the team consists of:
12 48 Philippe May
13 48 Philippe May
* Bala
14 48 Philippe May
15 48 Philippe May
* Giulio
16 48 Philippe May
17 48 Philippe May
* Philippe
18 48 Philippe May
19 48 Philippe May
* Raj
20 48 Philippe May
21 48 Philippe May
* Ram
22 48 Philippe May
23 48 Philippe May
* Selvarani
24 48 Philippe May
25 48 Philippe May
h3. Collaborations
26 1 Philippe May
27 91 Selvarani C
Quick report of the collaborations the Geomatics Team the areas of work.
28 45 Philippe May
29 89 Selvarani C
30 88 Selvarani C
h1. Collaborations
31 88 Selvarani C
32 88 Selvarani C
Collaborations/coordination with other other groups, etc
33 88 Selvarani C
 
34 88 Selvarani C
|_.CSR Geomatics Description of Activity / Research / Project|_.AA|_.AVF|_.LB|_.FAMC|_.WG|_.CSR|_.Talam|_.DST|
35 88 Selvarani C
|Topographic Survey of Auroville City Area in coordination with L’avenir d’Auroville: Matrimandir entire compound and Residential Zone Sector 1 completed, Sector 2 half completed|yes|||||||yes|
36 88 Selvarani C
|Topographic Survey of specific projects area: Vibrance, Wasteless, Cultural Zone along the Crown Road, Baraka, Gardens of Unexpected |  |  |  |  |  |  |  |  |
37 88 Selvarani C
| Collective wastewater treatment systems health check-up survey: 68 plants evaluated | yes |  |  |  | yes | yes |  | yes |
38 88 Selvarani C
| Manual weekly monitoring of water level in selected wells on Auroville land on approximately 50 wells (number fluctuates depending on local conditions) | yes |  |  |  | yes |  |  | yes |
39 88 Selvarani C
| Collection of rainfall data through manual raingauges distributed to Aurovilians: data received regularly from at least 7 raingauges |  |  |  |  | yes |  |  | yes |
40 88 Selvarani C
| Collection of weather data through automatic weather station installed at CSR: data collected every minute, stored in the database, and published online in real time |  |  |  |  | yes | yes |  | yes |
41 88 Selvarani C
| Collaboration with Land Board for survey of identified land boundary stones: collection of coordinates of Government boundary stones for georefering of cadastral maps |  | yes | yes |  |  |  |  |  |
42 88 Selvarani C
| Collaboration with AV Foundation for compilation of land ownership map: geographic land records as provided by AV Foundation, protected by login access |  | yes |  |  |  |  |  |  |
43 88 Selvarani C
| Collaboration with L’avenir d’Auroville for data sharing and coordinated system set-up: organisation of geographic data for unique online platform to enhance planning processes (initial stage) | yes |  |  |  |  |  |  |  |
44 88 Selvarani C
| Collaboration with L’avenir d’Auroville and FAMC for database links: structural work on procedures for linking databases already existing with various agencies | yes |  |  | yes |  |  |  |  |
45 88 Selvarani C
| Study of application of drone topographic survey in Auroville context: pilot test conducted on Residential Zone with outside drone survey agency | yes |  |  |  |  | yes |  | yes |
46 88 Selvarani C
| Study of open source software for drone topographic survey: testing of softwares like OpenDroneMap, MeshLab, CloudeCompare to evaluate work flow, processes and limitations |  |  |  |  |  | yes |  | yes |
47 88 Selvarani C
| Surface water modelling (ongoing): research on evaluation of surface water collection potential through automatic processing of field data |  |  |  |  |  | yes |  | yes |
48 88 Selvarani C
| Collaboration with TALAM on research on radio-transmission for automatic wells level monitoring (ongoing): evaluation of application of radio-transmitted signals for water-related monitoring and metering (selected borewells, flow meters) |  |  |  |  |  |  | yes | yes |
49 88 Selvarani C
| Organisation of data collected in Auroville in the past (ongoing): standardisation of data in geospatial database |  |  |  |  |  | yes |  |  |
50 88 Selvarani C
| Provision for basic statistical analyses of geographic-related data (indicators/dashboard) |  |  |  |  |  | yes |  | yes |
51 88 Selvarani C
| Publication of collected data in standardised format on web portal gis.auroville.org.in |  |  |  |  |  | yes |  | yes |
52 88 Selvarani C
53 88 Selvarani C
* AA : L'avenir d'Auroville
54 88 Selvarani C
* AVF : Auroville Foundation
55 88 Selvarani C
* LB : Auroville Land Board
56 88 Selvarani C
* FAMC : Auroville Funds and Assets Management Committee
57 88 Selvarani C
* WG : Auroville Water Group
58 88 Selvarani C
* CSR : Auroville Centre for Scientific Research
59 88 Selvarani C
* TALAM : a project under CSR
60 88 Selvarani C
* DST : Department of Science and Technology, Ministry of Science and Technology, New Delhi
61 88 Selvarani C
62 5 Philippe May
h2. Our workflow
63 2 Philippe May
64 92 Selvarani C
65 92 Selvarani C
h2. Surveys
66 92 Selvarani C
67 92 Selvarani C
Most field surveys are executed by our team of surveyors, using advanced DGPS equipment.
68 92 Selvarani C
Other surveyors might also be contracted.
69 92 Selvarani C
70 92 Selvarani C
71 92 Selvarani C
h2. CAD
72 92 Selvarani C
73 92 Selvarani C
The survey data are imported to a CAD software (Aurocad/Civil 3D).
74 93 Selvarani C
75 93 Selvarani C
h1. Editing shapefiles in Autocad
76 93 Selvarani C
77 93 Selvarani C
h2. FEATURES CREATION
78 93 Selvarani C
79 93 Selvarani C
1.	Assign a CRS to the drawing (TM-AUSPOS) (MAPCSLIBRARY command)
80 93 Selvarani C
2.	Create features in CAD (Points, lines, polygons)
81 93 Selvarani C
3.	Export shapefile (a) from CAD (Output > DWG to SDF) (Convert to LL84 – 3D)
82 93 Selvarani C
83 93 Selvarani C
h2. FEATURES IMPORT INTO DB
84 93 Selvarani C
85 93 Selvarani C
4.	Create zip file of the shapefile
86 93 Selvarani C
5.	Upload into the GISAF Shapefiles Basket
87 93 Selvarani C
6.	Import the shapefile into DB
88 93 Selvarani C
7.	Delete the shapefile from Local Machine
89 93 Selvarani C
90 93 Selvarani C
91 93 Selvarani C
h2. FEATURES EDITING
92 93 Selvarani C
93 93 Selvarani C
8.	Open the table in QGis
94 93 Selvarani C
9.	Save as a shapefile (b) in TM AUSPOS CRS
95 93 Selvarani C
10.	In CAD, open a new drawing and assign ASUPOS CRS
96 93 Selvarani C
11.	Import the shapefile (b) (MapImport) with all Object Data
97 93 Selvarani C
12.	Edit features
98 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)
99 93 Selvarani C
100 93 Selvarani C
101 93 Selvarani C
h2. FEATURES IMPORT INTO DB
102 93 Selvarani C
103 93 Selvarani C
14.	Create zip file of the shapefile
104 93 Selvarani C
15.	Upload into the GISAF Shapefiles Basket
105 93 Selvarani C
16.	Import the shapefile into DB
106 93 Selvarani C
17.	Delete the shapefile from Local Machine
107 92 Selvarani C
108 96 Selvarani C
 
109 92 Selvarani C
110 92 Selvarani C
h2. QGis
111 92 Selvarani C
112 92 Selvarani C
h3. Conventions
113 2 Philippe May
114 3 Philippe May
115 94 Selvarani C
h1. Shapefiles
116 94 Selvarani C
117 94 Selvarani C
We work with "QGis":https://en.wikipedia.org/wiki/QGIS , a widely used open source, free software for working on maps and geographical data.
118 94 Selvarani C
119 94 Selvarani C
"Shapefile":https://en.wikipedia.org/wiki/Shapefile is a standard file format for mapping, that Gisaf can import. QGis can open and save *shapefiles*.
120 94 Selvarani C
121 94 Selvarani C
We have defined some simple norms about these shapefiles for integration with Gisaf.
122 94 Selvarani C
123 94 Selvarani C
124 94 Selvarani C
125 94 Selvarani C
h2. Coordinate system
126 94 Selvarani C
127 94 Selvarani C
We use CRS SRID 32644.
128 94 Selvarani C
129 94 Selvarani C
130 94 Selvarani C
131 94 Selvarani C
h2. Column (attributes)
132 94 Selvarani C
133 94 Selvarani C
* All objects in a shapefile (layer) have a unique identifier named "id": numerical value.
134 94 Selvarani C
135 94 Selvarani C
136 94 Selvarani C
137 94 Selvarani C
h3. Field (attribute) names
138 94 Selvarani C
139 94 Selvarani C
* All fields are lower case (-UpperCase-, use: @lowercase@)
140 94 Selvarani C
141 94 Selvarani C
* They do not contain spaces, but underscores (-not this-, use: @but_that@)
142 94 Selvarani C
143 94 Selvarani C
* The field names cannot have more than 8 characters (-this_is_too_long-, use: @this_short@)
144 94 Selvarani C
145 94 Selvarani C
146 94 Selvarani C
h3. Attribute types
147 94 Selvarani C
148 94 Selvarani C
* The dates are written in ISO format: @YYYY-MM-DD@ (eg. @1968-02-25@)
149 94 Selvarani C
150 94 Selvarani C
h3. Fields to remove
151 94 Selvarani C
152 94 Selvarani C
* Eventually, remove the fields containing the coordinates: northing, easting, elevation, latitude, longitude, area, length, etc (these might be present when the data is imported from speadsheet)
153 94 Selvarani C
154 94 Selvarani C
h2. Foreign keys
155 94 Selvarani C
156 94 Selvarani C
We often deal with labels or categories of objects in a layer.
157 94 Selvarani C
158 94 Selvarani C
A common use case to explain: Alice creates a layer of stones, and wants to *tag* each stone with a rating: these are picked from a list of choices, like: _Beautiful_, _Interesting_, _Pretty_, etc.
159 94 Selvarani C
160 94 Selvarani C
For these kind of attribute: define a column like @rating_id@ (_something_ ending with @_id@) as a numerical value, and assign values 1, 2, 3, etc. The text is defined in another table (typically a CSV file), that looks like:
161 94 Selvarani C
162 94 Selvarani C
|_. id |_. name |
163 94 Selvarani C
| 1 | Beautiful |
164 94 Selvarani C
| 2 | Interesting |
165 94 Selvarani C
| 3 | Pretty |
166 94 Selvarani C
167 94 Selvarani C
h2. Code
168 94 Selvarani C
169 94 Selvarani C
We have defined a standard set of codes, that defines the type of data. They can be found here (TODO: add link).
170 94 Selvarani C
171 94 Selvarani C
Add a column @code_name@, matching with one the code, eg. @V25@ for TDEF.
172 94 Selvarani C
173 94 Selvarani C
h2. Surveyor
174 94 Selvarani C
175 94 Selvarani C
We keep a record of the people who realized the surveys (the _surveyors_).
176 94 Selvarani C
The shapefiles must contain an attribute @srvyr_id@, which refers to this table (TODO: add link).
177 94 Selvarani C
178 94 Selvarani C
h2. Accuracy
179 94 Selvarani C
180 94 Selvarani C
We keep a record of the accuracy of the surveys.
181 94 Selvarani C
The shapefiles must contain an attribute @accur_id@, which refers to this table (TODO: add link).
182 94 Selvarani C
183 94 Selvarani C
184 94 Selvarani C
h2. Date of survey
185 94 Selvarani C
186 94 Selvarani C
As nothing is absolutely permanent, it's also important to keep track of the date of the surveys: the shapefiles must contain an attribute @date@.
187 94 Selvarani C
188 94 Selvarani C
189 3 Philippe May
h2. Working with Gisaf
190 3 Philippe May
191 6 Philippe May
h3. Survey data
192 6 Philippe May
193 12 Philippe May
Raw survey data are contained in CSV files, typically downloaded from surveying instruments.
194 12 Philippe May
195 25 Philippe May
See more information of the process for the survey data (including a flow diagram): [[Survey data]]
196 12 Philippe May
197 12 Philippe May
h3. Categories
198 12 Philippe May
199 12 Philippe May
The categories define the types of the geographical features.
200 12 Philippe May
201 12 Philippe May
See [[Categories]]
202 6 Philippe May
203 6 Philippe May
204 1 Philippe May
h3. QGis: work on shapefiles
205 1 Philippe May
206 1 Philippe May
Go to [[shapefiles]].
207 5 Philippe May
208 5 Philippe May
209 18 Philippe May
h2. Data analysis
210 18 Philippe May
211 18 Philippe May
See [[Data analysis]]
212 18 Philippe May
213 18 Philippe May
214 5 Philippe May
215 5 Philippe May
h2. Hosting
216 5 Philippe May
217 5 Philippe May
The team is located in the CSR of Auroville.
218 5 Philippe May
219 5 Philippe May
We have setup a server for hosting the software and database. See [[CSR_server]] for technical information about the setup.
220 7 Philippe May
221 7 Philippe May
222 11 Philippe May
h3. Backup and restoration of the database
223 1 Philippe May
224 1 Philippe May
See [[db-support]]
225 17 Philippe May
226 17 Philippe May
227 17 Philippe May
h2. Gear
228 17 Philippe May
229 17 Philippe May
h3. Survey equipment
230 17 Philippe May
231 17 Philippe May
See [[survey equipment]]
232 17 Philippe May
233 17 Philippe May
h3. Weather station
234 17 Philippe May
235 17 Philippe May
See [[Ambient_Weather_weather_station]]
236 11 Philippe May
237 11 Philippe May
238 7 Philippe May
h2. Plan for future
239 7 Philippe May
240 8 Philippe May
Beside living well, see [[plan]].
241 8 Philippe May
242 49 Philippe May
h2. Other
243 1 Philippe May
244 50 Philippe May
* [[GDAL (OGR) tools]]
245 49 Philippe May
246 8 Philippe May
h2. Links and references
247 8 Philippe May
248 10 Philippe May
[[links]]
249 16 Philippe May
250 16 Philippe May
251 16 Philippe May
h2. Old docs
252 16 Philippe May
253 15 Philippe May
[[Shapefiles]]
254 15 Philippe May
[[Data (measurements, auxiliary tables)]]
255 16 Philippe May
256 13 Philippe May
h2. Pavneet's docs (imported from gisaf's wiki)
257 1 Philippe May
258 15 Philippe May
259 14 Philippe May
[[Rules of Map making - What all Maps should have!]]
260 14 Philippe May
[[Survey Database]]
261 14 Philippe May
[[Field to finish]]
262 14 Philippe May
[[Survey Data Post-Processing]]
263 14 Philippe May
[[Wells Documentation]]
264 14 Philippe May
[[Civil 3D useful commands]]
265 14 Philippe May
[[Online references for Civil 3D]]
266 1 Philippe May
[[connections in QGIS- using browser panel and Add postGIS]]
267 33 Pavneet Kaur
[[Reconcilation of Raw survey data using pgAdmin]]
268 22 Pavneet Kaur
[[importing RAW data to GISAF]]
269 26 Pavneet Kaur
[[Editing Z value of features in Shapefiles in QGIS]]
270 34 Pavneet Kaur
[[Miscellaneous- Civil 3D]]
271 36 Pavneet Kaur
[[Documentation- Rain Gauge]]
272 40 Pavneet Kaur
[[Documentation- Wells Monitoring (Piezometer by Bala)]]
273 40 Pavneet Kaur
[[Documentation- Flow meter, by Bala]]
274 42 Pavneet Kaur
[[Documentation- DST- Vegetation Indexing]]
275 44 Pavneet Kaur
[[Documentation- DST- Interpolation]]
276 43 Pavneet Kaur
[[Documentation- DST- Survey- Office workflow]]
277 40 Pavneet Kaur
[[From CAD to GIS, by Giulio]]
278 41 Pavneet Kaur
[[QGIS- Miscellaneous]]
279 52 Giulio Di Anastasio
280 1 Philippe May
h2. Giulio's documentation
281 59 Giulio Di Anastasio
282 52 Giulio Di Anastasio
[[Documentation - Reconciliation of points using Gisaf]]
283 65 Giulio Di Anastasio
[[Documentation - Status and Status Changes]]
284 66 Giulio Di Anastasio
[[Documentation - Tags retained after re-import of same geometry]]
285 67 Giulio Di Anastasio
286 67 Giulio Di Anastasio
287 67 Giulio Di Anastasio
h1. Access to data
288 67 Giulio Di Anastasio
289 67 Giulio Di Anastasio
h2. Connection to server directly from CSR
290 67 Giulio Di Anastasio
291 67 Giulio Di Anastasio
To connect to the server directly without going through Aurinoco server, the correct url is
292 67 Giulio Di Anastasio
http://gis.csr.av
293 67 Giulio Di Anastasio
294 67 Giulio Di Anastasio
h2. Connection to Gisaf via QGis through WFS / OGC API
295 67 Giulio Di Anastasio
296 67 Giulio Di Anastasio
This works only on QGis from version 3.14.15 onward
297 67 Giulio Di Anastasio
298 67 Giulio Di Anastasio
In the browser, click on WFS/OGC API, then right-click to create a new connection
299 67 Giulio Di Anastasio
Give a name (e.g. OGC API Qgis Gisaf)
300 67 Giulio Di Anastasio
Give the url https://gis.auroville.org.in/ogcapi
301 67 Giulio Di Anastasio
302 67 Giulio Di Anastasio
Under the WFS Options box, on Version dropdown, the default option "Maximum" works just fine
303 67 Giulio Di Anastasio
Click on OK
304 67 Giulio Di Anastasio
The list of layers will appear in the Browser under WFS/OGC API.
305 68 Giulio Di Anastasio
306 68 Giulio Di Anastasio
307 68 Giulio Di Anastasio
h1. How to create a new projection in QGis
308 68 Giulio Di Anastasio
309 68 Giulio Di Anastasio
To create a new projection in QGis, go to menu "Settings", and click on "Custom Projections".
310 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.
311 68 Giulio Di Anastasio
Click on the green "+" sign on the right top part of the window to create a new projection.
312 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).
313 68 Giulio Di Anastasio
In the "Format" dropdown list, select "Proj String (legacy - Not Recommended)"
314 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".
315 68 Giulio Di Anastasio
316 68 Giulio Di Anastasio
Finally, click on OK.
317 68 Giulio Di Anastasio
318 68 Giulio Di Anastasio
In a more explicit  way, the parameters mean the following:
319 68 Giulio Di Anastasio
Map Projection:        TransverseMercator (TM)
320 68 Giulio Di Anastasio
False Easting:          370455.6300
321 68 Giulio Di Anastasio
False Northing:        1328608.9940
322 68 Giulio Di Anastasio
Latitude of Origin:    12°00'57.79560" (DMS)   12.01605433 (DD)
323 68 Giulio Di Anastasio
Central Meridian:     79°48'35.96164"  (DMS)   79.80998934 (DD)
324 68 Giulio Di Anastasio
Scale Factor:             1.00000000
325 68 Giulio Di Anastasio
Zone Width:              6.0°
326 69 Giulio Di Anastasio
327 69 Giulio Di Anastasio
h1. Elimination of Duplicate points – General criteria
328 69 Giulio Di Anastasio
329 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.
330 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.
331 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.
332 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.
333 69 Giulio Di Anastasio
How to identify duplicate points?
334 69 Giulio Di Anastasio
The following criteria can be used:
335 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)
336 69 Giulio Di Anastasio
2.	The orig_id (serial number) of the points are not in series
337 69 Giulio Di Anastasio
3.	The survey date is not the same
338 69 Giulio Di Anastasio
4.	In case of trees, the species of trees is the same
339 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)
340 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.
341 70 Giulio Di Anastasio
342 70 Giulio Di Anastasio
343 70 Giulio Di Anastasio
h1. Linework for the Survey Area
344 70 Giulio Di Anastasio
345 70 Giulio Di Anastasio
h2. 1.	Creation of Initial Linework in QGIS using Survey points import - (Ram, System 4)
346 70 Giulio Di Anastasio
347 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.
348 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*.
349 70 Giulio Di Anastasio
The Initial Linework for the Survey Area is also stored temporarily in 
350 70 Giulio Di Anastasio
351 74 Selvarani C
+D: > AVSM > Zone-Survey number (eg RZ-01) > Survey Area (eg J) > Temporary WD+
352 70 Giulio Di Anastasio
353 70 Giulio Di Anastasio
h2. Note: The line shapefiles / Geopackages shall be in CRS: TM AUSPOS
354 70 Giulio Di Anastasio
355 70 Giulio Di Anastasio
h2. 2.	Creation of final working drawing Shapefiles / Geopackages - (Selvarani, System 1)
356 1 Philippe May
357 1 Philippe May
Final working drawing Shapefiles / Geopackages are created from the Initial Linework of Survey Area.
358 70 Giulio Di Anastasio
As the Surveyor draws all features as lines (both for lines and polygons features), the following actions shall be done:
359 74 Selvarani C
1.	*If features are lines:*
360 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).
361 70 Giulio Di Anastasio
362 70 Giulio Di Anastasio
h2. The CRS for the export shall be EPSG:4326 - WGS 84
363 70 Giulio Di Anastasio
364 74 Selvarani C
2.	*If features are polygons:*
365 1 Philippe May
•	Lines shall be converted into polygons:
366 74 Selvarani C
367 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:
368 87 Selvarani C
369 84 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9760/Line%20to%20Polygon%20Menu.png!
370 70 Giulio Di Anastasio
371 86 Selvarani C
372 1 Philippe May
The new window for “Lines to Polygons” conversion will appear:
373 86 Selvarani C
374 86 Selvarani C
375 83 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9762/Lines%20to%20Polygon%20Window.png!
376 1 Philippe May
377 71 Giulio Di Anastasio
•	Always cross check the input layer, to make sure that the input layer is the active one
378 71 Giulio Di Anastasio
•	Save the output in a temporary layer
379 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)
380 72 Giulio Di Anastasio
381 74 Selvarani C
h2. The CRS for the export shall be EPSG:4326 - WGS 84
382 74 Selvarani C
383 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.
384 1 Philippe May
385 74 Selvarani C
h2. Linework for the whole Survey Zone
386 74 Selvarani C
387 74 Selvarani C
h2. 1.	Merging Shapefiles / Geopackages - (Selvarani, System 1)
388 74 Selvarani C
389 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.
390 1 Philippe May
Master shapefiles / geopackages are merged with the Survey Area shapefiles / geopackages:
391 72 Giulio Di Anastasio
•	To do it, go to “Vector” Menu, click on Geoprocessing Tools, then click on Union:
392 72 Giulio Di Anastasio
393 85 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9763/Union%20Menu.png!
394 1 Philippe May
395 1 Philippe May
396 85 Selvarani C
The new window for “Union” will appear:
397 1 Philippe May
398 86 Selvarani C
399 86 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9764/Union%20Window.png!
400 73 Giulio Di Anastasio
401 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).
402 73 Giulio Di Anastasio
•	(The output can be saved to a file, as the CRS should already be EPSG4326 – WGS84.)
403 73 Giulio Di Anastasio
404 74 Selvarani C
h2. 2.	Storing Shapefiles / Geopackages - (Selvarani, System 1)
405 74 Selvarani C
406 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)
407 73 Giulio Di Anastasio
Date in the name of Final Shapefile / Geopackage needs to be updated.
408 73 Giulio Di Anastasio
Once the merging operation is completed, the copy of Master shapefile / geopackage is deleted from the Temp folder.
409 73 Giulio Di Anastasio
410 74 Selvarani C
h2. 3.	Topology check of merged shapefiles
411 74 Selvarani C
412 73 Giulio Di Anastasio
The topology checker is applied again on the merged shapefiles / geopackages.
413 73 Giulio Di Anastasio
The “id_field” shall be removed from the attribute table.
414 73 Giulio Di Anastasio
415 74 Selvarani C
h2. 4.	Archive and replace the Master Shapefiles / Geopackages (Ram, System 4)
416 74 Selvarani C
417 73 Giulio Di Anastasio
Archive the previous master shapefiles / geopackages on system 4, and copy the new merged shapefiles / geopackages in its place.
418 74 Selvarani C
*Then delete the Merged Shapefile / Geopackage folder from System 1.
419 74 Selvarani C
*
420 73 Giulio Di Anastasio
421 74 Selvarani C
h2. 5.	Note about Shapefiles and Geopackages
422 73 Giulio Di Anastasio
423 73 Giulio Di Anastasio
All the above works are usually done using shapefile format, in QGIS latest version (3.16.3).
424 77 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 notes, as Gisaf database does not accept the Multipolygon and Multiline geometry types.