Latest Contributions by JohnathanHasthorpe

‎02-06-2020

Hi Megan This is a current limitation of QuickCapture and Survey123. If the Bluetooth connection to the GNSS receiver is taken over by another app, QuickCapture and Survey123 are unable to automatically reconnect to the receiver once you return to them. We are looking into the issue and will update this post when further information is available. Thanks John

‎02-05-2020

For updates on the R2, please use this thread: Quick Capture R2 iOS

‎02-05-2020

R1 firmware update for iOS released today: The FW v5.44 updater can be found HERE Full FW v5.44 release notes can be found HERE This should allow QuickCapture to connect directly to the R1 receiver when using an iOS device.

‎02-05-2020

Hi Malcolm I can't comment on the Trimble workflow, but we have done some testing with the Arrow Gold receiver. Arrow's EOS Pro Tools app is able to calculate the RTK corrected positions and either override the phone's internal position source or update the positions coming from the GNSS receiver. As QuickCapture can point to either the internal position source or directly to the GNSS receiver (via Bluetooth), it can get the RTK corrected data in both configurations. This is for iOS and Android. Maybe Dan can provide some info on how this would work with the R1/R2. Thanks John

‎02-03-2020

Hi Malcom, Please see the following post on the R1: quickcapture not working with trimble r1 Essentially we are waiting for firmware updates for both the R1 and R2 receivers (from Trimble) to get them working with QuickCapture. When I say working, I mean that you will be able to connect to directly to the receiver in the app and get access to the GNSS metadata it outputs. I know Trimble is currently working on the R1 update, but the R2 should be next on their list. Dan Colbert may be able to provide more information on timelines and the workflow for realtime corrections. Thanks John

‎01-21-2020

Hi Crispin We are aiming to get this added to the app for the UC release (July). The idea would be to allow the Azimuth from the device to be written to a field through the use of a variable. Thanks John

‎01-21-2020

Hi Huong No this is not possible. Please share your use case and I'll get it added to the enhancement we have for this. Thanks John

‎01-17-2020

Hi Andrew The issue was that the user had not created the fields they wanted to update in the feature service. As long as the field exists in the layer, then you can follow the guidance in the documentation: Configure a project—QuickCapture | Documentation or https://community.esri.com/community/arcgis-quickcapture/blog/2019/10/06/understanding-user-inputs-in-arcgis-quickcapture . Please let me know if you need any help with this. Thanks John

‎01-09-2020

This is bug in the designer. When creating new buttons using drag and drop, the button ID is duplicated. This issue will be fixed in 1.4 (released February).

‎01-09-2020

Hi Amanda As discussed, the designer filters out all items types that are not feature layers, image services will not be visible. Thanks John

‎01-05-2020

Yes, but only for buttons pointing to line or polygon layers. In the designer, if you create a button that points to a polyline layer that has 2 dateTime fields (one for the start time and one for the end time), you will be able to apply the startTime and EndTime variables to them in the data tab.

‎01-05-2020

Hi Ricardo, yes the video was to explain the concept only. The offsets can't be applied dynamically.

‎01-05-2020

Hi - We are just waiting for a firmware fix from Trimble (for the R1). Once this is released, then QuickCapture should work with the receiver.

‎01-02-2020

If you want to apply an offset to your captured data, you would need to capture the offset and direction as attributes and then use them as the basis of a post-processing operation. For example, you could have a button for 5m left and a button for 5m right. Capturing breadcrumbs (continuous points) would populate the Side field with Left or Right and the Offset field with 5. If you then updated a direction field using the direction of travel variable, you would have all you need to calculate the offset. In ArcGIS Pro, you could calculate the offset direction as a new field. If the direction captured in the direction field was 0 degrees (North) then: - A Left offset would be 0 + 270 = 270 - A Right offset would be 0 + 90 = 90 (If the answer equals 360 or more, then you would just need to minus 360 from the answer) You will now have all the required inputs for the following tool: Move a feature to a specified location—ArcGIS Pro | ArcGIS Desktop

‎01-01-2020

Hi John - I have sent you an invite to discuss this further

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by JohnathanHasthorpe

Re: EOS Arrow Connection Issues when switching between QC and Collector

Re: quickcapture not working with trimble r1

Re: Quick Capture Trimble R1 GNSS reciever won't connect

Re: Quick Capture R2 iOS

Re: Quick Capture R2 iOS

Re: Capture basic attributes on QuickCapture

Re: Does QuickCapture integrate with the other Field Apps?

Re: Quick Capture Comment Box

Re: QuickCapture records on device show incorrect attribute data

Re: Remove Map Image Layers when navigating content

Re: ArcGIS QuickCapture 1.3 Released!

Re: Left and Right Offset of data

Re: quickcapture not working with trimble r1

Re: Left and Right Offset of data

Re: Battery overheating with polyline capture

Re: Can I Avoid Multi-Screen Forms and Use a Singl...

Re: Time filter messes with map on the app

Re: Quick Capture - records not being sent automat...

Re: Using the same project user input for differen...

Migrating from Oriented Imagery Classic to Oriente...