|
POST
|
Hi, I've been posting a lot of questions here lately so thanks for your patience. I'm assisting with surveys remotely. One of our biologists was out collecting data today and they relayed the tracks were showing great in the Collector for ArcGIS app until about mid-survey when they disappeared. From what I understand, in the Tracker app the biologist could see his locations and I believe the 'My tracks' layer still showed in the layers list in Collector but nothing was showing on the Collector map. Has this happened with others? Any ideas of what might be happening? We will be going thru the Tracker data this afternoon but he said the external GPS was working and held connection. Thanks in advance for your thoughts!, Kathy
... View more
03-13-2020
01:20 PM
|
0
|
3
|
1431
|
|
POST
|
Thanks Aaron for the info info on the pagination and limit but hopefully we should be okay exporting after surveys. Thanks also for the documentation link!
... View more
03-13-2020
01:13 PM
|
0
|
0
|
3335
|
|
POST
|
That's great it "just works" but still have a setting within the app that actually shows which GPS provider the app is using would still be my preference. I don't like to just make assumptions. So far in our group the lack of settings in the tracker user interface doesn't have folks feeling that comfortable with the Tracker app compared to the Collector settings.
... View more
03-11-2020
10:07 AM
|
1
|
1
|
919
|
|
POST
|
Thanks Aaron for the response. I have other feature layers configured to the local time zone for use in the Collector app. We then have scripts to query the feature layers post-survey to both calculate field values based on survey data and then download records based on the most recent survey data. Having the dates configured with local time zone is preferable as it just makes more sense to the surveyors in viewing their data than translating from UTC and for the local dates to be stored in the downloaded files. We have also noticed that with UTC during the workday we can values for 2 different days in UTC versus 1 survey day in local time which adds errors to the queries. Adding the tracks layer to our current script post-survey process is the same, just makes more sense to look at the date/time in local time zone to be able to download that day's survey data. Since we can't add fields to the tracks layer view, we will have a translate UTC to local time zone in the script before querying the tracks layer to download the most recent survey data and then add in a field after the data is downloaded I guess. The feature class to feature class conversion tool does export the tracks layer as a feature class using Pro/arcpy so the fields are all there. I know you mentioned shapefiles but feature class downloads do work. Folks in our office have most commonly used handheld GPS to collect survey tracks and import into GIS. They are used to having the local date/time as the field not UTC or having to translate in between. We work in natural resources and this has been a very common workflow. I'm sure as more folks start using Collector and Tracker there will be similar requests. I do have the tracks feature layer added into Pro currently and it shows the tracks recorded. It recognizes the Location Timestamp as the Time Field but nothing else is configurable as if its just locked even with an advanced pro license. Also is there documentation in the Tracker for ArcGIS resources for all the fields created and what they are? I've seen some of your replies to other posts that some fields are only populated by Android devices and accuracy nuances but it would be great if it was just documented in one place. Thanks for your time, Kathy
... View more
03-11-2020
09:36 AM
|
0
|
5
|
3335
|
|
POST
|
I also now see a field in the tracks feature layer view named 'location_timestamp' and I was hopeful this field would be in our local time zone. It has the right date compared to the created_date but the time is not correct for when the tracks were recorded. How does the 'location_timestamp' field differ from the 'created_date' field? For example one record in a tracks layer shows. location_timestamp: 3/9/2020 11:21:14 PM (correct date, but time is 8 hours off should be 3:21:14 PM) created_date: 3/10/2020 12:46:50 AM My hope is to create a field in a downloaded copy of the tracks to have values in our local time zone. I would also like to configure the pop-up for the feature layer service. I have a view of the tracks but it still does not allow me to create to a new field in AGOL which I thought was mentioned in another post as a work around. Thanks, Kathy
... View more
03-11-2020
08:00 AM
|
0
|
8
|
3335
|
|
POST
|
Hi, We just got our first tracks recorded and I can view the tracks in the Track Viewer and see the corresponding point attributes along with the time shown in local time zone although this must be rendered based on my computer settings for the local time. However when I view the tracks feature layer I see the time must be recorded in UTC. I just went thru the process to configure and publish other feature layers using Pro to AGOL to have the local time zone. Is this possible to configure for the tracks as well? Otherwise it looks like we will have to create additional fields for the conversion to have the correct local date and time for the survey tracks. Thanks, Kathy
... View more
03-10-2020
09:44 AM
|
0
|
9
|
3494
|
|
POST
|
Hello, I just noticed that in the tracks feature layer that is created in AGOL the fields for creator and editor are different from other AGOL feature layers that have editing enabled. We are running scripts to query feature layers by "CreationDate". I realize we can accommodate for this in the python code but it seems like a best practice for AGOL/ESRI to have the tracks feature layers follow the same naming convention as other AGOL data fields. When you enable editing on AGOL feature layers the following fields are added: CreationDate Creator EditDate Editor Tracker feature layers: created_user created_date last_edited_user last_edited_date Is there any reason for the different naming conventions used in Tracker? Could these modified to be consistent with edited AGOL feature layers? Thanks for your time, Kathy
... View more
03-09-2020
09:18 AM
|
1
|
1
|
968
|
|
POST
|
Hi, We are trying to transition a survey that currently uses a customized ArcPad map to the new Collector app. It hasn’t been an easy task. Currently in ArcPad for a Boolean/binary field the users are used to having a checkbox option for a field. I’ve edited the integer field to be binary and added the two values to a list in AGOL but a checkbox is still preferable. Is this possible? Thanks in advance, Kathy
... View more
03-07-2020
07:29 PM
|
0
|
0
|
645
|
|
POST
|
I apologize I meant to add post a question, not a discussion!
... View more
03-07-2020
07:18 PM
|
0
|
3
|
919
|
|
POST
|
Hi, We are just getting familiar with Tracker for ArcGIS to use along with Collector. In the Collector app we see the external GPS is shown in the provider setting. How do we know which GPS the Tracker app is using? We want to make sure it’s using the external and not the integrated. Thank-you!, Kathy
... View more
03-07-2020
07:11 PM
|
1
|
4
|
1152
|
|
BLOG
|
Thanks Dan! What do you mean by 'clean everything out and start again', delete the clone and clone attempts and then create a new clone? I'm not very familiar at all with conda and so I must have lucked out the first go around with getting the clone and spyder working. I had previously created a shortcut as Duncan had outlined in this post (https://community.esri.com/people/Hornbydd/blog/2019/11/13/installing-spyder-ide-for-arcpro ) for using spyder. Thanks again for your help!
... View more
02-27-2020
11:04 AM
|
0
|
0
|
25338
|
|
BLOG
|
Hi, I had successfully installed Spyder thru a clone environment and it had been working until I updated to ArcGIS Pro 2.5 and then had a type mismatch in the clone environment. I was able to create a new clone and added the spyder package again similar to before thru the 'add package' within ArcGIS Pro. (your steps above). However now when I go click on the spyder.exe in my Users file path (same as before), I'm getting an error, "This application failed to start because it could not find or load the Qt platform plugin "windows" in "". Reinstalling the application may fix this problem." I've been looking around and found info related to the error with setting a new system environment variable with the correct path for "QT_PLUGIN_PATH path" but I'm not sure of what path to use. I tried the suggestion of “C:\Users\<username>\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone\Library\plugins\platforms” but this didn't resolve the issue or I'm not even sure the plugin is there. How do I find the exact name of the plugin? Is it installed elsewhere with the default install that I could copy it to the file path above? Has anyone else received this error and can help troubleshoot? Thanks, Kathy
... View more
02-27-2020
10:25 AM
|
0
|
0
|
25338
|
|
DOC
|
Hi Jake Skinner and Adam Eversole, I've using ArcGIS Pro's Feature Class to Feature Class tool: that you mention above in a script tool for other staff to use and it has been working great to download hosted AGOL feature layer data. However today I noticed that even though the Feature Class to Feature Class—Conversion toolbox | Documentation says it works with Basic, Standard and Advanced I'm getting a warning that the tool completes but with errors. The error is 001102: You must have at least the standard license to run this tool with the specified data. Apparently features with attachments must have a license level other than ArcGIS Desktop Basic to be copied. Ugh I had been working with an advanced ArcGIS Pro license but I'm glad I switched to basic to see this error since the script tool/workflow process I'm working on is for staff that use the basic version. I'm frustrated to find this error and wonder why a person has to have a standard license or higher to download attachments? Also just for clarification, the feature class to feature class tool does not allow hosted AGOL feature layer downloads in ArcMap correct only thru your tool Jake? Thanks for your help, Kathy
... View more
02-22-2020
11:11 AM
|
0
|
0
|
11077
|
|
POST
|
Hi, I am new to using the ArcGIS API for Python and starting to experiment with some of its capabilities. My concern is the number of credits I might consume and best practices for avoiding credit usage if possible. Currently, I am creating feature layers in which some of the fields will be populated using ESRI Field Apps (Collector for ArcGIS/Survey123). After each survey, I need a script to run and calculate values for other fields based on the survey data. The feature layers are currently stored in AGOL but I learned field calculator definitions are not saved so my alternative was to prepare a script to run after each survey. In addition to calculating fields, I also need to intersect the survey points with two other feature layers and populate those values in the table. I see the overlay uses credits, is there a way to get around this such as having output saved to a view similar to the join tool? Best practice 1 or 2? 1) Use the ArcGIS API for Python to download survey data after each survey and then run script for all calculations and intersect locally with 0 credit usage? Upload/append survey records to hosted feature layer with post-processed survey results. 2) Create a script using the ArcGIS API for Python to run all field calculations including intersect on survey data but with zero credit usage (is this possible?). Thanks in advance!
... View more
02-03-2020
02:27 PM
|
0
|
0
|
1214
|
|
POST
|
Thanks April for the update and bug number. Have you been able to create a work around in the interim or gotten it work with a new web map? Thank-you!
... View more
01-24-2020
08:47 AM
|
0
|
0
|
1137
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | 10-09-2025 08:45 AM | |
| 1 | 03-03-2025 10:42 AM | |
| 1 | 12-03-2024 01:10 PM | |
| 1 | 12-02-2022 03:16 PM | |
| 1 | 06-26-2025 05:35 AM |
| Online Status |
Offline
|
| Date Last Visited |
11-25-2025
08:47 AM
|