Latest Contributions by kmsmikrud

‎10-21-2020

Hello, We are migrating a current project that is in ArcPad to ArcGIS Collector. There are a number of point features that are collected that are offset (not under the plane) and surveyors might use the 'collect here' or shift the initial location to collect the observation. As part of the post-processing metrics some of the values rely on an altitude value for the survey estimates. Can someone provide information on when GPS metadata fields are populated and what determines when they are not. Is it only when the initial (crosshair) location is used for the recording a location GPS metadata fields are populated? Is there anyway to get these metadata fields to populate? Also what is the best practice for projections and point data collection using Collector and the Web Mercator Auxillary Sphere. Should we set up point layers with the Web Mercator Auxillary Sphere and then post-process/export the points to our local projection? We will be using the Esri basemaps in the Collector app. Thanks in advance, Kathy

‎09-10-2020

Hi Robert! Thanks for the reply! I didn't have an underscore at the end of the prefix BUT your reply prompted me to think about the prefix I was including with the underscore. Then I looked at the script and found this: for t in allTables: tableName = t.split('.')[-1] nameParts = tableName.split('_')" So I removed the underscore and renamed my tables in the enterprise geodatabase and reran the tool. It worked!!!!! I need to check it all but at first glance I've never gotten the tool to repeat and sync (I'm so excited!). I wouldn't have thought of the underscore in my naming but that was it. Thank-you!!

‎09-10-2020

Hello GRSM GIS and James Tedrick, I am running into the same issue noted above with existing tables in an enterprise database and I was wondering what worked for getting it to update when prior tables exist. When I first run the tool, I specified a prefix of YukonPSS_long and that works great. I've never gotten the tool to run successfully again. In the prefix I've tried several options including sde_dcf.DBO.YukonPSS_long, DBO.YukonPSS_long, and YukonPSS_long. In the response above you mention ( (i.e., GIS.GRSM_SASQUATCH_SRV_EVENT - this should be found by the search pattern) or capitalization (GRSM vs grsm). What do you mean by search pattern? Since you said you had made it past this issue I was curious what worked hoping for some insight. Thanks in advance, Kathy

‎07-31-2020

Thanks Jonathon! We've downloaded the update and hopeful it will fix the repeats. It looks like besides the repeat issue we also had some sync duplicates. We are working offline and so it looks like there are multiple CreationDates for some of the points as well. When the surveyor is syncing there likely isn't the best internet connection so maybe the points tried to sync a couple of times is all we can figure since they are the same geometry/fix time. I'm so glad we lucked out on the timing for this hotfix. Thanks, Kathy

‎07-30-2020

We are also experiencing the duplicate records and are currently conducting aerial surveys using the app. I just checked to see if the latest release was out but don't see it. Do you have a date for when it will be released?

‎07-28-2020

Hi there, I was just following the code update from April 2019 but having the issue of the text not staying in the .info file after republishing. I wanted to check to see if the code might have changed again with any updates for modifying the green default background color? Thanks!, Kathy

‎07-24-2020

Thanks John. We'll change the interval for recording points. Thanks so much for all the great info. It makes me feel better. Thanks, Kathy

‎07-24-2020

This is an update. The QuickCapture team reported there was a glitch in ArcGIS Online that was causing the save as function to no longer work. The team fixed the issue.

‎07-22-2020

Thank-you John. The information you provided is very useful. I still do have a remaining question, the surveyor will be working offline so the user will be manually uploading the points after their survey when they are back to a connection. My question, for streaming points is there a maximum capacity that a user could reach when using Quick Capture offline. The surveyor could potentially be streaming points for up to 8 hours a day depending on when they choose to use that feature. I just didn't know if the offline capacity reached some maximum and we would lose data? Hopefully my question makes sense. Thanks again, Kathy

‎07-21-2020

Hi, I have a similar question to the one posted in changing the streaming distance threshold. Currently we have a project that has a point layer we would like to use the streaming points as our survey tracks to be able to get the GPS metadata. The aerial surveys we are using the Quick capture project for are offline and I'm wondering if you have a distance threshold you would recommend for this application. I'm also wondering if there is a limit to the number of streaming points that can be stored on the device offline. When I briefly used the button to collect streaming points in town it looked to collect 25-30 points and then send them? I'm not entirely sure, but don't want to hit some upper limit for storing data offline. Thank-you!, Kathy

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by kmsmikrud

ArcGIS Collector offset x,y,z values

Re: Migrating data from the Survey Feature Service to an Enterprise Geodatabase

Re: Migrating data from the Survey Feature Service to an Enterprise Geodatabase

Re: Duplicate records from Quick Capture

Re: Duplicate records from Quick Capture

Re: Viewing Survey123 form on Web-Pale blue "wrapper"?

Re: Line Streaming in QuickCapture

Re: QuickCapture Project Save As Error

Re: Line Streaming in QuickCapture

Re: Line Streaming in QuickCapture