Quick Capture points going to 0,0

[JohnBickmore]

We have set up a new ArcGIS Enterprise version 11.3

We are trying to migrate old QuickCapture Projects from our 10.9.1 Enterprise (Note this was not an upgrade - this was installing a new environment and shutting down the old)

I have downloaded my Quick Capture Point and Line Layers and loaded them into the new 11.3 Hosted database. I have configured my new Quick Capture App to use these layers.

The app appears to capture points and lines, however lines are not captured and points have coordinates of 0,0 and show off the coast of Ghana. The coordinates populate into the table and appear ok.

I also tried creating a brand new Quick Capture using one of the ESRI templates - I used the wildlife template. I get the same results - Points are at 0,0

When I set my Quick Capture up about ten days ago - I was able to capture points and lines, but am now unable to. Any suggestions appreciated.

Thankyou  

[JohnathanHasthorpe]

Hi @JohnBickmore 

Can you share the version of QuickCapture you are using and the device you are testing?

Additionally, are you seeing the same problem if you test the projects under the Continue without signing in option? This will rule out an issue with enterprise.

Please send an email to quickcapture@esri.com- If you want to get on a call.

[JonathanPollack]

This just started happening to one of my users.  While trying to debug I toggled "Use precise Location" off on my android phone.  Now it is happening to me too and I cant get it back to non 0,0.  Point on Quickcature app map looks right so GPS is fine on phone.  I had the person re-install the app/project on a new phone and she still records 0,0.  We are enterprise 11.2 hosted feature.  I am using 1.21.13.  Anything I can try?  Both Android and I Phone.  

[VylaGrindberg]

Hi! I wanted to add onto this as well. Our data collection had been going well, but this Monday (12/16/24) all points also captured nearly off the coast of Africa (0,0), or at least very close to it. ArcGIS Enterprise 11.2, I'll see what version of Quickcapture once our user is back in the office. I may also reach out to the same email above.

[JohnathanHasthorpe]

We have been able to reproduce the issue. It relates to a bug in ArcGIS Enterprise 11.3 and earlier (BUG-000171694). We aim to release a hotfix update to QuickCapture as a workaround for these older enterprise versions.

[VylaGrindberg]

Thanks Johnathan for the update! I saw QuickCapture updated last Friday so there was probably something there. For what it's worth (I think it was asked earlier) QC version the user had was 1.21.13, on an iPhone 13 with iOS 18.2. I'll keep an eye out for the hotfix.

[JonathanPollack]

Is there anything we can "ROLL BACK" to get working again?  Any idea why it only affects certain folks (currently only 2 out of above 120 QuickCapture users).

[JonathanPollack]

I confirmed in only happens with Enterprise Projects.  Works fine with AGOL projects.

[JohnathanHasthorpe]

We have a fix for the issue, but are going through the approval process before making available. I'll confirm the release date as soon as I can.

If you have data in the wrong place, here are the steps to correct it:

The bug relates to Enterprise version prior to 11.3 ignoring the spatial reference being provided by QuickCapture. QuickCapture captures data in the Geographic Coordinate System: WGS84. However, enterprise thinks that the coordinates are in the projected coordinated system: WGS 1984 Web Mercator (Auxiliary Sphere).

As the coordinates are still being captured, the data can be corrected using the following steps in ArcGIS Pro:

1. Add the affected feature layer to a map in ArcGIS Pro.
2. Select the features that are in the wrong place.
3. In the table of contents, right click on the layer and choose Data=>Export features. 
4. In the new layer that is created, run the Define Projection tool on it. Make sure you set the Coordinate System value to GCS_WGS_1984.
5. This will move the local features to the correct place. The next step is to use the Append tool to write these features to the original feature service:
6. The final step is to delete the points in the wrong place from the original feature layer if desired.

I hope this helps.

[JonathanPollack]

This might be a good fix for POINT data but what about LINES and POLYGONS?  I was thinking maybe I can use "PROJECT" somehow for a fix?  Any ideas?