Enhancement: Reverse geocoding address field using geopoint / pull data about sarcop HOT 8 CLOSED

I added pulldata("@geopoint",${location},"reversegeocode.address.Match_addr") to the Address field. I did not yet put in a maximum error yet. We should discuss what a good threshold is if any.

from sarcop.

From Joe Simora [email protected]

Seems to work well in our test environment here. We are planning on testing more and utilizing during our regional drill in November to test further but thought I would let you know where we are with the Deployment Kit and utilizing the kit on the our AGOL account here.

I attached the modified Deployment Kit we are using. Maybe it will be on some use in the future.

If you have any questions or comments, feel free to reach out here.

SCTF SAR Survey2.xlsx

from sarcop.

Here is the pull data function Joe used

pulldata("@geopoint",${location},"reversegeocode.address.Match_addr","https://geocode.arcgis.com/arcgis/rest/services/World/GeocodeServer","featureTypes=" + "PointAddress")

from sarcop.

I believe @jdokemaps has implemented this in the current version of the form, check his work before beginning R&D.

from sarcop.

Cross-reference with County / State approach #17

from sarcop.

Questions:
There is an ability to set a threshold on horizontal accuracy if the GPS is showing +10m accuracy do we even want an address? What should the horizontal accuracy threshold be set to? Does dragging the pin override it? @tedrick

from sarcop.

Regarding horizontal accuracy - that can be set either by the body::accuracyThreshold column (maximum error in m) or via the constraint (using pulldata('@geopoint', ${q}, 'accuracy') function to retrieve the value and compare). A manually moved point has null accuracy; it will pass a body::accuracyThreshold check but not a constraint check.

from sarcop.

Reverse geocoding was implemented, but we have decided to not include an accuracy threshold at this time. This will be something we come back to in future versions.

from sarcop.