nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Geopoint Rounding in Feature Report

Anonymous User

Is there a way to alter the default rounding when obtaining the lat/long of a geopoint question in a feature report? Anytime I pull lat/long in a feature report using this function ${geopoint | getValue: “y”} and ${geopoint | getValue: “x”} and it always rounds to the 5th decimal place. There are however some circumstances where we need it to 8 decimals. I understand the accuracy of the GPS on most mobile devices is really only accurate to the 5th decimal place, but I work for a state government agency that requires us to record this information to the 8th decimal place.

Find more posts tagged with

Accepted answers

Anonymous User

Hello Ruth,

I ended up adding two hidden calculation questions in the survey that use the pulldata function to obtain the full-length Lat and Long from our geopoint question. From there I use the round function and can add the lat and long for 8 decimal places in our feature report. It was overall straightforward, and technically only added one more question to our survey.

Thanks!

All comments

Anonymous User

Hello Ruth,

Thanks!

Ruth_JiatengXu

Hi @Anonymous User

Thanks for sharing here. The ${geopoint | getValue: “x|y”} currently can only return the lat/long with 5 decimal places, and you cannot get more significant digits. However, there is one expression can pad zeros to the output number, if you use ${geopoint | getValue: “x|y” | toFixed:8} you will get the lat/long with 8 decimal places (5 significant decimal digits + 3 zeros).

We have discussed your use case with the team, and in the future release we will make the ${geopoint | getValue: “x|y”} to return original lat/long, and then you can use round or toFixed expression to format the output lat/long. I will reply to this post once the change is available for testing.

Thanks,

Ruth

Anonymous User

Yes I have and trust me I understand the accuracy of the GPS on our mobile devices doesn't necessitate 8 decimal places, but unfortunately, it's what management wants.

DylanT_EsriCanada

Have you looked through the docs: https://doc.arcgis.com/en/survey123/desktop/create-surveys/geopoints.htm#GUID-CC769D6B-B463-4F1F-893B-F14F055FF229

Even if you can force more decimal points it doesn't mean that the device is recording the position more accurately.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.