Redmine: Issueshttps://redmine.auroville.org.in/https://redmine.auroville.org.in/favicon.ico2023-11-22T14:58:45ZRedmine
Redmine GIS - Feature #15270 (New): Record well sensor data (mqtt)https://redmine.auroville.org.in/issues/152702023-11-22T14:58:45ZPhilippe May
<p>Ram (<a class="email" href="mailto:rkris@wisense.in">rkris@wisense.in</a>) has set up a "gateway" to collect well water sensor (to start with).</p>
<p>The mqtt messages arrive directly on the server. See:</p>
<pre>
Sensor data published by the GW to this topic "/v1/telemetry" in JSON format. See example below.
{
"Name":"WSN-0012f82e",
"MacId":"00:12:f8:2e",
"RSSI":-19,
"LQI":13,
"0x78":"2.97",
"0x33":"215.00",
"0x58":"0.40",
"Sequence_number":64
}
</pre> GIS - Bug #15003 (New): Well level trend computation has opposite sign (minus instead of plus, an...https://redmine.auroville.org.in/issues/150032023-04-25T10:18:15ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>The well water level trend computed for each well by subtracting the last reading from the previous one, gives the difference with opposite sign: when the last reading is lower than the previous, the trend should be negative, but it is positive. Viceversa, when it should be positive, it is negative...</p> GIS - Feature #14306 (New): Cannot connect from QGishttps://redmine.auroville.org.in/issues/143062022-07-18T09:09:52ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>Today I tried to connect QGis to the PostGIS layers in Gisaf, as usual.<br />But I got the error message as in the attached screenshot</p> GIS - Bug #13901 (New): Map: style of the category with status 'E' is always applied https://redmine.auroville.org.in/issues/139012022-04-12T05:31:11ZPhilippe May
<p>Taking an example: V-BLDG-SHED has categories for 3 statuses: E, D, F.</p>
<p>But on the map, the style of category "E" is applied for the 3 statuses.</p> GIS - Feature #13597 (New): Courage well: tags to add after publishinghttps://redmine.auroville.org.in/issues/135972022-02-03T11:44:55ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>Courage well: the survey took 3 points on the casing: the three points define a circle (the casing), the center of the circle is a point which needs to be created by Raj, which will have the code of Borewell.<br />Inside the casing there are 2 pipes (from Auroville Water Service), because there are 2 separate pipelines and 2 pumps: during the survey (03.02.2022) one point for each pipe has been measured. When these data will be published, then a tag shall be created for each of these 2 AWS points, describing that these are two separate pipes for separate water distribution</p> GIS - Feature #12976 (New): Weather Station not recording data on 3rd October 2021https://redmine.auroville.org.in/issues/129762021-10-04T06:48:29ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>I have just noticed on the CSR weather Station Dashboard that the CSR Weather Station did not record any data other than the pressure, from 6 pm on the 3rd of October 2021, till 8 am on the 4th of October 2021.<br />To Philippe: kindly check if those data can be retrieved and stored into the database.<br />Thanks, Giulio</p> GIS - Support #12850 (New): Mistakenly deleted ticket about PgAdminhttps://redmine.auroville.org.in/issues/128502021-09-07T04:15:26ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>Dear Philippe,<br />I mistakenly deleted the ticket related to the PgAdmin. I am sorry, I clicked on the wrong button, and I don't know how to undo it (if it is ever possible...)</p>
<p>I am very sorry, hope you can recover it</p>
<p>Giulio</p> GIS - Feature #11486 (New): Button Labels for wells detailshttps://redmine.auroville.org.in/issues/114862020-12-21T04:56:02ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>The labels of the new buttons for the wells details are right now not clear: in fact the labels "Extra 1" / "Extra 2", or "Pump 1" / "Pump 2", or "Management 1" / "Management 2" confuses the user who does not know what the numbers 1 and 2 refer to.<br />These numbers refer to the records for each of these tables, so if there are 3 records in Extra, 1 having Harvest and 2 having CSR Geomatics as sources, then all the 3 records will be displayed, as "Extra 1", "Extra 2", and "Extra 3". So we cannot say for instance "Extra H" meaning extra info from Harvest, and the other records as "Extra CSR" meaning extra info from CSR Geomatics, because we might have 2 or more extra info from CSR Geomatics.</p> GIS - Feature #11329 (New): Boundary Stones Updationhttps://redmine.auroville.org.in/issues/113292020-11-12T07:03:32ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>So far, Boundary Stones have been stored in one single category, V-TOPO-BDST, name:T2.</p>
But:<br />Boundary stones have been surveyed in two ways:
<ol>
<li>by our team, when they found a stone in the field and they thought it is a Boundary Stone, but it has not been confirmed by Land Board because LB did not visit the place. We can call these stones as Unconfirmed Boundary Stones, and the category is the old one we were using for boundary stones (V-TOPO-BDST, Name: T2). At the moment we have 29 of these.</li>
<li>by Land Board team, and then recorded by our team. In this case, there are several different situations:</li>
<ul>
<li>Government Stones: they are physically present in the field, are visible and we can survey them, and for sure they have been placed by GOvernment Surveyors. The category and name are V-TOPO-GBST, T61. At the moment we have 28 of these.</li>
<li>Close Boundary Stones: their location is identified by Land Board, but the stones are not physically present (if they have been removed) or are not visible (if they have been covered by earth, e.g. in bunds), or are indicated by stoned placed by Auroville Land Board (this info is usually shared by Land Board surveyors). The category and name are V-TOPO-CBST, T62. At the moment we have 23 of these.</li>
<li>Approximate Boundary Stones: their location is approximately identified by Land Board surveyor, but for some reason the location is not accessible (dense bush, thorns, etc.), so a nearby point is surveyed, therefore its position is only approximate. The category and name are V-TOPO-ABST, T63. At the moment we do not have any of these.</li>
</ul></li>
</ol>
<p>As said, so far in Gisaf the boundary stones (43 of them) have been all stored in V-TOPO-BDST (T2), irrespective of their status.</p>
<p>Now data have been cleared, and a text file has been created for each of the above categories.</p>
<p>The first thing to be done should be to delete all the points stored now in the T2 table, and then upload one by one the text files, and import into the database.</p>
<p>Kindly let me know if I can proceed deleting the points from the Admin interface.</p>
<p>Thanks</p> GIS - Bug #10862 (New): Fix the issues resulted from import point bughttps://redmine.auroville.org.in/issues/108622020-08-30T09:19:30ZPhilippe May
<p>The bug <a class="issue tracker-1 status-3 priority-4 priority-default" title="Bug: Import issue with raw survey points (Resolved)" href="https://redmine.auroville.org.in/issues/10830">#10830</a> caused issues on the map: many points are not where they are supposed to be.<br />Even though <a class="issue tracker-1 status-3 priority-4 priority-default" title="Bug: Import issue with raw survey points (Resolved)" href="https://redmine.auroville.org.in/issues/10830">#10830</a> is fixed, this ticket tracks the corrective actions for fixing the database used in production.</p> GIS - Bug #10170 (New): Fix logouthttps://redmine.auroville.org.in/issues/101702020-05-23T11:17:57ZPhilippe May
<p>Logout doesn't clear the auth token</p> GIS - Bug #8763 (New): Calculation of Run-off volume and Vegetation classificationhttps://redmine.auroville.org.in/issues/87632019-08-05T05:46:48ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>As discussed, the formula Q = C*I*A will be instead in the form of V = C*R*A, where Q (flow in the unit of time) is replaced by V (volume of run-off), and I (intensity of rainfall in the unit of time) is replaced by R (Rainfall).<br />To be able to proceed, we need to use the vegetation classification shapefiles as generated by Selvarani on the raster created by Pavneet, and incorporate in the calculation parameters like:<br />- infiltration<br />- evapotranspiration<br />- threshold of effective rainfall to generate run-off<br />- antecedent conditions of the soil wetness<br />- imperviousness of surfaces (buildings, platforms, roads, etc)</p>
<p>I have copied the initial raster of the orthophoto mosaic from the drone as done by GKE Survey (Chennai Company) in the Samba folder: it is an .ecw file, which is readable by qgis</p>
<p>To be updated<br />Giulio</p> GIS - Feature #8262 (New): Change points into MISTAKES for updated cycle path and MM fencehttps://redmine.auroville.org.in/issues/82622019-05-09T09:29:21ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>Dear Raj,<br />Please give me the list of points related to the changed cycle path in Mahalakshmi park and on MM fence, so that I can change in the database</p> GIS - Feature #7817 (New): Updating dates for 66 records in the Benches attribute table.https://redmine.auroville.org.in/issues/78172019-03-04T09:32:58ZDebojyoti Mallickdebojyoti.mallick@outlook.com
<p>- Open attribute table for benches in QGIS [Layer Name : V_BLDG_BNCH_2019-03-04_13_02 (1) V_BLDG_BNCH]<br />- Sort by Date and you will find missing records<br />- Need to updates dates for those datasets</p> GIS - Feature #7776 (New): Text on IZ CAD filehttps://redmine.auroville.org.in/issues/77762019-02-26T07:27:53ZGiulio Di Anastasiogiulioenrica@gmail.com
<p>Dear Pavneet,<br />I saw that there is a text in the IZ CAD file which says "fence to be changed" <br />Are you aware of it?<br />We can look at it together</p>
<p>Regards</p>
<p>Giulio</p>