Add Polygon Support in SMART Observations
Details are here, we have agreed on doing tasks 1.1->1.9 only:
https://docs.google.com/document/d/13cNiOHHOzJUhr8Xfpw-mLgaC6Fo_c90H8KAVhJ0nP78/edit#heading=h.m33strmod4uj
Includes simple lines as well, I don't think it is determined yet how we want to proceed with this exactly. Likely they won't want to choose ahead of time for a Category to be either lines or polys, so there are some things to figure out there I think.
https://docs.google.com/document/d/13cNiOHHOzJUhr8Xfpw-mLgaC6Fo_c90H8KAVhJ0nP78/edit#heading=h.m33strmod4uj
Includes simple lines as well, I don't think it is determined yet how we want to proceed with this exactly. Likely they won't want to choose ahead of time for a Category to be either lines or polys, so there are some things to figure out there I think.
Leave a comment
Jeff agreed at the Nov 2023 TC meeting we would have at least a canned demo of this feature for SMART User Congress (The SMART Global Congress will be held 10-14 March, 2024. https://smartconservationtools.org/en-us/SGC2024)
In smart-cs:9184 support for polygon/linestring geometry attributes (re: #3596)
In smart-cs:9185 support for polygon/linestring geometry attributes (re: #3596)
and removal of entity plugin re: #3654
In smart-cs:9186 support for polygon/linestring geometry attributes (re: #3596)
In smart-cs:9187 support for polygon/linestring geometry attributes (re: #3596)
SMART Mobile data format is expected to be GeoJSON with a "source" property.
Source:
MANUAL_DRAW, //drawn on a map manually (user clicks point on map)
MANUAL_POINT, //manually enter coordinates (x,y) without aid of map
GPS, //taken by a GPS (smart mobile)
UNKNOWN;
"a:0:123a76486f6b452ba00569b9cfea764e": {
"type": "Feature",
"geometry": {
"type": "Polygon",
"coordinates": [[[11.2981, -0.5383],[11.4981, -0.5383],[11.4981, -0.6383],[11.2981, -0.6383],[11.2981, -0.5383]]]
},
"properties"{
"source": "gps",
}
},
Source:
MANUAL_DRAW, //drawn on a map manually (user clicks point on map)
MANUAL_POINT, //manually enter coordinates (x,y) without aid of map
GPS, //taken by a GPS (smart mobile)
UNKNOWN;
Implementing this required a change to the way ALL geometry columns are represented in reports. When testing we need to test upgrading reports from SMART 7 to SMART 8 on both desktop and connect to ensure most reports are upgraded correctly.
There is a lot to test here:
There is a lot to test here:
- attribute creation
- setting/updating values
- attribute support in profiles module
- query ( and query result maps) desktop & connect
- reports (desktop & connect)
- data generator
- connect data api (ER data api)
- connect custom query api (ER)
- smart mobile data collection
Independent Incidents are not showing the collected geometry attributes on desktop when viewed in the Incidents window. They are appearing in the query window.
Tested using version smart.8.0.0.win64.04122024 and Mobile 483 with "test local - Saanich"
Tested using version smart.8.0.0.win64.04122024 and Mobile 483 with "test local - Saanich"
@darrinc I don't think you've described the issue correctly here. The problem is if you have one incident open then open another incident the geometry attributes don't display correctly for the second incident. But if you close all the incidents then reopen the second one they do display correctly.
In smart-cs:9310 re: #3596