#3701
- Created on2024-03-27 17:09
- Reported by
- StatusFixed (Completed)
- PriorityNormal (3)
- Assigned to
- Milestone
- Plan Level-
- Estimate0.0
- Due Date-
Allow the Configurable Data Model to Specificy Method of Geometry Collection for SMART Mobile: Tap, GPS, auto
There was a request after discussing the smart 8 demo to do the above, so admin users can control.restrict how users collect Geometry if they like. By default it would allow any method, but the model could specify only allow them to use 1 or 2 methods if desired.
Hopefully this is a reasonable small change, let me know if it's more complicated than it sounds!
Hopefully this is a reasonable small change, let me know if it's more complicated than it sounds!
Leave a comment
Tap - drawn on map manually
GPS - user tells app when to take GPS reading
Auto - GPS reading automatically taken every x seconds - this options also requires a setting option for X
Also need to update the GeometrySource attribute to differentiate between GPS (User) and GPS (Auto)
GPS - user tells app when to take GPS reading
Auto - GPS reading automatically taken every x seconds - this options also requires a setting option for X
Also need to update the GeometrySource attribute to differentiate between GPS (User) and GPS (Auto)
When exporting to SMART Mobile packages we include some extra details for SMART Mobile:
The "GEOM_AUTO_GPS_SEC" option will provide the number of seconds between GPS readings for the GPS_AUTO option:
The GPS_AUTO, GPS_MANUAL, MANUAL_DRAW options determine which data collection methods should be supported. They will either exist with a doubleValue of 1 or not exist in the xml.
So, if only GPS_AUTO is supported you see something like this:
NOTE: the GEOM_COLLECTION_OP exists for use in SMART. It is a comma delimited list of the accepted values. You can use this if you want, but I thought adding specific options would be easier.
re: #3596
The GEOMETRY SOURCE options have been changes to support the above. Instead of MANUAL_DRAW, MANUAL_POINT, GPS, UKNOWN we now support:
<attribute attributeKey="fireboundary" ...>
<name language_code="en" value="Fire Boundary" source="DM"/>
<option id="IS_VISIBLE" doubleValue="1.0"/>
<option id="GEOM_AUTO_GPS_SEC" doubleValue="120.0"/>
<option id="GPS_AUTO" doubleValue="1.0"/>
<option id="GPS_MANUAL" doubleValue="1.0"/>
<option id="MANUAL_DRAW" doubleValue="1.0"/>
</attribute>The "GEOM_AUTO_GPS_SEC" option will provide the number of seconds between GPS readings for the GPS_AUTO option:
<option id="GEOM_AUTO_GPS_SEC" doubleValue="120.0"/>The GPS_AUTO, GPS_MANUAL, MANUAL_DRAW options determine which data collection methods should be supported. They will either exist with a doubleValue of 1 or not exist in the xml.
<option id="GPS_AUTO" doubleValue="1.0"/>
<option id="GPS_MANUAL" doubleValue="1.0"/>
<option id="MANUAL_DRAW" doubleValue="1.0"/>So, if only GPS_AUTO is supported you see something like this:
<attribute attributeKey="fireboundary" ...>
<name language_code="en" value="Fire Boundary" source="DM"/>
<option id="IS_VISIBLE" doubleValue="1.0"/>
<option id="ENTER_ONCE" stringValue="NONE"/>
<option id="GEOM_COLLECTION_OP" stringValue="GPS_AUTO"/>
<option id="GEOM_AUTO_GPS_SEC" doubleValue="2400.0"/>
<option id="GPS_AUTO" doubleValue="1.0"/>
</attribute>NOTE: the GEOM_COLLECTION_OP exists for use in SMART. It is a comma delimited list of the accepted values. You can use this if you want, but I thought adding specific options would be easier.
re: #3596
The GEOMETRY SOURCE options have been changes to support the above. Instead of MANUAL_DRAW, MANUAL_POINT, GPS, UKNOWN we now support:
- MANUAL_DRAW, //drawn on a map manually (user clicks point on map)
- MANUAL_POINT, //manually enter coordinates (x,y) without aid of map
- GPS_AUTO, //GPS with points recorded at fixed time intervals
- GPS_MANUAL //GPS with points taken by the user
- UNKNOWN
In smart-cs:9278 re: #3701
