Project

General

Profile

Wiki » History » Version 260

Giulio Di Anastasio, 05/05/2021 17:10

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