Project

General

Profile

Wiki » History » Version 287

Giulio Di Anastasio, 06/05/2021 12:30

1 1 Philippe May
h1. %{color:BLUE}  Wiki%
2 227 Giulio Di Anastasio
3 232 Giulio Di Anastasio
h1. [[CSR Geomatics Team]]
4 231 Giulio Di Anastasio
5 229 Giulio Di Anastasio
h1. [[Collaborations]]
6 229 Giulio Di Anastasio
7 240 Giulio Di Anastasio
h1. [[Data Analysis]]
8 234 Giulio Di Anastasio
9 241 Giulio Di Anastasio
h1. [[CSR Geomatics Server Setup]]
10 234 Giulio Di Anastasio
11 245 Giulio Di Anastasio
h1. [[Database Backup and Restoration]]
12 243 Giulio Di Anastasio
13 243 Giulio Di Anastasio
h1. [[CAD to GIS Workflow]] %{color:RED}  - TO BE UPDATED%
14 248 Giulio Di Anastasio
15 246 Giulio Di Anastasio
h1. [[GIS Conventions]]
16 246 Giulio Di Anastasio
 
17 252 Giulio Di Anastasio
h1. [[Working with Gisaf]]
18 96 Selvarani C
19 92 Selvarani C
h1. [[Gisaf Workflow]]
20 252 Giulio Di Anastasio
21 256 Giulio Di Anastasio
h1. [[GIS to CAD Workflow]] %{color:RED}  - TO BE UPDATED%
22 94 Selvarani C
23 285 Giulio Di Anastasio
h1. [[Rain gauges]]
24 285 Giulio Di Anastasio
25 257 Giulio Di Anastasio
h1. [[Weather Station]]
26 142 Selvarani C
27 259 Giulio Di Anastasio
h1. [[GDAL - Useful Tips]]
28 5 Philippe May
29 262 Giulio Di Anastasio
h1. [[Gisaf - Auxiliary Data (non-geographical data)]]
30 143 Selvarani C
31 264 Giulio Di Anastasio
h1. [[QGis - Useful Tips]]
32 264 Giulio Di Anastasio
33 266 Giulio Di Anastasio
h1. [[AutoCAD Civil 3D - Useful Tips]]
34 266 Giulio Di Anastasio
35 280 Giulio Di Anastasio
h1. [[Wells]]
36 8 Philippe May
37 272 Giulio Di Anastasio
h1. [[Gisaf Data Modifications]]
38 272 Giulio Di Anastasio
39 274 Giulio Di Anastasio
h1. [[Other Useful Softwares]]
40 272 Giulio Di Anastasio
41 286 Giulio Di Anastasio
h1. [[Portable Ultrasonic Flow Meter]]
42 262 Giulio Di Anastasio
43 1 Philippe May
44 274 Giulio Di Anastasio
45 274 Giulio Di Anastasio
46 107 Selvarani C
47 110 Selvarani C
48 110 Selvarani C
49 110 Selvarani C
50 113 Selvarani C
51 270 Giulio Di Anastasio
52 270 Giulio Di Anastasio
53 119 Selvarani C
54 119 Selvarani C
55 128 Selvarani C
56 128 Selvarani C
57 129 Selvarani C
58 1 Philippe May
59 132 Selvarani C
60 177 Selvarani C
61 133 Selvarani C
62 133 Selvarani C
63 133 Selvarani C
64 134 Selvarani C
h1. Documentation- DST- Interpolation (Processing toolbox)
65 134 Selvarani C
66 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)* )
67 134 Selvarani C
68 134 Selvarani C
# Interpolate (Cubic spline) - SAGA
69 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.
70 134 Selvarani C
# V.surf.rst - GRASS
71 134 Selvarani C
# Krigging - SAGA
72 1 Philippe May
73 181 Selvarani C
[[Documentation- DST- Survey- Office workflow]]  - *%{color:RED} to be written%*
74 135 Selvarani C
75 135 Selvarani C
h1. From CAD to GIS by Giulio
76 135 Selvarani C
77 135 Selvarani C
*FEATURES CREATION*
78 135 Selvarani C
1.	Assign a CRS to the drawing (TM-AUSPOS) (MAPCSLIBRARY command)
79 135 Selvarani C
2.	Create features in CAD (Points, lines, polygons)
80 135 Selvarani C
3.	Export shapefile (a) from CAD (Output > DWG to SDF) (Convert to LL84 – 3D)
81 135 Selvarani C
82 135 Selvarani C
*FEATURES IMPORT INTO DB FIRST TIME*
83 135 Selvarani C
4.	Create zip file of the shapefile
84 135 Selvarani C
5.	Upload into the GISAF Shapefiles Basket
85 135 Selvarani C
6.	Import the shapefile into DB
86 135 Selvarani C
7.	Save the shapefile on Local Machine
87 135 Selvarani C
88 135 Selvarani C
*FEATURES IMPORT INTO DB EVERYTIME*
89 135 Selvarani C
8.	Combine the new features to corresponding last shape files (Insert the process here).
90 135 Selvarani C
9.	Follow step 4-8 again
91 135 Selvarani C
92 135 Selvarani C
*FEATURES EDITING IN QGIS*
93 135 Selvarani C
10.	Open the table in QGis
94 135 Selvarani C
11.	Save as a shapefile (b) in TM AUSPOS CRS
95 135 Selvarani C
12.	In CAD, open a new drawing and assign AUSPOS CRS
96 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
97 135 Selvarani C
14.	Edit features
98 135 Selvarani C
15.	Change workspace into “Planning and analysis”
99 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)
100 135 Selvarani C
101 135 Selvarani C
*FEATURES IMPORT INTO DB*
102 135 Selvarani C
17.	Create zip file of the shapefile
103 135 Selvarani C
18.	Upload into the GISAF Shapefiles Basket
104 135 Selvarani C
19.	Import the shapefile into DB
105 135 Selvarani C
20.	Delete the shapefile from Local Machine
106 135 Selvarani C
107 135 Selvarani C
108 182 Selvarani C
109 1 Philippe May
110 136 Selvarani C
h1. QGIS- Miscellaneous
111 136 Selvarani C
112 136 Selvarani C
*QGIS Introduction:*
113 136 Selvarani C
https://www.birdseyeviewgis.com/blog/2018/2/22/my-favorite-features-of-qgis-30to-date
114 136 Selvarani C
3D visualization of raster DEM- https://www.youtube.com/watch?v=2KrCsbP0kUs
115 136 Selvarani C
116 136 Selvarani C
*Spatial query:* 
117 136 Selvarani C
Spatial Query is selection of features that satisfies a certain condition which relates to other features in a space.
118 136 Selvarani C
Using plugin- Spatial query
119 136 Selvarani C
http://www.geodose.com/2018/03/spatial-query-in-qgis-3.html
120 136 Selvarani C
Labelling:
121 136 Selvarani C
Labelling with more than one field names and in different lines
122 136 Selvarani C
|| '\n' ||
123 136 Selvarani C
124 136 Selvarani C
125 136 Selvarani C
126 136 Selvarani C
*Hierarchy of extensions*
127 136 Selvarani C
128 136 Selvarani C
File levels and their uses.
129 136 Selvarani C
https://nathanw.net/2014/03/22/all-the-q-files/
130 136 Selvarani C
131 136 Selvarani C
+The Project file (.qgs)+
132 136 Selvarani C
It contains: Layer source pointer + Style information + Composers + a whole heap of other stuff
133 136 Selvarani C
134 136 Selvarani C
+The Layer Definition file (.qlr)+
135 136 Selvarani C
It contains: Layer source pointer + Style information
136 136 Selvarani C
137 136 Selvarani C
+The QML file (.qml)+
138 136 Selvarani C
It contains: Style information
139 136 Selvarani C
140 59 Giulio Di Anastasio
h2. Giulio's documentation
141 52 Giulio Di Anastasio
142 183 Selvarani C
143 137 Selvarani C
144 137 Selvarani C
h1. Documentation - Reconciliation of points using Gisaf
145 137 Selvarani C
146 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.
147 137 Selvarani C
148 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).
149 137 Selvarani C
150 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]].
151 137 Selvarani C
152 137 Selvarani C
153 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.
154 137 Selvarani C
155 137 Selvarani C
156 137 Selvarani C
PLEASE NOTE: 
157 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+*.
158 137 Selvarani C
159 137 Selvarani C
h2. How to perform Reconciliation
160 137 Selvarani C
161 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
162 137 Selvarani C
163 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).
164 137 Selvarani C
165 137 Selvarani C
Under it, in the field "Original ID", the original point number of the point to be reconciled is to be entered.
166 137 Selvarani C
167 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.
168 137 Selvarani C
169 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.
170 137 Selvarani C
171 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.
172 137 Selvarani C
173 138 Selvarani C
h1. Documentation - Status and Status Changes
174 138 Selvarani C
175 138 Selvarani C
Status have been created to keep track og changes in surveyed features.
176 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.
177 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.
178 138 Selvarani C
179 138 Selvarani C
Status have been defined as follows:
180 138 Selvarani C
N - New Work
181 138 Selvarani C
E - Existing o remain
182 138 Selvarani C
D - Existing to demolish, Demolished or Changed
183 138 Selvarani C
F- Future work, Proposed feature
184 138 Selvarani C
T - Temporary work
185 138 Selvarani C
M - Item to be moved
186 138 Selvarani C
X - Not in contract
187 138 Selvarani C
188 138 Selvarani C
189 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).
190 138 Selvarani C
It needs to be done manually, one feature (point, line, polygon) at a time.
191 138 Selvarani C
192 138 Selvarani C
193 1 Philippe May
In the future Status changes might be incorporated in the Admin panel.
194 138 Selvarani C
195 185 Selvarani C
196 67 Giulio Di Anastasio
197 139 Selvarani C
h1. Documentation - Tags retained after re-import of same geometry
198 139 Selvarani C
199 139 Selvarani C
Documentation - Tags retained after re-import of same geometry
200 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.
201 139 Selvarani C
The result was that lines did not inherit the attributes survey date, accuracy, equipment, surveyor.
202 139 Selvarani C
Nevertheless lines were displayed on the Gisaf map, without these attributes, and tags were given to some of these lines.
203 139 Selvarani C
204 139 Selvarani C
The values for the two tables ("Accuracy", "Accuracy") have been corrected, ambiguity resolved.
205 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.
206 139 Selvarani C
207 139 Selvarani C
4 August 2020
208 139 Selvarani C
209 67 Giulio Di Anastasio
h1. Access to data
210 67 Giulio Di Anastasio
211 67 Giulio Di Anastasio
h2. Connection to server directly from CSR
212 67 Giulio Di Anastasio
213 67 Giulio Di Anastasio
To connect to the server directly without going through Aurinoco server, the correct url is
214 67 Giulio Di Anastasio
http://gis.csr.av
215 67 Giulio Di Anastasio
216 67 Giulio Di Anastasio
h2. Connection to Gisaf via QGis through WFS / OGC API
217 67 Giulio Di Anastasio
218 67 Giulio Di Anastasio
This works only on QGis from version 3.14.15 onward
219 67 Giulio Di Anastasio
220 67 Giulio Di Anastasio
In the browser, click on WFS/OGC API, then right-click to create a new connection
221 67 Giulio Di Anastasio
Give a name (e.g. OGC API Qgis Gisaf)
222 67 Giulio Di Anastasio
Give the url https://gis.auroville.org.in/ogcapi
223 67 Giulio Di Anastasio
224 67 Giulio Di Anastasio
Under the WFS Options box, on Version dropdown, the default option "Maximum" works just fine
225 67 Giulio Di Anastasio
Click on OK
226 67 Giulio Di Anastasio
The list of layers will appear in the Browser under WFS/OGC API.
227 68 Giulio Di Anastasio
228 68 Giulio Di Anastasio
229 68 Giulio Di Anastasio
h1. How to create a new projection in QGis
230 68 Giulio Di Anastasio
231 68 Giulio Di Anastasio
To create a new projection in QGis, go to menu "Settings", and click on "Custom Projections".
232 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.
233 68 Giulio Di Anastasio
Click on the green "+" sign on the right top part of the window to create a new projection.
234 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).
235 68 Giulio Di Anastasio
In the "Format" dropdown list, select "Proj String (legacy - Not Recommended)"
236 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".
237 68 Giulio Di Anastasio
238 68 Giulio Di Anastasio
Finally, click on OK.
239 68 Giulio Di Anastasio
240 68 Giulio Di Anastasio
In a more explicit  way, the parameters mean the following:
241 68 Giulio Di Anastasio
Map Projection:        TransverseMercator (TM)
242 68 Giulio Di Anastasio
False Easting:          370455.6300
243 68 Giulio Di Anastasio
False Northing:        1328608.9940
244 68 Giulio Di Anastasio
Latitude of Origin:    12°00'57.79560" (DMS)   12.01605433 (DD)
245 68 Giulio Di Anastasio
Central Meridian:     79°48'35.96164"  (DMS)   79.80998934 (DD)
246 68 Giulio Di Anastasio
Scale Factor:             1.00000000
247 68 Giulio Di Anastasio
Zone Width:              6.0°
248 69 Giulio Di Anastasio
249 69 Giulio Di Anastasio
h1. Elimination of Duplicate points – General criteria
250 69 Giulio Di Anastasio
251 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.
252 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.
253 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.
254 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.
255 69 Giulio Di Anastasio
How to identify duplicate points?
256 69 Giulio Di Anastasio
The following criteria can be used:
257 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)
258 69 Giulio Di Anastasio
2.	The orig_id (serial number) of the points are not in series
259 69 Giulio Di Anastasio
3.	The survey date is not the same
260 69 Giulio Di Anastasio
4.	In case of trees, the species of trees is the same
261 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)
262 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.
263 70 Giulio Di Anastasio
264 70 Giulio Di Anastasio
265 70 Giulio Di Anastasio
h1. Linework for the Survey Area
266 70 Giulio Di Anastasio
267 70 Giulio Di Anastasio
h2. 1.	Creation of Initial Linework in QGIS using Survey points import - (Ram, System 4)
268 70 Giulio Di Anastasio
269 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.
270 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*.
271 70 Giulio Di Anastasio
The Initial Linework for the Survey Area is also stored temporarily in 
272 70 Giulio Di Anastasio
273 74 Selvarani C
+D: > AVSM > Zone-Survey number (eg RZ-01) > Survey Area (eg J) > Temporary WD+
274 70 Giulio Di Anastasio
275 70 Giulio Di Anastasio
h2. Note: The line shapefiles / Geopackages shall be in CRS: TM AUSPOS
276 70 Giulio Di Anastasio
277 70 Giulio Di Anastasio
h2. 2.	Creation of final working drawing Shapefiles / Geopackages - (Selvarani, System 1)
278 1 Philippe May
279 1 Philippe May
Final working drawing Shapefiles / Geopackages are created from the Initial Linework of Survey Area.
280 70 Giulio Di Anastasio
As the Surveyor draws all features as lines (both for lines and polygons features), the following actions shall be done:
281 74 Selvarani C
1.	*If features are lines:*
282 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).
283 70 Giulio Di Anastasio
284 70 Giulio Di Anastasio
h2. The CRS for the export shall be EPSG:4326 - WGS 84
285 70 Giulio Di Anastasio
286 74 Selvarani C
2.	*If features are polygons:*
287 1 Philippe May
•	Lines shall be converted into polygons:
288 74 Selvarani C
289 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:
290 87 Selvarani C
291 84 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9760/Line%20to%20Polygon%20Menu.png!
292 70 Giulio Di Anastasio
293 86 Selvarani C
294 1 Philippe May
The new window for “Lines to Polygons” conversion will appear:
295 86 Selvarani C
296 86 Selvarani C
297 83 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9762/Lines%20to%20Polygon%20Window.png!
298 1 Philippe May
299 71 Giulio Di Anastasio
•	Always cross check the input layer, to make sure that the input layer is the active one
300 71 Giulio Di Anastasio
•	Save the output in a temporary layer
301 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)
302 72 Giulio Di Anastasio
303 74 Selvarani C
h2. The CRS for the export shall be EPSG:4326 - WGS 84
304 74 Selvarani C
305 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.
306 1 Philippe May
307 74 Selvarani C
h2. Linework for the whole Survey Zone
308 74 Selvarani C
309 74 Selvarani C
h2. 1.	Merging Shapefiles / Geopackages - (Selvarani, System 1)
310 74 Selvarani C
311 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.
312 1 Philippe May
Master shapefiles / geopackages are merged with the Survey Area shapefiles / geopackages:
313 72 Giulio Di Anastasio
•	To do it, go to “Vector” Menu, click on Geoprocessing Tools, then click on Union:
314 72 Giulio Di Anastasio
315 85 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9763/Union%20Menu.png!
316 1 Philippe May
317 1 Philippe May
318 85 Selvarani C
The new window for “Union” will appear:
319 1 Philippe May
320 86 Selvarani C
321 86 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9764/Union%20Window.png!
322 73 Giulio Di Anastasio
323 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).
324 73 Giulio Di Anastasio
•	(The output can be saved to a file, as the CRS should already be EPSG4326 – WGS84.)
325 73 Giulio Di Anastasio
326 74 Selvarani C
h2. 2.	Storing Shapefiles / Geopackages - (Selvarani, System 1)
327 74 Selvarani C
328 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)
329 73 Giulio Di Anastasio
Date in the name of Final Shapefile / Geopackage needs to be updated.
330 73 Giulio Di Anastasio
Once the merging operation is completed, the copy of Master shapefile / geopackage is deleted from the Temp folder.
331 73 Giulio Di Anastasio
332 74 Selvarani C
h2. 3.	Topology check of merged shapefiles
333 74 Selvarani C
334 73 Giulio Di Anastasio
The topology checker is applied again on the merged shapefiles / geopackages.
335 73 Giulio Di Anastasio
The “id_field” shall be removed from the attribute table.
336 73 Giulio Di Anastasio
337 74 Selvarani C
h2. 4.	Archive and replace the Master Shapefiles / Geopackages (Ram, System 4)
338 74 Selvarani C
339 73 Giulio Di Anastasio
Archive the previous master shapefiles / geopackages on system 4, and copy the new merged shapefiles / geopackages in its place.
340 74 Selvarani C
*Then delete the Merged Shapefile / Geopackage folder from System 1.
341 74 Selvarani C
*
342 73 Giulio Di Anastasio
343 74 Selvarani C
h2. 5.	Note about Shapefiles and Geopackages
344 73 Giulio Di Anastasio
345 73 Giulio Di Anastasio
All the above works are usually done using shapefile format, in QGIS latest version (3.16.3).
346 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.
347 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).
348 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)
349 223 Selvarani C
350 223 Selvarani C
h1. Creating 3D Shapefile/Geopackage
351 223 Selvarani C
352 223 Selvarani C
While creating a Shapefile/Geopackage, the File name/Database-table name, Geometry type and CRS have to be entered.
353 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).
354 224 Giulio Di Anastasio
355 224 Giulio Di Anastasio
h1. Exporting from QGis (shapefiles and/or geopackages) to CAD dxf format
356 224 Giulio Di Anastasio
357 226 Giulio Di Anastasio
An algorithm has been created by Selvarani, to see the whole process click here:
358 226 Giulio Di Anastasio
https://redmine.auroville.org.in/projects/gis/wiki/Automatic_export_from_QGis_to_dxf