[Exercise] New QuickCapture Variables

[xiao8579]

Description

We have added a bunch of new variables in 1.6 version of the mobile app. Plan is to officially release them in the upcoming 1.7 version.

For point features

1. Record the position (azimuth, pitch, roll) of the device when the feature was captured or when the photo was taken.

   • "${azimuth}" The device compass bearing when the point feature was
   • "${photoAzimuth}" The device compass bearing when the photo was taken)
   • “${pitch}” Pitch of device when the record was captured (0° is nadir)
   • “${photoPitch}” Pitch of the device when the photo was captured (0° is nadir)
   • “${roll}” Roll of device when the record was captured
   • “${photoRoll}” Roll of the device when the photo was captured

2. Photo longitude and latitude.

   • "${photoLatitude}" Photo latitude in decimal degrees
   • "${photoLongitude}" Photo longitude in decimal degrees

3. Cardinal Directions and Coordinate Formats.

   • “${DMS}” Location in Degrees, Minutes, Seconds
   • “${DDM}” Location in Degrees and Decimal Minutes
   • “${USNG}” Location in US National Grid
   • “${MGRS}” Location in Military Grid Reference System
   • "${directionCardinal4}" Direction of travel in 4 cardinal directions: N, E, S, W
   • "${directionCardinal8}" Direction of travel in 8 cardinal directions: N, NE, E, SE, S, SW, W, NW

For line and polygon features:

1. Calculate the length of the captured line and polygon features.

   • "${lengthM}" The length of the feature in Meters
   • "${lengthKM}" The length of the feature in meters Kilometres
   • "${lengthMI}" The length of the feature in meters in Miles

2. Calculate the area of the captured polygon features.

   • "${areaM2}" Area of feature in Meters
   • "${areaKM2}" Area of feature in Kilometers
   • "${areaMI2}" Area of feature in Miles

For device information

• "${appVersion}" The version of the QuickCapture application
• "${operatingSystem}" The operating system of the device

Test and verify results

Scan the QR code below to download the test project.

Verify feature attributes of submitted data with this web map: https://quickcapture.maps.arcgis.com/home/item.html?id=b88a464c99c84ce08b12ac870517ae49

1. Verify all new variables are successfully captured.
2. Verify the values match the actual position when you capturing the records.

[engelm1324]

Verify new QC variables are successfully captured: They were successful Verify the values match the actual position when you capture records: As far as I know, the features were captured in the actual position.

(In the webmap, there are point near Angier, NC, you can view there)

[engelm1324]

Tested the "${photoAzimuth}", "${azimuth}", “${pitch}”, “${photoPitch}” variable, and that worked as described.

[mdickieDev]

Works as described. However, the point for first photo I took has only "${photoAzimuth}", “${photoPitch}”, “${photoRoll}” attributes populated ("${azimuth}", “${pitch}”, “${roll}” are blank). Presumably this is because the position type changed to 1 (User defined) after collecting the few breadcrumb points before it.

A second test with the same steps. Start breadcrumb, move to location, stop breadcrumb, take photo(s) seemed to work fine.

[xiao8579]

Sorry for the confusion. I just found out the button Litter was not configured to capture any new variables. Now updated the project, so four of the photo buttons are all capturing new variables.

[xiao8579]

Test cases have been updated for 1.7 holistic.

[PaytenSamuels]

I was able to capture most of the new variables. They're mostly accurate, but my device accuracy isn't great for attempting to collect data inside :(

For the lines and polygons, I did not see the OS or app version variables.

I collected data in St Louis, Missouri if you'd like to look.

[ChaseFisher]

Worked at expected... 4 for 4 on this one.... nice work...

[mw1m]

Because of the user-defined position source type, most of these variables don't carry over. Perhaps have a quick disclaimer/warning about this informing variables like compass, speed, altitude, etc. won't be populated. These could be key values for analysis depending on your project.

Or the option to preserve it in some way?