Project

General

Profile

Wiki » History » Version 258

Giulio Di Anastasio, 05/05/2021 15:56

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 255 Giulio Di Anastasio
h1. [[Categories - Survey codes]]
22 255 Giulio Di Anastasio
23 256 Giulio Di Anastasio
h1. [[GIS to CAD Workflow]] %{color:RED}  - TO BE UPDATED%
24 94 Selvarani C
25 257 Giulio Di Anastasio
h1. [[Weather Station]]
26 142 Selvarani C
27 5 Philippe May
28 143 Selvarani C
29 17 Philippe May
30 8 Philippe May
31 107 Selvarani C
h1. Plan
32 107 Selvarani C
33 107 Selvarani C
Some interesting projects that might be integrated:
34 107 Selvarani C
35 107 Selvarani C
* https://github.com/Oslandia/albion : Build 3D geological model from wells information
36 107 Selvarani C
37 49 Philippe May
h2. Other
38 1 Philippe May
39 155 Selvarani C
40 49 Philippe May
41 108 Selvarani C
h1. GDAL (OGR) tools
42 108 Selvarani C
43 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:
44 108 Selvarani C
45 108 Selvarani C
* @ogr2ogr@ can easily convert one data format to another
46 108 Selvarani C
* @ogrinfo@ displays information about files.
47 108 Selvarani C
48 108 Selvarani C
h2. Using Windows
49 108 Selvarani C
50 108 Selvarani C
On a computer with Windows and GQIS installed:
51 108 Selvarani C
52 108 Selvarani C
1. Open a command line console (eg. <Windows Key> to display the Start menu, then just type @cmd@ and <Enter>)
53 108 Selvarani C
2. In the console window, type (adjust with the QGIS version and location, this seems to be the standard one):
54 108 Selvarani C
55 108 Selvarani C
<pre>
56 108 Selvarani C
"c:\Program Files\QGis 3.10\OSGeo4W.bat"
57 108 Selvarani C
</pre>
58 108 Selvarani C
59 108 Selvarani C
3. GDAL utilities can be used: @ogr2ogr@, etc.
60 108 Selvarani C
61 108 Selvarani C
h2. Example: convert Geopackage to Shapefiles
62 108 Selvarani C
63 108 Selvarani C
Output the content of the geopackage @9wdoogfr_2019-11-13_12_26_07.gpkg@ to the folder @shapefiles@:
64 108 Selvarani C
65 108 Selvarani C
<pre>
66 108 Selvarani C
ogr2ogr -progress -f "ESRI Shapefile" shapefiles 9wdoogfr_2019-11-13_12_26_07.gpkg
67 108 Selvarani C
</pre>
68 108 Selvarani C
69 108 Selvarani C
To output the content of the geopackage @9wdoogfr_2019-11-13_12_26_07.gpkg@ to the @root@ folder:
70 108 Selvarani C
71 108 Selvarani C
<pre>
72 108 Selvarani C
ogr2ogr -progress -f "ESRI Shapefile" c:\shapefiles 9wdoogfr_2019-11-13_12_26_07.gpkg
73 108 Selvarani C
</pre>
74 108 Selvarani C
75 108 Selvarani C
h2. With reprojection
76 108 Selvarani C
77 108 Selvarani C
Same as above, reprojecting to UTM44N: 
78 108 Selvarani C
79 108 Selvarani C
<pre>
80 108 Selvarani C
ogr2ogr -progress -f "ESRI Shapefile" -t_srs EPSG:32644 c:\shapefiles 9wdoogfr_2019-11-13_12_26_07.gpkg
81 108 Selvarani C
</pre>
82 108 Selvarani C
83 8 Philippe May
h2. Links and references
84 8 Philippe May
85 156 Selvarani C
86 16 Philippe May
87 109 Selvarani C
h1. Links
88 109 Selvarani C
89 109 Selvarani C
h2. Water management
90 109 Selvarani C
91 109 Selvarani C
h3. Modflow
92 109 Selvarani C
93 109 Selvarani C
* https://water.usgs.gov/ogw/modflow/
94 109 Selvarani C
95 109 Selvarani C
The reference software for underground water modelling and simulation.
96 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.
97 109 Selvarani C
98 109 Selvarani C
99 109 Selvarani C
h3. Freewat
100 109 Selvarani C
101 109 Selvarani C
* http://www.freewat.eu/project
102 109 Selvarani C
103 109 Selvarani C
This project is partly based on modflow, and integrates with QGis.
104 109 Selvarani C
105 109 Selvarani C
h2. QGIS
106 109 Selvarani C
107 109 Selvarani C
* https://www.qgis.org/en/site/
108 109 Selvarani C
109 109 Selvarani C
* Tools for Geology
110 109 Selvarani C
Construction of geological cross sections in QGIS - http://www.geokincern.com/?p=1452
111 109 Selvarani C
112 109 Selvarani C
113 109 Selvarani C
h2. Autocad
114 109 Selvarani C
115 109 Selvarani C
* Overview of Converting Geospatial Data to Drawing Objects: 
116 109 Selvarani C
http://docs.autodesk.com/CIV3D/2013/ENU/index.html?url=filesMAPC3D/GUID-C38FD485-3CC2-4B52-8264-0D8C0F45422B.htm,topicNumber=MAPC3Dd30e41809
117 109 Selvarani C
118 109 Selvarani C
* CAD-DB connection:
119 109 Selvarani C
https://knowledge.autodesk.com/support/autocad-civil-3d/learn-explore/caas/video/youtube/watch-v-AQoB--nyUJA.html
120 109 Selvarani C
121 211 Selvarani C
h1. Orfeo
122 109 Selvarani C
123 109 Selvarani C
* https://www.orfeo-toolbox.org/
124 109 Selvarani C
125 109 Selvarani C
Remote sensing
126 16 Philippe May
127 16 Philippe May
h2. Old docs
128 16 Philippe May
129 157 Selvarani C
[[Shapefiles]] - *%{color:RED} to be written%*
130 158 Selvarani C
131 110 Selvarani C
h1. Data (measurements auxiliary tables)
132 110 Selvarani C
133 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).
134 110 Selvarani C
135 110 Selvarani C
h2. Command line
136 110 Selvarani C
137 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.
138 110 Selvarani C
139 110 Selvarani C
@import_to_db.py@ is a support tool, that is planned to be integrated with the web interface.
140 110 Selvarani C
141 110 Selvarani C
Import all with:
142 110 Selvarani C
143 110 Selvarani C
<pre>
144 110 Selvarani C
phil@phil-mbp:~/BlueLight/gisaf_src/gisaf$ python import_to_db.py
145 110 Selvarani C
</pre>
146 110 Selvarani C
147 110 Selvarani C
The script currently accepts an argument for filtering the URLs to import.
148 110 Selvarani C
149 212 Selvarani C
h1. Pavneet's docs (imported from gisaf's wiki)
150 111 Selvarani C
151 111 Selvarani C
h1. Basic Rules of Map making
152 111 Selvarani C
153 111 Selvarani C
Regardless of the cartographic style or content, most maps have the following common elements.
154 111 Selvarani C
155 111 Selvarani C
156 111 Selvarani C
h2. TITLE
157 111 Selvarani C
158 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.
159 111 Selvarani C
160 111 Selvarani C
 
161 111 Selvarani C
162 111 Selvarani C
h2. SCALE INDICATOR
163 111 Selvarani C
164 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.
165 111 Selvarani C
166 111 Selvarani C
 
167 111 Selvarani C
168 111 Selvarani C
h2. ORIENTATION
169 111 Selvarani C
170 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.
171 111 Selvarani C
172 111 Selvarani C
h2. BORDER(s)
173 111 Selvarani C
174 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).
175 111 Selvarani C
176 111 Selvarani C
There can also be a border around the entire map layout (enclosing and grouping the title, legend, text boxes, etc.). 
177 111 Selvarani C
178 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.
179 111 Selvarani C
180 111 Selvarani C
h2. LEGEND
181 111 Selvarani C
182 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.
183 111 Selvarani C
184 111 Selvarani C
h2. MAP CREDITS
185 111 Selvarani C
186 111 Selvarani C
* SOURCE OF DATA (especially on thematic maps)
187 111 Selvarani C
* NAME of the cartographer  
188 111 Selvarani C
* DATE of the map creation/publication 
189 111 Selvarani C
* DATE of the map data 
190 111 Selvarani C
* PROJECTION of the map (especially small-scale maps)
191 111 Selvarani C
192 111 Selvarani C
h2. LOCATOR MAP (INSET)
193 111 Selvarani C
194 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).
195 111 Selvarani C
196 111 Selvarani C
h2. EFFECTIVE GRAPHICAL DESIGN
197 111 Selvarani C
198 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:
199 111 Selvarani C
200 111 Selvarani C
* Neatly drawn
201 111 Selvarani C
* Appropriately and consistently generalized
202 111 Selvarani C
* Symmetrically balanced (avoid crowding or large blank areas)
203 111 Selvarani C
* Without unnecessary clutter (keep it simple, be wary of 'artistic' details)
204 111 Selvarani C
205 111 Selvarani C
h2. VISUAL HIERARCHY
206 111 Selvarani C
207 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.
208 111 Selvarani C
209 111 Selvarani C
h2. PURPOSE
210 111 Selvarani C
211 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.
212 1 Philippe May
213 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).
214 111 Selvarani C
215 111 Selvarani C
*In general, with cartography, less is more (avoid excessive clutter).*
216 1 Philippe May
217 161 Selvarani C
h1. GIS - Survey_Database
218 112 Selvarani C
219 112 Selvarani C
DB- Database
220 112 Selvarani C
C3D- Civil 3D
221 112 Selvarani C
222 215 Selvarani C
h1. How to create Survey database in Civil 3D
223 112 Selvarani C
224 215 Selvarani C
h2. 1. Setting up the Working Folder
225 112 Selvarani C
226 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:
227 112 Selvarani C
228 117 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9783/working%20folder%20image.jpg!
229 116 Selvarani C
230 215 Selvarani C
h2. 2. Creating a database
231 112 Selvarani C
232 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.
233 112 Selvarani C
234 215 Selvarani C
h2. 3. Setting up the database
235 112 Selvarani C
236 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.
237 112 Selvarani C
238 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
239 112 Selvarani C
240 112 Selvarani C
h2. Components of Survey Database
241 112 Selvarani C
242 112 Selvarani C
Survey database in civil 3D has the following components when expanded. 
243 112 Selvarani C
# Import Events
244 112 Selvarani C
# Survey Queries
245 112 Selvarani C
# Networks
246 112 Selvarani C
# Network Groups
247 112 Selvarani C
# Figures
248 112 Selvarani C
# Figure Groups
249 112 Selvarani C
# Survey Points
250 112 Selvarani C
# Survey point Groups
251 112 Selvarani C
252 118 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9782/Survey_db.png!
253 163 Selvarani C
254 113 Selvarani C
255 113 Selvarani C
h1. Survey- Field to Finish
256 113 Selvarani C
257 113 Selvarani C
h2. Steps from field work 
258 113 Selvarani C
259 113 Selvarani C
# ?? To be added by Raj and Ram
260 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")
261 113 Selvarani C
# Cleaning up the .txt files/removing errors (If any)
262 113 Selvarani C
263 113 Selvarani C
h2. Feeding the survey data into Civil 3D- by Surveyor
264 113 Selvarani C
265 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
266 113 Selvarani C
# Open up project in Civil 3D
267 113 Selvarani C
# Importing of Events (explain the step)
268 113 Selvarani C
269 113 Selvarani C
h2. Processing- by Surveyor
270 113 Selvarani C
271 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.
272 113 Selvarani C
273 113 Selvarani C
h2. Post-Processing
274 113 Selvarani C
275 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.
276 113 Selvarani C
277 113 Selvarani C
h2. Creating shapefiles in AutoCAD
278 113 Selvarani C
279 217 Selvarani C
?? add by pavneet - *%{color:RED} to be written%*
280 113 Selvarani C
281 113 Selvarani C
h2. Sharing on WebGIS - "GISAF-  +gis.auroville.org.in+" 
282 113 Selvarani C
283 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.
284 113 Selvarani C
285 113 Selvarani C
286 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.
287 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)
288 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.
289 113 Selvarani C
# *Import to GISAF (Only with Authorization)* - Click on the import arrow.
290 113 Selvarani C
291 113 Selvarani C
h2. Adding new codes
292 113 Selvarani C
293 220 Selvarani C
ADD !! - *%{color:RED} to be written%*
294 113 Selvarani C
295 113 Selvarani C
h2. Reconciliation of points
296 113 Selvarani C
297 220 Selvarani C
The points are noted with their codes from and codes to reconcile into. ADD!! - *%{color:RED} to be written%*
298 119 Selvarani C
299 119 Selvarani C
h1. Survey Data Post-Processing
300 119 Selvarani C
301 119 Selvarani C
+Softwares used: Civil 3D, QGIS+
302 119 Selvarani C
303 119 Selvarani C
AutoCAD Civil 3D - C3D, 
304 119 Selvarani C
305 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.
306 119 Selvarani C
307 119 Selvarani C
QGIS is an Open source GIS.
308 119 Selvarani C
309 119 Selvarani C
Getting Started:
310 119 Selvarani C
+Standards and Workflow for C3D+
311 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.
312 119 Selvarani C
313 119 Selvarani C
+Geometry types-+
314 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).
315 119 Selvarani C
316 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.
317 119 Selvarani C
318 119 Selvarani C
+Using Feature lines for creating Curved geometries in 3D-+
319 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 :-
320 119 Selvarani C
321 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.
322 119 Selvarani C
323 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.
324 119 Selvarani C
325 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.
326 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.
327 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.
328 119 Selvarani C
Situations of sharing of points with different layers and proceeding with linework in such circumstances-
329 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. 
330 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).
331 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. 
332 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. 
333 119 Selvarani C
334 119 Selvarani C
*+Purpose of Survey+*
335 119 Selvarani C
336 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.
337 119 Selvarani C
338 119 Selvarani C
339 119 Selvarani C
+Use of Layers+
340 119 Selvarani C
341 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.
342 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.
343 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.
344 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.
345 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.
346 119 Selvarani C
# Use of *V-ROAD-CYCP* is for designated cycle path as a single line.
347 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.
348 119 Selvarani C
# *V-WMNG-PIPP* for pipe points, *V-WMNG-PIPL*- for pipe lines.
349 119 Selvarani C
# *V-BLDG-BMRK* is for unidentified bench marks and *V-BLDG-MHOL* is for unidentified manholes.
350 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.
351 119 Selvarani C
# *V-WMNG-POOL* is for water bodies made for leisure activities- like swimming pool etc.
352 119 Selvarani C
# *V-WMNG-SUMP* is collectively for artificial water retention structures.
353 119 Selvarani C
# *V-WATR-POND* is for top of natural water retention.
354 119 Selvarani C
# *V-WATR-PONB* is for bottom of natural water retention.
355 119 Selvarani C
# *V-WMNG-DRBA* is for bottom of artificial drains.
356 119 Selvarani C
# *V-WMNG-DRTA* is for top of artificial drains.
357 119 Selvarani C
# *V-WATR-DRBN* is for bottom of Natural drains.
358 119 Selvarani C
# *V-WATR-DRTN* is for top of Natural drains.
359 119 Selvarani C
# *V-WMNG-DRNC* is for drain covers.
360 1 Philippe May
# *V-WATR-DRAS* is for indicating slope of drainage, these are arrows.
361 119 Selvarani C
362 120 Selvarani C
h1. Wells Documentation
363 120 Selvarani C
364 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.
365 120 Selvarani C
366 120 Selvarani C
*Terms of reference*
367 120 Selvarani C
368 120 Selvarani C
+Well status+ 
369 120 Selvarani C
	
370 120 Selvarani C
# *In use*      Well is equipped with functioning a pump	
371 120 Selvarani C
# *Not in use*  Well is not equipped with a functioning pump. (Special case- well is equipped with a non functioning pump)
372 120 Selvarani C
# *Closed*      Well is closed/ sealed/ abandoned, (Historical reference)
373 120 Selvarani C
374 1 Philippe May
Note: Wells with pump under repair (temporary measure) at the time of survey are treated as *In use*.
375 120 Selvarani C
376 167 Selvarani C
377 121 Selvarani C
378 121 Selvarani C
h1. Civil 3D useful commands
379 121 Selvarani C
380 121 Selvarani C
381 121 Selvarani C
h2. Making Feature line to polyline-
382 121 Selvarani C
383 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)
384 121 Selvarani C
385 121 Selvarani C
h2. Converting Circle to polyline-
386 121 Selvarani C
387 121 Selvarani C
BR > enter > break the circle at two points to obtain a part of circle. 
388 121 Selvarani C
PEDIT> enter> select the part of leftover circle> J > enter> Close> enter.
389 121 Selvarani C
390 121 Selvarani C
h2. Converting 2DPOLYLINE to POLYLINE
391 121 Selvarani C
392 121 Selvarani C
Explode the 2D polyline, and use the PEDIT command to convert the segments to polylines. Then join the polylines.
393 121 Selvarani C
394 121 Selvarani C
h2. Viewing only the used layer in ACAD-
395 121 Selvarani C
396 121 Selvarani C
Set the value of SHOWLAYERUSAGE from 0 to 1
397 121 Selvarani C
398 121 Selvarani C
h2. Convert 3d polyline to polyline- 
399 121 Selvarani C
400 121 Selvarani C
COVERT3DPOLYS (Change the elevation of the polyline using properties manager to 0 in our case)
401 121 Selvarani C
402 121 Selvarani C
h2. Generating contours from a Surface in Civil 3D
403 121 Selvarani C
404 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.
405 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.
406 121 Selvarani C
# Go to the surface created in prospector and right click > Edit surface style> Turn on the Major and Minor contour.
407 121 Selvarani C
# Turn on the layers for Major and Minor contours in Layers Manager (LA > enter)
408 121 Selvarani C
409 121 Selvarani C
h2. Shortcuts:
410 121 Selvarani C
411 121 Selvarani C
• Properties manager - ctrl + 1
412 121 Selvarani C
• To view 3D- Select and right click> object Viewer.
413 121 Selvarani C
• To copy the Line - Copy and select the line enter 
414 121 Selvarani C
• To convert spline to polyline >Splinedit
415 121 Selvarani C
• To export shapefile - Mapexport > follow the process.
416 121 Selvarani C
• To assign coordinate system to the drawing - MAPCSLIBRARY
417 121 Selvarani C
• To check coordinate system of the drawing- > TOOLSPACE> Settings> Right click on the drawing name > Edit settings
418 121 Selvarani C
419 122 Selvarani C
h1. Online references for Civil 3D
420 122 Selvarani C
421 123 Selvarani C
*Description Key Sets*
422 122 Selvarani C
423 122 Selvarani C
https://www.youtube.com/watch?v=Von8oCwYcTk
424 122 Selvarani C
425 124 Selvarani C
*Autodesk civil 3D Geotechnical module- for borehole data*
426 122 Selvarani C
427 122 Selvarani C
https://www.youtube.com/watch?v=0Be9kShBou0
428 122 Selvarani C
429 123 Selvarani C
*Civil 3D for Surveyors*
430 122 Selvarani C
431 122 Selvarani C
https://www.youtube.com/playlist?list=PL1EzH8XlwSxuxCMdeLvzqfgsAlmeeHMv2
432 122 Selvarani C
433 123 Selvarani C
*Civil 3D: Survey - Survey Database*
434 1 Philippe May
435 122 Selvarani C
https://www.youtube.com/watch?v=VPWdAfYJt5Y 
436 123 Selvarani C
437 169 Selvarani C
438 125 Selvarani C
439 125 Selvarani C
h1. Connections in QGIS- Using browser panel and Add postGIS
440 125 Selvarani C
441 125 Selvarani C
Working using QGIS as interface using PostGIS connections.
442 125 Selvarani C
443 125 Selvarani C
* Server: @gisdb.csr.av@
444 125 Selvarani C
445 125 Selvarani C
* Database: @avgis@
446 125 Selvarani C
447 125 Selvarani C
* Leave @Service@ empty
448 125 Selvarani C
449 125 Selvarani C
450 125 Selvarani C
h2. Adding tables (With geometries) in form of shape files from database using Browser panel-
451 125 Selvarani C
452 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.
453 125 Selvarani C
454 125 Selvarani C
455 125 Selvarani C
h2. Adding tables (For non-geometry type) using PostGIS connections-
456 125 Selvarani C
457 125 Selvarani C
Add PostGIS Layers > Give credentials > select "Also list tables with no geometry" > expand public > click on the desired table> add.
458 125 Selvarani C
459 125 Selvarani C
h2. Joining tables
460 125 Selvarani C
461 125 Selvarani C
Right click/double click on file> go to Join > perform the desired joins - add/subtract the joins. 
462 125 Selvarani C
463 125 Selvarani C
464 170 Selvarani C
h1. *Reconcilation of Raw survey data using pgAdmin*
465 126 Selvarani C
466 126 Selvarani C
+For changing the layer codes, to be done using Pgadmin.+
467 126 Selvarani C
468 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.
469 126 Selvarani C
470 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).
471 126 Selvarani C
472 126 Selvarani C
h3.  Other > Project > select the project > with selected> reconcile RAW survey points.
473 126 Selvarani C
474 127 Selvarani C
h1. Importing point data (TS and RTK) to GISAF 
475 127 Selvarani C
476 127 Selvarani C
# *Gisaf Admin > Basket > Survey data > "Project" > "surveyor" > TS/ RTK > upload > import.*
477 127 Selvarani C
# *Auto import of Raw points data* (changes from Raw to Shapefiles, the point files)
478 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...
479 127 Selvarani C
480 172 Selvarani C
481 128 Selvarani C
482 128 Selvarani C
h1. Editing Z value of features in Shapefiles in QGIS
483 128 Selvarani C
484 128 Selvarani C
h2. using vertex editor tool - https://www.youtube.com/watch?v=8V8i1AtcA74&t=256s
485 128 Selvarani C
486 129 Selvarani C
h1. Miscellaneous- Civil 3D
487 129 Selvarani C
488 129 Selvarani C
*Autodesk civil 3D Geotechnical module- for borehole data :- To analyse borehole data, To make profiles and calculate volumes*
489 129 Selvarani C
490 129 Selvarani C
https://www.youtube.com/watch?v=0Be9kShBou0
491 129 Selvarani C
Reference videos
492 129 Selvarani C
Exploring:
493 129 Selvarani C
https://www.youtube.com/watch?v=gr-ISPzLcU0
494 129 Selvarani C
Modelling:
495 129 Selvarani C
https://www.youtube.com/watch?v=Pz0-HOoiBrs
496 129 Selvarani C
solids
497 129 Selvarani C
https://www.youtube.com/watch?v=mQ0Yeh6tZA8
498 129 Selvarani C
https://www.youtube.com/watch?v=4eMsUiYBhuE
499 129 Selvarani C
500 129 Selvarani C
501 129 Selvarani C
*CIVIL 3D Survey*
502 129 Selvarani C
Getting started- Always open a new drawing with a template. 
503 129 Selvarani C
504 129 Selvarani C
*Description key sets*- (till 18:30) https://www.youtube.com/watch?v=mmwkkRyBkS0
505 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.
506 129 Selvarani C
Tool space > settings > points > description key sets
507 129 Selvarani C
“Description key sets name”> edit key- to view the points in a list: 
508 129 Selvarani C
Automatic linework (18:30- till end)
509 129 Selvarani C
Survey > Linework code sets- for automatic linework
510 129 Selvarani C
511 129 Selvarani C
*Using Master view*
512 129 Selvarani C
Uses-
513 129 Selvarani C
copy styles from one drawing to other
514 129 Selvarani C
copy drawing data from one drawing to other (data referencing)
515 129 Selvarani C
516 129 Selvarani C
*Civil 3d surface model*- from points- break lines
517 129 Selvarani C
https://www.youtube.com/watch?v=wC40rdmDEMo
518 129 Selvarani C
moving for example- point groups under point groups- 
519 129 Selvarani C
520 129 Selvarani C
*Civil 3D Planning and Analysis*
521 129 Selvarani C
Workspace: Planning and Analysis
522 129 Selvarani C
1. Working with Object data (GIS Attributes)
523 129 Selvarani C
Map Setup> Define object data> New table> Define new object data table start defining fields
524 129 Selvarani C
525 129 Selvarani C
526 130 Selvarani C
527 130 Selvarani C
h1. Documentation- Rain Gauge
528 130 Selvarani C
529 130 Selvarani C
h2. Manual Rain Gauge
530 130 Selvarani C
531 130 Selvarani C
*Why it is important to comply to standards?*
532 130 Selvarani C
533 130 Selvarani C
1. Consistency for comparing rainfall data in different places within Auroville since rainfall varies in different parts of Auroville.
534 130 Selvarani C
535 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. 
536 130 Selvarani C
537 130 Selvarani C
*Proposed standards and ethics:*
538 130 Selvarani C
539 130 Selvarani C
1. The time of taking the reading - 08:30 am. 
540 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.
541 130 Selvarani C
542 130 Selvarani C
2. Manual rain gauge typically used- green cylindrical and a collection jar.  
543 130 Selvarani C
  
544 130 Selvarani C
3. Measuring jar: 10 mm corresponding jar
545 130 Selvarani C
546 130 Selvarani C
 
547 130 Selvarani C
Area of the rim of manual rain gauge= 200 square cm
548 130 Selvarani C
Diameter of rim= approximately 16 cm
549 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.
550 130 Selvarani C
551 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.
552 130 Selvarani C
553 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.
554 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.
555 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. 
556 130 Selvarani C
557 130 Selvarani C
8. In case of doubt in reading or incorrect measure, "incorrect measure" should be marked
558 130 Selvarani C
559 130 Selvarani C
560 130 Selvarani C
*Ethics*
561 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). 
562 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. 
563 130 Selvarani C
564 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. 
565 130 Selvarani C
566 130 Selvarani C
*Important-*
567 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.
568 130 Selvarani C
CSR Geomatics Team is placed on first floor in CSR, Auroshilpam.
569 130 Selvarani C
570 130 Selvarani C
*AV rain data publication*: (http://gis.auroville.org.in/measures/raingauge_av).
571 130 Selvarani C
572 130 Selvarani C
Adding Rain gauge to our web portal (GISAF), following information is needed:
573 130 Selvarani C
1. GPS co-ordinates of location of placing the rain gauge (can be obtained using mobile phones easily)
574 130 Selvarani C
2. Name, place of residence & contact number- Mobile & Landline
575 130 Selvarani C
576 130 Selvarani C
h2. Automatic Rain Gauge
577 130 Selvarani C
578 130 Selvarani C
There is a possibility of publishing rain data coming from Automatic rain gauges like (id 15, auro orchard) and Weather stations. 
579 130 Selvarani C
For Automatic rain gauges, we can upload the files coming from the rain gauge directly into GISAF.
580 130 Selvarani C
581 130 Selvarani C
582 130 Selvarani C
_Thank you for contribution towards a sustainable management of Water in Auroville through Data collection._
583 130 Selvarani C
584 130 Selvarani C
585 131 Selvarani C
586 131 Selvarani C
h1. Documentation- Wells Monitoring (Manual and Automatic / Piezometer by Bala)
587 131 Selvarani C
588 131 Selvarani C
h2. Manual- Using tape with a sensor
589 131 Selvarani C
590 131 Selvarani C
Timings: The person assigned the job of monitoring collects the readings in three slots.
591 131 Selvarani C
592 131 Selvarani C
1.	Between 6 am to 7 am till about 9 am to 10 am.
593 131 Selvarani C
2.	Between 11 am and 1 pm
594 131 Selvarani C
3.	Between 2 pm and 5 pm
595 131 Selvarani C
596 131 Selvarani C
Things required:
597 131 Selvarani C
•	Notebook
598 131 Selvarani C
•	Pen
599 131 Selvarani C
•	Measuring tape
600 131 Selvarani C
•	Vehicle for movement
601 131 Selvarani C
602 131 Selvarani C
603 131 Selvarani C
*Ethics*- 
604 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.
605 131 Selvarani C
•	The monitor should have contact numbers of the person in charge/ care taker for any communication.
606 131 Selvarani C
•	If the monitoring is stopped for any reason at any point, the monitor should communicate the same to the person concerned.
607 131 Selvarani C
•	The monitor shall take responsibility to inform any kind of changes in a well in terms of its functioning etc.
608 131 Selvarani C
•	The monitor should report to the CSR Geomatics Team who has responsibility to publish data.
609 131 Selvarani C
•	The monitor published the data to the website and works with the geomatics team.
610 131 Selvarani C
611 131 Selvarani C
612 131 Selvarani C
*Definitions*:
613 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. 
614 131 Selvarani C
615 131 Selvarani C
*Well type*
616 131 Selvarani C
1.	Open
617 131 Selvarani C
2.	Borewell
618 131 Selvarani C
3.	Dug cum borewell
619 131 Selvarani C
620 131 Selvarani C
*Well status*
621 131 Selvarani C
1.	In use
622 131 Selvarani C
2.	Not in use
623 131 Selvarani C
3.	Closed
624 131 Selvarani C
625 131 Selvarani C
*Pump Status*
626 131 Selvarani C
1.	Functioning
627 131 Selvarani C
2.	Not functioning
628 131 Selvarani C
629 131 Selvarani C
*Pump Automation*
630 131 Selvarani C
1.	Manual 
631 131 Selvarani C
2.	Automatic
632 131 Selvarani C
633 131 Selvarani C
* Non-accessibility factors*
634 131 Selvarani C
1.	Dogs
635 131 Selvarani C
2.	Heavy slab
636 131 Selvarani C
3.	Narrow casing
637 131 Selvarani C
4.	enclosed/locked
638 131 Selvarani C
5.	permission
639 131 Selvarani C
640 131 Selvarani C
*Data Matching Accuracy (reconnecting with harvest wells data)*
641 131 Selvarani C
1.	High
642 131 Selvarani C
2.	Medium
643 131 Selvarani C
3.	Low
644 131 Selvarani C
645 131 Selvarani C
*Well coordinates*
646 131 Selvarani C
For a new well, coordinates of the well position are taken on a mobile GPS.
647 131 Selvarani C
Person In charge
648 131 Selvarani C
For communication purpose, contact the person in charge as recorded in directory.
649 131 Selvarani C
650 131 Selvarani C
h2. Automatic- Piezometer (by bala, to be edited) 
651 131 Selvarani C
652 131 Selvarani C
The calibrations and setting are already done by Azha
653 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
654 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
655 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.
656 131 Selvarani C
The piezometer sometimes does not have proper signal and so it would not be able to send it
657 131 Selvarani C
658 132 Selvarani C
h1. Documentation- Flow meter by Bala
659 132 Selvarani C
660 132 Selvarani C
Flow meter – for checking the flow of water in pipe
661 132 Selvarani C
662 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.
663 132 Selvarani C
we tested in the west water system pump in csr. then we test in many more place .
664 132 Selvarani C
 ami, aurodam and buddha garden borewell pumps . we got request from the water service 
665 132 Selvarani C
Cross check they flow meters .
666 132 Selvarani C
 so before that  we want to know how our meter works. 
667 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. 
668 132 Selvarani C
we tested two times in  15 minutes.and one time 30 minutes,so we got variation between this three. 
669 132 Selvarani C
we find 1,5 % error but the flow meret they said  1 % error only.
670 132 Selvarani C
we cross checked the flow meter of the water service we find some error  in they meter also. 
671 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.  
672 132 Selvarani C
then we find some error in (AVWS) meter also.
673 132 Selvarani C
It is used to check the flow of water in pipe
674 132 Selvarani C
tools used 
675 132 Selvarani C
First the outer diameter of the pipe has to be entered in the device. It is measured using Vernier caliper
676 132 Selvarani C
Then the thickness of the pipe is set which is also measured using vernier
677 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) 
678 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
679 132 Selvarani C
When the sensors are fixed the motor is turned on and the sensors send reading to the display device
680 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.
681 1 Philippe May
This was done in different places to check to flow rate
682 132 Selvarani C
683 177 Selvarani C
684 133 Selvarani C
685 133 Selvarani C
h1. Documentation- DST- Vegetation Indexing
686 133 Selvarani C
687 133 Selvarani C
h2. Steps for Dzetsaka Classification tool for Vegetation indexing in QGIS
688 133 Selvarani C
689 133 Selvarani C
 
690 133 Selvarani C
 1. Install the plugin Dzetsaka classfication tool.
691 133 Selvarani C
 2. Open the Raster from the Survey.
692 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. 
693 133 Selvarani C
     More the samples, better the indexing.
694 133 Selvarani C
 4. Apply Dzetsaka Classification tool, Select the base raster and the sample- index polygon shapefile created in step 3.
695 133 Selvarani C
 5. The result is a Raster with DN numbers specified in the Shapefile in step 3.
696 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.
697 133 Selvarani C
 7. Polygonise the Raster to Vector (From processing)
698 133 Selvarani C
 8. Run the v.generalise tool on the shapefile. This tool removes the pixelated boundaries of the polygons in the Vector.
699 133 Selvarani C
700 134 Selvarani C
h1. Documentation- DST- Interpolation (Processing toolbox)
701 134 Selvarani C
702 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)* )
703 134 Selvarani C
704 134 Selvarani C
# Interpolate (Cubic spline) - SAGA
705 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.
706 134 Selvarani C
# V.surf.rst - GRASS
707 134 Selvarani C
# Krigging - SAGA
708 1 Philippe May
709 181 Selvarani C
[[Documentation- DST- Survey- Office workflow]]  - *%{color:RED} to be written%*
710 135 Selvarani C
711 135 Selvarani C
h1. From CAD to GIS by Giulio
712 135 Selvarani C
713 135 Selvarani C
*FEATURES CREATION*
714 135 Selvarani C
1.	Assign a CRS to the drawing (TM-AUSPOS) (MAPCSLIBRARY command)
715 135 Selvarani C
2.	Create features in CAD (Points, lines, polygons)
716 135 Selvarani C
3.	Export shapefile (a) from CAD (Output > DWG to SDF) (Convert to LL84 – 3D)
717 135 Selvarani C
718 135 Selvarani C
*FEATURES IMPORT INTO DB FIRST TIME*
719 135 Selvarani C
4.	Create zip file of the shapefile
720 135 Selvarani C
5.	Upload into the GISAF Shapefiles Basket
721 135 Selvarani C
6.	Import the shapefile into DB
722 135 Selvarani C
7.	Save the shapefile on Local Machine
723 135 Selvarani C
724 135 Selvarani C
*FEATURES IMPORT INTO DB EVERYTIME*
725 135 Selvarani C
8.	Combine the new features to corresponding last shape files (Insert the process here).
726 135 Selvarani C
9.	Follow step 4-8 again
727 135 Selvarani C
728 135 Selvarani C
*FEATURES EDITING IN QGIS*
729 135 Selvarani C
10.	Open the table in QGis
730 135 Selvarani C
11.	Save as a shapefile (b) in TM AUSPOS CRS
731 135 Selvarani C
12.	In CAD, open a new drawing and assign AUSPOS CRS
732 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
733 135 Selvarani C
14.	Edit features
734 135 Selvarani C
15.	Change workspace into “Planning and analysis”
735 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)
736 135 Selvarani C
737 135 Selvarani C
*FEATURES IMPORT INTO DB*
738 135 Selvarani C
17.	Create zip file of the shapefile
739 135 Selvarani C
18.	Upload into the GISAF Shapefiles Basket
740 135 Selvarani C
19.	Import the shapefile into DB
741 135 Selvarani C
20.	Delete the shapefile from Local Machine
742 135 Selvarani C
743 135 Selvarani C
744 182 Selvarani C
745 1 Philippe May
746 136 Selvarani C
h1. QGIS- Miscellaneous
747 136 Selvarani C
748 136 Selvarani C
*QGIS Introduction:*
749 136 Selvarani C
https://www.birdseyeviewgis.com/blog/2018/2/22/my-favorite-features-of-qgis-30to-date
750 136 Selvarani C
3D visualization of raster DEM- https://www.youtube.com/watch?v=2KrCsbP0kUs
751 136 Selvarani C
752 136 Selvarani C
*Spatial query:* 
753 136 Selvarani C
Spatial Query is selection of features that satisfies a certain condition which relates to other features in a space.
754 136 Selvarani C
Using plugin- Spatial query
755 136 Selvarani C
http://www.geodose.com/2018/03/spatial-query-in-qgis-3.html
756 136 Selvarani C
Labelling:
757 136 Selvarani C
Labelling with more than one field names and in different lines
758 136 Selvarani C
|| '\n' ||
759 136 Selvarani C
760 136 Selvarani C
761 136 Selvarani C
762 136 Selvarani C
*Hierarchy of extensions*
763 136 Selvarani C
764 136 Selvarani C
File levels and their uses.
765 136 Selvarani C
https://nathanw.net/2014/03/22/all-the-q-files/
766 136 Selvarani C
767 136 Selvarani C
+The Project file (.qgs)+
768 136 Selvarani C
It contains: Layer source pointer + Style information + Composers + a whole heap of other stuff
769 136 Selvarani C
770 136 Selvarani C
+The Layer Definition file (.qlr)+
771 136 Selvarani C
It contains: Layer source pointer + Style information
772 136 Selvarani C
773 136 Selvarani C
+The QML file (.qml)+
774 136 Selvarani C
It contains: Style information
775 136 Selvarani C
776 59 Giulio Di Anastasio
h2. Giulio's documentation
777 52 Giulio Di Anastasio
778 183 Selvarani C
779 137 Selvarani C
780 137 Selvarani C
h1. Documentation - Reconciliation of points using Gisaf
781 137 Selvarani C
782 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.
783 137 Selvarani C
784 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).
785 137 Selvarani C
786 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]].
787 137 Selvarani C
788 137 Selvarani C
789 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.
790 137 Selvarani C
791 137 Selvarani C
792 137 Selvarani C
PLEASE NOTE: 
793 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+*.
794 137 Selvarani C
795 137 Selvarani C
h2. How to perform Reconciliation
796 137 Selvarani C
797 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
798 137 Selvarani C
799 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).
800 137 Selvarani C
801 137 Selvarani C
Under it, in the field "Original ID", the original point number of the point to be reconciled is to be entered.
802 137 Selvarani C
803 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.
804 137 Selvarani C
805 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.
806 137 Selvarani C
807 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.
808 137 Selvarani C
809 138 Selvarani C
h1. Documentation - Status and Status Changes
810 138 Selvarani C
811 138 Selvarani C
Status have been created to keep track og changes in surveyed features.
812 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.
813 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.
814 138 Selvarani C
815 138 Selvarani C
Status have been defined as follows:
816 138 Selvarani C
N - New Work
817 138 Selvarani C
E - Existing o remain
818 138 Selvarani C
D - Existing to demolish, Demolished or Changed
819 138 Selvarani C
F- Future work, Proposed feature
820 138 Selvarani C
T - Temporary work
821 138 Selvarani C
M - Item to be moved
822 138 Selvarani C
X - Not in contract
823 138 Selvarani C
824 138 Selvarani C
825 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).
826 138 Selvarani C
It needs to be done manually, one feature (point, line, polygon) at a time.
827 138 Selvarani C
828 138 Selvarani C
829 1 Philippe May
In the future Status changes might be incorporated in the Admin panel.
830 138 Selvarani C
831 185 Selvarani C
832 67 Giulio Di Anastasio
833 139 Selvarani C
h1. Documentation - Tags retained after re-import of same geometry
834 139 Selvarani C
835 139 Selvarani C
Documentation - Tags retained after re-import of same geometry
836 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.
837 139 Selvarani C
The result was that lines did not inherit the attributes survey date, accuracy, equipment, surveyor.
838 139 Selvarani C
Nevertheless lines were displayed on the Gisaf map, without these attributes, and tags were given to some of these lines.
839 139 Selvarani C
840 139 Selvarani C
The values for the two tables ("Accuracy", "Accuracy") have been corrected, ambiguity resolved.
841 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.
842 139 Selvarani C
843 139 Selvarani C
4 August 2020
844 139 Selvarani C
845 67 Giulio Di Anastasio
h1. Access to data
846 67 Giulio Di Anastasio
847 67 Giulio Di Anastasio
h2. Connection to server directly from CSR
848 67 Giulio Di Anastasio
849 67 Giulio Di Anastasio
To connect to the server directly without going through Aurinoco server, the correct url is
850 67 Giulio Di Anastasio
http://gis.csr.av
851 67 Giulio Di Anastasio
852 67 Giulio Di Anastasio
h2. Connection to Gisaf via QGis through WFS / OGC API
853 67 Giulio Di Anastasio
854 67 Giulio Di Anastasio
This works only on QGis from version 3.14.15 onward
855 67 Giulio Di Anastasio
856 67 Giulio Di Anastasio
In the browser, click on WFS/OGC API, then right-click to create a new connection
857 67 Giulio Di Anastasio
Give a name (e.g. OGC API Qgis Gisaf)
858 67 Giulio Di Anastasio
Give the url https://gis.auroville.org.in/ogcapi
859 67 Giulio Di Anastasio
860 67 Giulio Di Anastasio
Under the WFS Options box, on Version dropdown, the default option "Maximum" works just fine
861 67 Giulio Di Anastasio
Click on OK
862 67 Giulio Di Anastasio
The list of layers will appear in the Browser under WFS/OGC API.
863 68 Giulio Di Anastasio
864 68 Giulio Di Anastasio
865 68 Giulio Di Anastasio
h1. How to create a new projection in QGis
866 68 Giulio Di Anastasio
867 68 Giulio Di Anastasio
To create a new projection in QGis, go to menu "Settings", and click on "Custom Projections".
868 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.
869 68 Giulio Di Anastasio
Click on the green "+" sign on the right top part of the window to create a new projection.
870 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).
871 68 Giulio Di Anastasio
In the "Format" dropdown list, select "Proj String (legacy - Not Recommended)"
872 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".
873 68 Giulio Di Anastasio
874 68 Giulio Di Anastasio
Finally, click on OK.
875 68 Giulio Di Anastasio
876 68 Giulio Di Anastasio
In a more explicit  way, the parameters mean the following:
877 68 Giulio Di Anastasio
Map Projection:        TransverseMercator (TM)
878 68 Giulio Di Anastasio
False Easting:          370455.6300
879 68 Giulio Di Anastasio
False Northing:        1328608.9940
880 68 Giulio Di Anastasio
Latitude of Origin:    12°00'57.79560" (DMS)   12.01605433 (DD)
881 68 Giulio Di Anastasio
Central Meridian:     79°48'35.96164"  (DMS)   79.80998934 (DD)
882 68 Giulio Di Anastasio
Scale Factor:             1.00000000
883 68 Giulio Di Anastasio
Zone Width:              6.0°
884 69 Giulio Di Anastasio
885 69 Giulio Di Anastasio
h1. Elimination of Duplicate points – General criteria
886 69 Giulio Di Anastasio
887 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.
888 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.
889 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.
890 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.
891 69 Giulio Di Anastasio
How to identify duplicate points?
892 69 Giulio Di Anastasio
The following criteria can be used:
893 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)
894 69 Giulio Di Anastasio
2.	The orig_id (serial number) of the points are not in series
895 69 Giulio Di Anastasio
3.	The survey date is not the same
896 69 Giulio Di Anastasio
4.	In case of trees, the species of trees is the same
897 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)
898 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.
899 70 Giulio Di Anastasio
900 70 Giulio Di Anastasio
901 70 Giulio Di Anastasio
h1. Linework for the Survey Area
902 70 Giulio Di Anastasio
903 70 Giulio Di Anastasio
h2. 1.	Creation of Initial Linework in QGIS using Survey points import - (Ram, System 4)
904 70 Giulio Di Anastasio
905 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.
906 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*.
907 70 Giulio Di Anastasio
The Initial Linework for the Survey Area is also stored temporarily in 
908 70 Giulio Di Anastasio
909 74 Selvarani C
+D: > AVSM > Zone-Survey number (eg RZ-01) > Survey Area (eg J) > Temporary WD+
910 70 Giulio Di Anastasio
911 70 Giulio Di Anastasio
h2. Note: The line shapefiles / Geopackages shall be in CRS: TM AUSPOS
912 70 Giulio Di Anastasio
913 70 Giulio Di Anastasio
h2. 2.	Creation of final working drawing Shapefiles / Geopackages - (Selvarani, System 1)
914 1 Philippe May
915 1 Philippe May
Final working drawing Shapefiles / Geopackages are created from the Initial Linework of Survey Area.
916 70 Giulio Di Anastasio
As the Surveyor draws all features as lines (both for lines and polygons features), the following actions shall be done:
917 74 Selvarani C
1.	*If features are lines:*
918 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).
919 70 Giulio Di Anastasio
920 70 Giulio Di Anastasio
h2. The CRS for the export shall be EPSG:4326 - WGS 84
921 70 Giulio Di Anastasio
922 74 Selvarani C
2.	*If features are polygons:*
923 1 Philippe May
•	Lines shall be converted into polygons:
924 74 Selvarani C
925 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:
926 87 Selvarani C
927 84 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9760/Line%20to%20Polygon%20Menu.png!
928 70 Giulio Di Anastasio
929 86 Selvarani C
930 1 Philippe May
The new window for “Lines to Polygons” conversion will appear:
931 86 Selvarani C
932 86 Selvarani C
933 83 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9762/Lines%20to%20Polygon%20Window.png!
934 1 Philippe May
935 71 Giulio Di Anastasio
•	Always cross check the input layer, to make sure that the input layer is the active one
936 71 Giulio Di Anastasio
•	Save the output in a temporary layer
937 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)
938 72 Giulio Di Anastasio
939 74 Selvarani C
h2. The CRS for the export shall be EPSG:4326 - WGS 84
940 74 Selvarani C
941 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.
942 1 Philippe May
943 74 Selvarani C
h2. Linework for the whole Survey Zone
944 74 Selvarani C
945 74 Selvarani C
h2. 1.	Merging Shapefiles / Geopackages - (Selvarani, System 1)
946 74 Selvarani C
947 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.
948 1 Philippe May
Master shapefiles / geopackages are merged with the Survey Area shapefiles / geopackages:
949 72 Giulio Di Anastasio
•	To do it, go to “Vector” Menu, click on Geoprocessing Tools, then click on Union:
950 72 Giulio Di Anastasio
951 85 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9763/Union%20Menu.png!
952 1 Philippe May
953 1 Philippe May
954 85 Selvarani C
The new window for “Union” will appear:
955 1 Philippe May
956 86 Selvarani C
957 86 Selvarani C
!https://redmine.auroville.org.in/attachments/download/9764/Union%20Window.png!
958 73 Giulio Di Anastasio
959 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).
960 73 Giulio Di Anastasio
•	(The output can be saved to a file, as the CRS should already be EPSG4326 – WGS84.)
961 73 Giulio Di Anastasio
962 74 Selvarani C
h2. 2.	Storing Shapefiles / Geopackages - (Selvarani, System 1)
963 74 Selvarani C
964 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)
965 73 Giulio Di Anastasio
Date in the name of Final Shapefile / Geopackage needs to be updated.
966 73 Giulio Di Anastasio
Once the merging operation is completed, the copy of Master shapefile / geopackage is deleted from the Temp folder.
967 73 Giulio Di Anastasio
968 74 Selvarani C
h2. 3.	Topology check of merged shapefiles
969 74 Selvarani C
970 73 Giulio Di Anastasio
The topology checker is applied again on the merged shapefiles / geopackages.
971 73 Giulio Di Anastasio
The “id_field” shall be removed from the attribute table.
972 73 Giulio Di Anastasio
973 74 Selvarani C
h2. 4.	Archive and replace the Master Shapefiles / Geopackages (Ram, System 4)
974 74 Selvarani C
975 73 Giulio Di Anastasio
Archive the previous master shapefiles / geopackages on system 4, and copy the new merged shapefiles / geopackages in its place.
976 74 Selvarani C
*Then delete the Merged Shapefile / Geopackage folder from System 1.
977 74 Selvarani C
*
978 73 Giulio Di Anastasio
979 74 Selvarani C
h2. 5.	Note about Shapefiles and Geopackages
980 73 Giulio Di Anastasio
981 73 Giulio Di Anastasio
All the above works are usually done using shapefile format, in QGIS latest version (3.16.3).
982 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.
983 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).
984 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)
985 223 Selvarani C
986 223 Selvarani C
h1. Creating 3D Shapefile/Geopackage
987 223 Selvarani C
988 223 Selvarani C
While creating a Shapefile/Geopackage, the File name/Database-table name, Geometry type and CRS have to be entered.
989 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).
990 224 Giulio Di Anastasio
991 224 Giulio Di Anastasio
h1. Exporting from QGis (shapefiles and/or geopackages) to CAD dxf format
992 224 Giulio Di Anastasio
993 226 Giulio Di Anastasio
An algorithm has been created by Selvarani, to see the whole process click here:
994 226 Giulio Di Anastasio
https://redmine.auroville.org.in/projects/gis/wiki/Automatic_export_from_QGis_to_dxf